It would certainly bring us down to two major players on the Java side: IBM and Oracle.

IBM likes to create these 'boil the ocean' kinds of solutions

IBM could wind up having six different JVM [Java Virtual Machine] implementations

it's a good thing for Sun to get out of the doldrums

Every time IBM has bought a company that was in a leadership position, that company seems to have lost market share

JCP for behaving like a "Russian commissar.

Although many have lost faith in the JCP, this is one area where a new steward could really breathe new life into Java

the speediest when it comes to keeping their Java technologies up-to-date

hold back innovation in support of their own client needs

server market would become a bit tighter and that playing field would be altered as well

IBM is not interested in Sun software but in the Sun hardware and storage

pose a number of integration issues for IBM Software Group

expect that IBM will take the long view, that an open, flourishing ecosystem around Java will be the tide that lifts all boats

some observers say IBM would do well to merge the best parts of both platforms into one.

IBM has been a proponent of open standards in the Java ecosystem, and I expect that will continue

shed a lot of the weaker products (and a significant number of redundant staff)

EXTREMELY idiotic thing - because JSF has their famous lifecycle with lots of magic phases, some backing bean getters are called multiple times!

Back button problem.

Unreadable URLs. JSF always does the POST.

JSF is submitting a form on itself so it could call a backing bean method to handle an event. Of course, if you have a request, there is unnecessary repeated initialization, getter calls, postconstruct etc

Reusability? Good joke…

JSF - you are FIRED!

IDE support

Development of custom component? No way, extremely complicated. Extensible? In the movie, maybe…