51–60 of 83 posts
If using Coldfusion, I’d recommend scanning your sites with a service or product like Tenable Security. There are quite a few high priority exploits that we’ve seen over the recent years. These end up being available as one-click takedown type scripts in tools like Metasploit.
Am I the only one bothered by the author's repeated assertion that Node is a language?
I should probably just take off my "Well, actually," glasses.
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.
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. (Certainly there are workarounds to such technical projects in…
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.
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 Mic…
https://en.m.wikipedia.org/wiki/ColdFusion_Markup_Language#H...
I don't get how you could think "interpreted XML" was a good idea. Great, you don't need context switching the way PHP does it, but instead of properly splitting templates and code, ColdFusion still mixes both while managing to be less readable. Added to that I feel unable to imagine a piece of indented 80 column wide XML that doesn't somehow curl up on the right edge. It's certainly not for me, but I won't tell you…
>And, more important… does it matter? If author wants to continue using CF for his own reasons, that's fine but it's still worth knowing why others care about popularity : 1) job prospects - e.g. knowing Javascript will have more relevance in job hunting than knowing Microsoft's VBScript that was used in Internet Explorer 8. 2) large community that has seen similar problems and can provide answers to copy&paste code…
OTOH, all reasons are cons... an expert in an esoteric system with none of those will be paid her weight in gold by the fewer employers in need of a very finite resource... while js programmers are a dime a dozen.
I worked with these guys. I always use them to remind myself that no matter how the powers that be kiss my ass right now they'll have no problem paying me shit even if it means incredibly short sighted moves like sticking with a system with an ever dwindling set of devs.
I put in a small amount of study time refreshing myself on this tech.. waiting for the day they're all dead and I can name my price. I'm not counting on it though.
Earlier quoted context omitted.
OTOH, all reasons are cons... an expert in an esoteric system with none of those will be paid her weight in gold by the fewer employers in need of a very finite resource... while js programmers are a dime a dozen.
If one language is expensive, and another language is cheap which do you think employers will be building NEW software in? I've seen people who follow the strategy you prescribe, and while they did make above market while they helped companies migrate away from [dying technology] they eventually became unemployable. It simply isn't a good long term play, for either employee or employer.
> "Whilst y'all dimwits call us unpopular, we're busy running the world - from health and banking to government and Telco companies. Adobe's Evangelism Kit points out that Coldfusion is utilized by over 70% of the Fortune 100." this is unprofessional and doesn't help drive your point. You're arguing that "dimwits" perceive popularity as a good measurement of the value of a language, and then you point to the language…
>Ha ha! I hardly ever write new code and spend almost all my time patching bugs created by a self taught 90s webmaster who works in a totally different industry these days! Aren't U jealous??
Earlier quoted context omitted.
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. (Certainly there are workarounds to such technical projects in…
Both PHP and ColdFusion have frameworks (Laravel and Coldbox for example) to address this. Without Rails or Sinatra, Ruby web apps would have the same problems.
Ruby wasn't built to be embedded inside HTML, so I don't Ruby would have the worst problems of classical PHP even if Rails didn't exist, just as Perl (which both PHP and Ruby took inspirations from) even at its worst CGI architectures never quite had the same raw architecture problems that were rampant in early page-based mixed HTML and PHP design. 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.
Is there something we can do to the title to distinguish the Coldfusion language with nuclear cold fusion? The title seems applicable to both and even the first paragraph could be misleading if you assumed the latter.