2024 DevOps Lifecycle: Share your expertise on CI/CD, deployment metrics, tech debt, and more for our Feb. Trend Report (+ enter a raffle!).
Kubernetes in the Enterprise: Join our Virtual Roundtable as we dive into Kubernetes over the past year, core usages, and emerging trends.
Stats
Reputation: | 2431 |
Pageviews: | 0 |
Articles: | 0 |
Comments: | 31 |
Nothing here yet! Would you like to post an article?
Refcards
Distributed SQL Essentials
Getting Started With Distributed SQL
Comments
Aug 30, 2013 · ANDREW OLIVER
Aug 08, 2013 · Tony Thomas
Oct 23, 2012 · Will Soprano
Oct 23, 2012 · Will Soprano
Oct 21, 2012 · Eric Gregory
Oct 21, 2012 · Eric Gregory
Oct 21, 2012 · Eric Gregory
Oct 21, 2012 · Eric Gregory
Oct 21, 2012 · Eric Gregory
Oct 21, 2012 · Eric Gregory
Oct 19, 2012 · ANDREW OLIVER
Oct 17, 2012 · Will Soprano
Oct 17, 2012 · Will Soprano
Oct 17, 2012 · Will Soprano
Oct 17, 2012 · Will Soprano
Oct 17, 2012 · Will Soprano
Oct 16, 2012 · Will Soprano
I don't think Java is a great thing to write UIs in anymore. Oracle is pretty clear that JavaFX is the future http://amyfowlersblog.wordpress.com/2010/09/21/a-heartfelt-ramble-on-swing-javafx/. However when I watched this stuff demoed recently at the Chicago Java Users group (we have an office in Chicago and I split my time between our Durham, NC office, our Chicago, IL office and our likely third location Los Angeles, CA) I kept thinking "looks better in JQuery and is easier to do" after each demonstration. I also kept thinking "reminds me of the SwingSet demo 12 years back".
The same lack of killer design skills caused me to make applications in Swing that didn't look like I had killer design skills. I still don't make applications in jQuery that look like I have killer design skills. However, they're faster and don't require any plugins.
I also am not bullish on fat clients generally though: http://www.infoworld.com/d/application-development/the-long-death-of-fat-clients-196554
Oct 10, 2012 · Eric Gregory
You're reading only parts of the statements out of context and reinterpreting them to mean what you want the to mean. I said I've watched this since 2005 while working at JBoss, I continue to watch it while running a consulting company (even with clients who use JavaEE application servers) and that YOU can prove it to yourself with jobtrends or whatever sites you like (ironically when we started I trained everyone on EJB3 and not Spring).
You can spot check that your suggestion is not true by looking at a few ads on monster or whatever people use for job sites. You can also go spelunking linkedin and see how many people's most recent project was JavaEE vs Spring based. Spring won the programming model. Pure, simple and true.
JavaEE has a place but continuing to try and recapture the programming model is a waste of resources.
Oct 10, 2012 · Eric Gregory
Oct 10, 2012 · Eric Gregory
Oct 10, 2012 · Eric Gregory
I think that JAX-RS is a fine decorator for Spring, the default programming model for Java applications. JCA is an "SPI" and not "programming model" (thus I fully support it so long as I don't have to write it because it is winding) and irrelevant to the argument. It is not clear to me why I would write an EJB at this point. Between CDI, Spring, WebBeans, etc -- what is the role of EJB other than "legacy" at this point?
Don't get me wrong, I think it was bad branding and the illogic of the market that caused EJB3 (in particular) to be beat out by Spring. It took forever for Spring to support annotations and it seemed like forever that Rod & Co were trying to Jedi mindtrick us with "you like XML, XML is good"... However, the market decided. JavaEE is mostly dead as a programming model.
Oct 10, 2012 · Eric Gregory
I think that JAX-RS is a fine decorator for Spring, the default programming model for Java applications. JCA is an "SPI" and not "programming model" (thus I fully support it so long as I don't have to write it because it is winding) and irrelevant to the argument. It is not clear to me why I would write an EJB at this point. Between CDI, Spring, WebBeans, etc -- what is the role of EJB other than "legacy" at this point?
Don't get me wrong, I think it was bad branding and the illogic of the market that caused EJB3 (in particular) to be beat out by Spring. It took forever for Spring to support annotations and it seemed like forever that Rod & Co were trying to Jedi mindtrick us with "you like XML, XML is good"... However, the market decided. JavaEE is mostly dead as a programming model.
Oct 09, 2012 · ANDREW OLIVER
Sep 23, 2012 · Tony Thomas
Aug 09, 2012 · ANDREW OLIVER
Jul 24, 2012 · ANDREW OLIVER
Jul 13, 2012 · ANDREW OLIVER
Jul 08, 2012 · ANDREW OLIVER
Jul 02, 2012 · ANDREW OLIVER
Jun 08, 2012 · ANDREW OLIVER
May 31, 2012 · ANDREW OLIVER