Skip to main content

J2EE's Growing Pains

Given the discussion some of us in the CF community have been having lately about the affect alternative CFML engines have on CF as a whole, I thought this article about what's going on in the J2EE world these days was pretty interesting:

Alternative Frameworks: Bad for J2EE ... or Good?

On one front, the commoditization of things like app servers may lead to the big J2EE players to abandon their commercial offerings if they're no longer profitable. (I don't agree with this argument at all, but it's one that's frequently made.)

On another front, many in the Java world are challenging the complexities of J2EE and coming up with alternative frameworks such as Spring (dev framework) and Hibernate (persistence framework). These alternatives are more lightweight and easier to use than their heavier counterparts, but some argue that it starts to water down the standards.

On the CF side of the world, these arguments are very analogous to the situation with Macromedia's ColdFusion and New Atlanta's BlueDragon. Some think having alternative CFML engines makes CF less proprietary and strengthens CF overall, while others feel that it bifurcates CF and therefore weakens it. What are some of your thoughts?


Comments


I work for a very large non-profit health organization in the midwest and having an alternate engine has helped CFMX when it is called a proprietary technology. Especially when compared to .Net and J2EE, not that it should be but it happens.


I think competition is good in pretty much any arena. If you've got a viable product, you can be profitable, if you don't, then you won't. Especially in the enterprise software market, there is SO much more than the actual software to consider. One example is product support (paid or community). One thing that is missing from the CFMX/BD issue is a spec. J2EE is a formal specification, as well as a certification process for the spec. CFML, on the other hand, is whatever Macromedia makes CFMX do. Thus, you can't say what a "CFML runtime" really means. That, I think, hurts both Macromedia and New Atlanta, though the latter far moreso. Until there's a spec, CFML is absolutely a proprietary system, whether there are copycats or not. If one of those copycats can make a product that competes with CFMX, more power too them, but they're still a copycat. MM doesn't want competition, and why would they? Hence to CFML specfication, because they know that always playing catch-up will eventually beat every copycat product into the ground.

Comments

Popular posts from this blog

Installing and Configuring NextPVR as a Replacement for Windows Media Center

If you follow me on Google+ you'll know I had a recent rant about Windows Media Center, which after running fine for about a year suddenly decided as of January 29 it was done downloading the program guide and by extension was therefore done recording any TV shows.

I'll spare you more ranting and simply say that none of the suggestions I got (which I appreciate!) worked, and rather than spending more time figuring out why, I decided to try something different.

NextPVR is an awesome free (as in beer, not as in freedom unfortunately ...) PVR application for Windows that with a little bit of tweaking handily replaced Windows Media Center. It can even download guide data, which is apparently something WMC no longer feels like doing.

Background I wound up going down this road in a rather circuitous way. My initial goal for the weekend project was to get Raspbmc running on one of my Raspberry Pis. The latest version of XBMC has PVR functionality so I was anxious to try that out as a …

Setting Up Django On a Raspberry Pi

This past weekend I finally got a chance to set up one of my two Raspberry Pis to use as a Django server so I thought I'd share the steps I went through both to save someone else attempting to do this some time as well as get any feedback in case there are different/better ways to do any of this.

I'm running this from my house (URL forthcoming once I get the real Django app finalized and put on the Raspberry Pi) using dyndns.org. I don't cover that aspect of things in this post but I'm happy to write that up as well if people are interested.

General Comments and Assumptions

Using latest Raspbian “wheezy” distro as of 1/19/2013 (http://www.raspberrypi.org/downloads)We’lll be using Nginx (http://nginx.org) as the web server/proxy and Gunicorn (http://gunicorn.org) as the WSGI serverI used http://www.apreche.net/complete-single-server-django-stack-tutorial/ heavily as I was creating this, so many thanks to the author of that tutorial. If you’re looking for more details on …

The Definitive Guide to CouchDB Authentication and Security

With a bold title like that I suppose I should clarify a bit. I finally got frustrated enough with all the disparate and seemingly incomplete information on this topic to want to gather everything I know about this topic into a single place, both so I have it for my own reference but also in the hopes that it will help others.Since CouchDB is just an HTTP resource and can be secured at that level along the same lines as you'd secure any HTTP resource, I should also point out that I will not be covering things like putting a proxy in front of CouchDB, using SSL with CouchDB, or anything along those lines. This post is strictly limited to how authentication and security work within CouchDB itself.CouchDB security is powerful and granular but frankly it's also a bit quirky and counterintuitive. What I'm outlining here is my understanding of all of this after taking several runs at it, reading everything I could find on the Internet (yes, the whole Internet!), and a great deal…