When comparing Yesod vs Java, the Slant community recommends Yesod for most people. In the question“What are the best backend web frameworks?” Yesod is ranked 12th while Java is ranked 42nd. The most important reason people chose Yesod is:
While not required, Yesod offers templating through a Shakespearean family of languages to produce page code.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Offers templating for type-safe, well-formed content
While not required, Yesod offers templating through a Shakespearean family of languages to produce page code.
Pro Uses type-safe URLs
Ensures that data provided by the URL is type-safe. This means that data in the URL has a definitive type.
Pro Can be used without knowing much Haskell
While Yesod is written in Haskell, developers can achieve basic functionality without much investment in the language.
Pro Verbosity
It makes it easy to debug and to read code.
Pro Mature ecosystem
The language and all its tools have enough time to age and they've aged well.
Pro Type-safe
It is easier to catch errors sooner.
Cons
Con Is hard to customize
Learning how Yesod works internally is hard. It is a large framework with complicated components. Finding the appropriate code and understanding how it contributes to the framework is difficult, meaning developers will struggle.
Con Too much template haskell
You actually want to code in haskell and not some DSL with "magic" hidden under the bonnet.
Con Memory hungry
Running the virtual machine, application server and application itself consumes significant amount of resources.
Con Unnecessarily obtuse and verbose
If you like typing 40 lines of code to open a file, Java is the language for you. If, on the other hand, you’d actually like to get something done, look elsewhere.
Con Oracle
Enough said.
In more detail: Oracle has acquired Java from Sun and continues to surround it with controversy ever since (legendary lawsuit with google, money extortion from the enterprise users etc.).