Coldfusion software engineer - yes, Coldfusion. When I'm not debating the finer points of software development, I can be found pedaling furiously along a winding country road.
You sound upset that Lucee doesn't offer a funky JS calendar widget. I'm sorry. As for MS Exchange, I've simply never met such a thing (read about it in old books though), and there's a perfectly workable CFPDFForm Lucee extension. If Lucee actually wasn't a viable product, then guess what... we wouldn't use it.
I apologize for your poor experience with the community. After being bludgeoned over the head for 10 years with cries of death, please pardon us for carrying a shield. And we have a lot more experience in other languages than you'd expect.
Lest you think I'm a narrow-headed dev with my head stuck in the sand, I wrote a piece on our "Legacy of legacy". Yep, we do have work to do - as a language, as a community, in documentation and in frameworks. But it's worth the climb up, at least if you're running Lucee.
You sound upset that Lucee doesn't offer a funky JS calendar widget.
No, I remember this vividly. The client had a lot of CF servers running and it was pretty difficult to reliably migrate to Lucee from Adobe CF because of Event Gateways and the application.cfc handling issues. That + the fact that almost nobody knows unit / integration testing in the CF world. I would actually love to hear how people test ColdFusion code today.
Regardless, it was virtually not possible to save this client money on licensing with a huge upfront development cost investment. This was pure vendor lock in. Sorry. Maybe the situation has changed in the last two years.
After being bludgeoned over the head for 10 years with cries of death, please pardon us for carrying a shield.
Two years after my original post, I think that sense of carrying the shield is part of the problem. Why does one need to carry a shield? I am not golang, I am not ColdFusion, why personalizing with the technology used? Why is one bothered when someone else on the internet talks bad about ColdFusion? What emotion does it trigger?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You sound upset that Lucee doesn't offer a funky JS calendar widget. I'm sorry. As for MS Exchange, I've simply never met such a thing (read about it in old books though), and there's a perfectly workable CFPDFForm Lucee extension. If Lucee actually wasn't a viable product, then guess what... we wouldn't use it.
I apologize for your poor experience with the community. After being bludgeoned over the head for 10 years with cries of death, please pardon us for carrying a shield. And we have a lot more experience in other languages than you'd expect.
Lest you think I'm a narrow-headed dev with my head stuck in the sand, I wrote a piece on our "Legacy of legacy". Yep, we do have work to do - as a language, as a community, in documentation and in frameworks. But it's worth the climb up, at least if you're running Lucee.
No, I remember this vividly. The client had a lot of CF servers running and it was pretty difficult to reliably migrate to Lucee from Adobe CF because of Event Gateways and the application.cfc handling issues. That + the fact that almost nobody knows unit / integration testing in the CF world. I would actually love to hear how people test ColdFusion code today.
Regardless, it was virtually not possible to save this client money on licensing with a huge upfront development cost investment. This was pure vendor lock in. Sorry. Maybe the situation has changed in the last two years.
Two years after my original post, I think that sense of carrying the shield is part of the problem. Why does one need to carry a shield? I am not golang, I am not ColdFusion, why personalizing with the technology used? Why is one bothered when someone else on the internet talks bad about ColdFusion? What emotion does it trigger?