ColdFusion MX on Mac OS X
kylner writes "This seemed to be one of the lesser-covered news items at Macworld, but it seems that Macromedia has decided to release its JRun 4 J2EE Server for Mac OSX. What's siginificant about this release? Well, they simultaneously released Macromedia ColdFusion MX for J2EE Application Servers to go with it! It may not be a stand-alone edition of ColdFusion MX, but this is still a dream item for any ColdFusion developer with a Mac at home. It took me about 30 minutes to install on my iBook 600 (I messed up a few times since it requires a little terminal work) but once I got it up and running it just worked. All I've had time to do so far is create a variable and output 'Hello World', but so far so good."
Because the world doesn't revolve around apache and php.
-
ping -f 255.255.255.255 # if only
Ah. It seems you are learning a valuable lesson: what you consider to be "proprietary" is not inherently bad. What you consider to be "Free" is not inherently good. The world is not a battle of "us versus them" (or in this case, "you versus us") but rather a bunch of people all struggling to make their way together.
One should use the best tool for the job, based on one's own judgment. If one uses a second-best tool simply because it is "Free," then one is still using a second-best tool.
I write in my journal
How about:
1) He wanted ColdFusion, not PHP.
2) Apache and PHP (and even mod_perl) come pre-installed even on the client version.
Karma: Incomprehensible (Mostly affected by posting at +5, reading at -1, and metamoderating everything unfair.)
And PHP ain't Coldfusion.
I work in and like PHP, but Coldfusion is much nicer. You pay for it and it isn't open, but CF has a lot going for it in terms of performance, portability and comprehensibility. I mention the last because PHP, Perl, ASP can be rough to maintain for casual developers. CF's tag-based approach is like having an immense and time-tested library of JSP tags which are largely in plain english so it is relatively easy to read.
When the vendor flops or gets bought and closed, your code turns to dust. I've seen it happen too many times.
You should know better. Code doesn't stop working when a vendor goes away.
With the number of Free tools that are as good as or much better than CF, their days seem numbered.
It startles me, in this day and age, just how common that misconception still is.
I write in my journal