What is hard in Scheme but easy in Java?

Question

These two languages are very different. They're each well-suited to their own particular tasks. What tasks are easy to do in Java, yet are hard / require lots of ugly code to do in Scheme? Another way of putting it: what is Java better at?

If you can think of things that Scheme is better at, see this question.

EDIT: This pair of questions has gotten about 14 upvote/downvote pairs. It's interesting that this is so controversial. I want to make a disclaimer that I don't mean this as flamebait.

Answer 1

Everything you do in Java is hard to read in Scheme. Everything you do in Scheme is simpler than in Java--once you understand it.

Answer 2

Finding a job.

Answer 3

Making apps that run in a web browser.

Most people have the JRE already installed, so you can run Java code in someone's browser (the client-side), complete with JRE libraries. To run Scheme code, you have to use a Scheme interpreter written in JavaScript. JavaScript has fewer permissions because it is sanboxed more strictly. Any libraries must be included explicitly.

Answer 4

Swing makes Java one of the easiest languages to create nice GUI's fast, so, general GUI-programming.

Answer 5

Hiring a junior developer who already knows the language.

Answer 6

Using the gazillion Java libraries out there (this can be a good or a bad thing)