Watch this short video that showcases ColdFusion technology. If you multiply this by only 3 projects you have already made your money back in savings when compared to paying a PHP programmer by the hour to create the same functionality and you've only just begun. Speed of development is the key with ColdFusion over other programming languages.
NET only faster. Including a robust development language Your email address will not be published. Save my name, email, and website in this browser for the next time I comment.
Submit Comment. Is Adobe ColdFusion Dead? After Decades of ColdFusion Experience. Performance and Security Improvements The modern versions of ColdFusion are the fastest application servers ever produced. You May Also Like Submit a Comment Cancel reply Your email address will not be published. If so you would be wrong. I remember when it was being designed and first release that it was such a hodge-podge of ideas that in combination resulted in something that we could trivially see were bad using principles from long before.
I don't really care much for language popularity, but I think the case to be made, as can be for any language of waning popularity, is the pool of developers who are available for hire. ColdFusion is also unpopular for an important fact: it's proprietary and their licenses aren't cheap.
WorldMaker on May 23, parent next [—]. ColdFusion also suffers technically from most of the same reasons PHP is historically legitimately unpopular as a technical choice: confusing client-side and server-side markup in the same files, making it hard to share code cleanly between modules, often "encouraging" bad software architectures simply because they are the most convenient to page layout.
ColdFusion does everything that PHP does poorly, with the added bonus that you are paying for it, and there's never been the excuse that ColdFusion just runs "everywhere" like PHP had during the early internet. Without Rails or Sinatra, Ruby web apps would have the same problems. WorldMaker on May 23, root parent next [—]. The trade-offs for those architecture problems was development speed and "ease of use", PHP succeeded so well on the early internet almost precisely because of such problems.
ColdFusion too presumably succeeded as much as it did in Enterprise because of those problems in that space easy to sprinkle a bit of server-side code in the middle of a page at will , though with no excuse for being free or easy to host. It's unfortunate that that also leads to the legacy of spaghetti code it will perhaps eternally have left behind in big-E Enterprise.
CydeWeys on May 23, parent prev next [—]. The proprietary nature of it has really stunted it in the long term. Students aren't learning it in school because there's plenty of free in all senses of the word alternatives available, such as Python or NodeJS. I think the overall marketplace has shown pretty clearly that proprietary languages are doomed to insignificant market share at best, outright failure at worst. The writing was really on the wall when Microsoft opened up all of.
CFML has had open source implementations for over 10 years. Too late. It was already dying a decade ago. Two decades ago might have made a difference. Wasn't speaking to that - only whether or not there are open source options. Being open source in and off itself seems to be a prerequisite, but it's more a matter of building a strong ecosystem for example, imagine Ruby without Rails or node without npm , which never really materialized for CFML.
Got to love how much misinformation is being spread here. The ColdFusion language has multiple engines that it can run on. At least 2 of them are open source. Coldfusion has a unique place in the world of programming languages. In its prime it was a great way to get a website started with minimal effort, similar to PHP. Both PHP and Coldfusion let you create simple websites, easy to deploy, full of spaghetti code.
Source: Was Coldfusion developer for approximately 10 years. You are correct with the spaghetti code comment, but I've seen worse in Java. Author, glad you don't care. You've failed to convince me that I need to learn cold fusion now or in the future. Let me tell a story. Up until ish, it was still being maintained and distributed. The guy that wrote it was the sole owner and maintainer of this billing company and swore up and down that RPG was the best language in the world and he'd never consider writing in anything else.
But guess what happened? He couldn't hire anyone else to maintain this system. Further, it was slowly and obviously decaying. Operating the system was a full time job for 2 employees. Eventually the companies using that software abandoned it for a solution that was maintained by a company that was both larger and had a workforce of more than 1. Those companies cut their billing staff to it being a part time job for just 1 person. Why do I tell this story? Because you can literally replace "ColdFusion" with "RPG" and you'll have the same article that guy would have written.
That guy's business is shutdown now. Popularity IS important. Popularity feeds support and stability. The author is free to cling onto a language that, frankly, I thought WAS dead.
But he'd be well advised to brush up on one of the more "Popular" languages and techs. Perhaps, rather than worry about which language is "dead" this year, we should be more focused on the quality of our programming, no matter what language its in. Just another opinion Sure you're not going to find a decent CF job down the street. Doesn't mean nobody uses CF anymore or that there are no CF jobs out there.
I know there are plenty of sites out there built in whatever other languages, what I mean to say is that you still come across CF sites and you'll always come across CF sites. I'll say , coldfusion is a good starter language to learn and build from. And I'm not astroturfing just saying. If it wasn't for coldfusion I never would have built some of my first apps, and consequently never have gotten my business started. I owe coldfusion and the cf community my gratitude.
And I feel it safe to say I'm not alone on this. It wasn't designed to be the only language out there. Neither was ColdFusion. Neither was Java. Neither was Ruby. Neither was Python. They are all tools, and they all have their place. A reader brought up Myspace as an example of a web app that started as CF and had problems.
That is true. That is the beauty and the tragedy of ColdFusion. You can just throw something together. So in the case of myspace it wasn't the technology that failed, but the way that the technology was used. More important than the technology is the use of the technology. You cannot just make general statements and call them truth. I have seen hundreds of apps written in ColdFusion. Some of them would easily scale and handle loads of traffic.
Some others would and did crash at random times. I have also seen projects in PHP that were absolute garbage. The goal wasn't stability, scalability or anything other than throwing together some code.
CF is just getting started! All of the computer systems in Washington for government have been converted to ColdFusion. I have been using CF since , and I think it's great.
I build all my applications in record time, saving my companies time and money. In regards to the "no sites use CF" comment. Have you heard of MySpace, one of the largest social networking sites on the planet. They use CF and CF frameworks. So no CF isn't dead, nor is it going to die anytime soon. In the section "Coldfusion is alive and well and living in the Enterprise".
You say your first app you took over failed like clockwork. I wouldn't blame the language, I'd blame the back-end database MS Access. Before you single out a technology, why don't you get to know it better. Python is very elegant as well, day to day I would love to never leave the php world.
The thing is, once I got railo CF running on the cloud with fusion reactor, it's very difficult not to code in CF. For me it's the easiest way to run a man enterprise application cluster.
I was starting to jump on the CF is pissing me off bandwagon but with Railo, my love affair is back on. Also, for all you CF devs getting butthurt by this guy, all he had to do was post CF is dead story and his blog just took off, poke at a beehive and you get a little traffic? Wait and see There's no point learning something, even if its free, which doesn't help you keep upto date with the latest web developing techniques.
I laughed outload when I read this - you obviously don't deal with billion dollar companies do you? Want to earn 6 figures with ease? And who gives a crap if it is used heavily for corporate intranets?
I mean - have you even installed CF past version 5? I digress, instead, leave that to us professionals and continue succeeding in being a complete and utter HACK. Just because you have not used the language in a number of years clearly is not an indicator that you are a trend-setter as you seem to dictate yourself to be when it comes to programming languages. If you happened to take a look at the Adobe curriculum, they espouse it as such.
Indeed, many of the Flex tags related to charting, formatting and validation have their roots in CF. Equally noted if you were around at that time Flash 4 briefly had coding roots in VB with at that time Basic syntax that involved commands like "add" and "if.. So before you espouse a language as essentially dead, take a look at the wider audience.
You'd be surprised that in spite of your tunnel like vision, CF has a niche in the programming environment, like. It was my first dig at the language, not that I really had any interested in learning the language, but it came with the package. I detest the cumbersome and unorthodox syntax. I like the ease that it just works and ties up nicely with Flex.
Debugging coldfusion was pain in the ass in the beginning until you established more knowledge such as and so forth. I think almost all folks have taken it too personally. The point that is being missed here is whether it's worth it for the new developers to learn "Solely" coldfusion? I very much doubt it. Java being more versatile and widely used than Coldfusion, I would definitely stick with it. Also, Java's syntax is not as horrendous as Coldfusion. One point I agree with Robert Reinhardt is that Coldfusion was part of initial steps that lead to Rich Internet Apps movement, when it first introduced remoting.
That was Coldfusion MX. It saved it back then. Then it was the ability to dynamically generate Flash forms right from coldfusion and so forth. For some it always had those locked up features for RIAs, that the other Open Source technologies had to learn and adapt from.
Apart from that, due to the reasons 'unknown to me', the acceptance and usage never gained much traction in the wider development community. Whether it lacks enterprise capabilities? These are some of the points that have crossed my mind over the past few months.
So, I was much surprised when I saw Coldfusion 9 released. Now as a developer who doesn't know diddly squat about Coldfusion and looking to learn new skills. I learn from folks like you everyday.. As a developer - for many obvious reasons I try to focus on technology that require taking as less hurdles as possible. Still - if anyone feels comfortable with coldfusion or QuickBasic be my guest.
Also important, i find it a funny article! I've used two variants in projects for startups who then migrated to a full CF license. I also wanted to shout out to Ray C. Aral, across the pond in Canada, CF is actually taught is an introductory language of choice for up and coming computer progammers as a way to teach them the basics of programming.
Believe it or not, when applying OOP and computer logic principles to CF, it can make a great framework for developing minds. With that toolset, they can readily see why 2 lines of CF can equal up to 10 lines in. NET code or 20 lines in J2EE code which makes developers wonder why waste your time creating so many lines of code. While the underlying engine may be proprietary, libraries written in CF and to some extent Java do not have to be.
Many of the current fads, such as Rails, are anti-SQL and want to replace SQL with object databases or wrappers that look like object databases. Objects already lost the database fight because they cannot take advantage of set theory, but the hanger-on's keep pushing it out of stubbornness or purity obsessions. I suspect that someday a decent desktop-like GUI-over-the-web open standard will appear so that we don't have to work with the e-brochure approach of hypertext markup-based technologies and buggy, version-sensitive JavaScript libraries.
That will be the game changer. Until then, I've seen nothing that is a noticeable improvement over CF. ColdFusion is the backbone of our entire enterprise. It is awesome to work with. We can rapidly develop applications and get them into production. AT ALL! While some of your points may be valid, the fact is that not everyone that learns ColdFusion is focused on a lifetime career as a developer.
There are plenty of people out there learning ColdFusion because it is easy, fast to implement, and a very powerful web technology that works well the other Adobe technologies such as Flex. ColdFusion is the perfect backend development language for new and old web developers. You obviously do not know anything about ColdFusion today. That's why you are getting fact checked left and right. I am sure it wasn't your intention to look foolish, but maybe a bit of research could have save you the embarrassment.
What worries me though is that you are ultimately dangerous. I mean you could be hurting the very young developer you are supposedly trying to protect. ColdFusion is a wonderful language and it has a very short learning curve. It makes development a pleasure, by allowing you to concentrate on solutions rather than the language.
I would not call it easy, I think it's clever. A lot of intelligence goes into making ColdFusion easy to use and this is what is often wrongfully underestimated by the narrow minded. Those of us who love it see behind that apparent simplicity. In fact, I think, ColdFusion most impressive features is what it don't make us do. It is a tagged language and using a tag will create objects, instantiate them, and add properties to them all in one line of code. Tell me that's not cool?
Want to do AJAX? No problem a few tags could generate most of the functionality you will ever need. Want to do some FLEX? Just for the record there are plenty of sites that use ColdFusion. And by the way ColdFusion lives in the cloud, yet another thing you got wrong.
Again a bit of research could have safe face. Hope this helped, Miguel Ulloa by Miguel Ulloa on Hi Miguel, Way to ignore the main point I'm making: that the opportunity cost of teaching people a proprietary, commercial application server solution in an age when application servers are commoditized is a disservice. I stand firmly by that assertion. I have nothing against Coldfusion on a technical level. However, it's the last technology I would recommend an aspiring developer to learn when there are far too many interesting and relevant open alternatives.
People who don't agree with you are not necessarily ignorant. Read the post again, understand the main argument and you'll see what I'm talking about. If you read the post again, you'll see that I specifically mention that Coldfusion may live on in enterprises for years to come. CF applications tend to have been written by newcomers to programming who had no formal training in programming and little experience or knowledge of modern programming.
Do not consider a career in maintaining legacy CF applications unless you enjoy maintaining ill-designed spaghetti code. Or, if you have repeating controls having the same name in a form which is perfectly legal , CF makes them available as a single 'list' variable with the various values in a comma-separated list. This just does not work if the input can contain commas when your input is plain text, duh. I use CF almost every day because I have to and my humble opinion is that CF has to be the worst programming language out there.
And ColdFusion is not even free. The ultimate workaround for the problems of ColdFusion and the uncertainty regarding its future is simple: do not use it, do not buy it, do not learn it.
And for you managers who happen to be in charge of a large legacy of CF applications, my advice is simple: despair. Sit down on the floor and cry, because you need CF experts and they are becoming increasingly scarce on the market. Your entry here comes across as an attempt to sway public opinion with personal opinion.
In "Is it dead? In "Is it dying? If that is a fact, then please provide references to that data. You also state "It's not modern, it's not exciting", which is, again, an opinion. Others feel just the opposite. An opinion, by nature, is neither right nor wrong. It is not a fact, and should not be made to appear as fact. Why not complain about all of "first-class functions" features. You can write functions within functions if you include them.
You can assign functions to variables; you just cannot assign anonymous functions to variables. Python cannot do that either. Net have on ColdFusion? As for other languages i. PHP, it does not support any "first-class functions" features, neither does Java. This goes to reinforce my previous post point that if ColdFusion holds its shares is because it does not sit around waiting to become extinct.
As for the rest of you post, it kind of go downhill from here. Are you the very programmer you are so enthusiastically complaining about? My feeling about most of you post is that bad developers will do bad development on any language, and you cannot blame the language for that. All Web development technologies have proprietary code designed to hook you in. Innovation is what drives shares in our business. If X programming language has nothing to bring to the table nobody is going to adopt it.
That said Web Development is Web Development. That's why I could not disagree more with you main point. ColdFusion is just as relevant as any other Web programming language that has amounted and more importantly maintained its shares. Anything you learn in ColdFusion is transferable to other technologies and vice versa. I am not just talking about what's common among the languages but also what's unique.
Yes, please check OpenBD at openbluedragon. Not that that matters much either way as most technologies are free for developers anyway, unless of course you like to look at the source, I certainly do, but if you ever wanted to run ColdFusion site completely free you can.
Aral, if you were arguing what's cooler, I would totally agree with you, but cooler does not mean better. ColdFusion was once a cool technology also. It was ground breaking. There was nothing like it. Since then many other technologies have come up and maybe they were better at first. You can always learn from others design misses or improve on their designs, but ColdFusion is not standing still.
Instead it is absorbing the newest innovations. Here is a quote from Gartner, because I am sure you know who they are and respect their opinion right? There are plenty that do a better job one of these areas; there are few that do a slightly better job in two out of three; but there are none that match CF in all three areas.
I have been developing ColdFusion applications since the beginning of ColdFusion. Of course it isn't object-oriented and most of the existing frameworks don't help either. What the future will hold? No idea and I remember a lot of platforms and languages coming and going. Cloud computing? Where do you see that? They talk about it, but that is it. I agree with your comment about spending more time on usability and accessibility issues, but if big companies push a specific product it usually has a good chance to survive.
But I do think Adobe is a bit late pushing ColdFusion. As more Developers there are as more pressure will be on Adobe getting it right and that can only be a good thing. Railo will hopefully help the cause and that is the right way forward. There is nothing that those technologies do better than ColdFusion. I have found a lot of the innovation coming from Python and Ruby. Their framework DJango and Rails respectively brought a wealth of features never available to the average developer before.
0コメント