Honestly it doesn't make that much difference these days. Spring and Java EE are both good choices. Java EE needs an app server but there are plenty of free options including Glassfish which is the reference implementation. I'd tend to choose Java EE over Spring because it is easier to "grow" as you need to in my opinion, and I don't think the learning curve is any bigger really. Plus the fact that it is backed by the major vendors means that if you need to tie into a banks MQ Series/CICS/whatever back-end it is that much easier to do. There is pretty much nothing you need to do in enterprise software that Java EE doesn't handle reasonably well with the possible exception of HFT - even in low latency environments Java is a pretty decent choice.
10 years ago I'd have gone the other way mainly because Spring was just so much simpler. These days Spring has got really kind of complex, the two more-or-less have feature parity, and Java EE has got simper, and they've kind of met in the middle.
One downside of Java EE is the standard web framework - JSF. Whilst it has its uses for the most part there are simpler options for a "typical" architecture - JSON over REST being presented via JQuery. Spring MVC is a good choice, as is Struts 2.
Yup. Used BlackBerry for about 5 years before switching to iPhone when the 4 came out. It took a day or to to get used to it, but these days I'm just as fast typing on the screen as I ever was on the BlackBerry phone. And the phone a whole is a lot better than the last BlackBerry I owned.
I do find the anti-Apple bias a bit weird here. Apple, Kindle, PSP 3, Xbox,Nokia, Samsung, Wii, IBM, Intel, MS all made at Foxconn. Apple is currently getting all the flak and yet are the only firm actually addressing it.
Agree with this. I think though it is interesting to me that he has shown his hand so openly - I wonder if he suspects he's about to loose. Basically Monty made a ton of money selling MySQL to Sun (way more than it was worth) and has considerable vested interest in Oracle being forced to sell MySQL because, I guess, he wants to buy it back again. He has overseen a slew of measures that are designed to keep MySQL alive outside of Oracle including the MariaDB fork and formation the Open Database Alliance to unify all development. However MariaDB isn't getting much traction (and is not all that likely to do so) so getting the MySQL name back would be good - and potentially he could sell it to someone else again an another few years which would be a neat trick. By contrast the former MySQL CEO Marten Mickos - and the ex-head of Sun's database group - not only dismissed concerns over Oracle's ownership of MySQL but also called on the EU to approve Oracle's purchase of Sun. Eliison is on record as saying re MySQL "we are going to increase our rate of investment to that product." It seems to me that owning MySQL is a bit of a win/win for Oracle. It generates decent revenues for Sun and can do the same for Oracle. If they don't own it then they loose customers to open source. if they do then they simply have a low cost alternative to the full Oracle platform.
Slashdot Mirror
Now the dust has had a chance to settle how do you think Oracle are doing as stewards of Java?
Between Oracle and Liquid Robotics you had a very brief spell at Google. Why did you quit so quickly?
What use of Java you've seen people make has most surprised you?
Honestly it doesn't make that much difference these days. Spring and Java EE are both good choices. Java EE needs an app server but there are plenty of free options including Glassfish which is the reference implementation. I'd tend to choose Java EE over Spring because it is easier to "grow" as you need to in my opinion, and I don't think the learning curve is any bigger really. Plus the fact that it is backed by the major vendors means that if you need to tie into a banks MQ Series/CICS/whatever back-end it is that much easier to do. There is pretty much nothing you need to do in enterprise software that Java EE doesn't handle reasonably well with the possible exception of HFT - even in low latency environments Java is a pretty decent choice. 10 years ago I'd have gone the other way mainly because Spring was just so much simpler. These days Spring has got really kind of complex, the two more-or-less have feature parity, and Java EE has got simper, and they've kind of met in the middle. One downside of Java EE is the standard web framework - JSF. Whilst it has its uses for the most part there are simpler options for a "typical" architecture - JSON over REST being presented via JQuery. Spring MVC is a good choice, as is Struts 2.
Yup. Used BlackBerry for about 5 years before switching to iPhone when the 4 came out. It took a day or to to get used to it, but these days I'm just as fast typing on the screen as I ever was on the BlackBerry phone. And the phone a whole is a lot better than the last BlackBerry I owned.
I do find the anti-Apple bias a bit weird here. Apple, Kindle, PSP 3, Xbox,Nokia, Samsung, Wii, IBM, Intel, MS all made at Foxconn. Apple is currently getting all the flak and yet are the only firm actually addressing it.
What is this? A report from the Maximegalon Institute of Slowly and Painfully Working Out the Surprisingly Obvious?
Agree with this. I think though it is interesting to me that he has shown his hand so openly - I wonder if he suspects he's about to loose. Basically Monty made a ton of money selling MySQL to Sun (way more than it was worth) and has considerable vested interest in Oracle being forced to sell MySQL because, I guess, he wants to buy it back again. He has overseen a slew of measures that are designed to keep MySQL alive outside of Oracle including the MariaDB fork and formation the Open Database Alliance to unify all development. However MariaDB isn't getting much traction (and is not all that likely to do so) so getting the MySQL name back would be good - and potentially he could sell it to someone else again an another few years which would be a neat trick. By contrast the former MySQL CEO Marten Mickos - and the ex-head of Sun's database group - not only dismissed concerns over Oracle's ownership of MySQL but also called on the EU to approve Oracle's purchase of Sun. Eliison is on record as saying re MySQL "we are going to increase our rate of investment to that product." It seems to me that owning MySQL is a bit of a win/win for Oracle. It generates decent revenues for Sun and can do the same for Oracle. If they don't own it then they loose customers to open source. if they do then they simply have a low cost alternative to the full Oracle platform.