They don’t, they need a framework that implements ...
# cfml-general
s
They don’t, they need a framework that implements rest like (coldbox or taffy) that way the functionality can change as the technology does, if such a solution is actually needed for their product.
a
(don't forget to use threads) Well one doesn't even need a framework I think (any more than one "needs" a framework for anything else. "should use ~", sure). My question was kind of... rhetorical. There isn't a need for an special handling for REST req/responses, so why does both CF and Lucee... have special handling for them? There must be some perceived reason for the work to have been done?
Or is it just Adobe thinking "CFMLers are too thick to be able to do REST, so we'll... um... [mutter]... LOOK NEW FEATURE!!". And Lucee just followed suit for reasons of compat?
s
my best guess, is that Adobe along with cfclient was trying to make development easier by adding features to a language that dont belong.
and then lucee tried to stay compatible
haha you beat me to the lucee answer lol
a
teeheehee...
<cfclient>
. Oh god.. I'd forgotten about that. Yeah, OK. nothing more to it than that sort of dumbarse thinking?
s
essentially, but I think its to be expected, even back to cfcollections Adobe was trying to build a one stop shop without considering that some things just don’t belong (which became apparent with versions not keeping up to date and limited customizations/settings) which led others to find outside solutions anyway
From my perspective today, the most beneficial thing that could have been done for CF is to make integration of Java libraries super smooth and then lean on the java ecosystem and cf plugin ecosystem to allow a rich environment for developing any solution
3
back in the day things like
cfinput
cfselect
cfajax
cfwebsockets
allowed me to implement cool things quickly, but left me with little option when i wanted them to do a little bit more
plus, the cf
form tags
really screwed me up because they would inject the javascript on the page at the top sometimes screwing up the formatting, etc.
rant over
f
If you were to use the Adobe’s API manager / gateway then it can autodiscover those REST services. But personally I’ve always favored avoiding the builtin rest stuff - I’ve used coldbox, taffy and noframework instead.
1
a
That UI stuff had its time. But by the time they added in all the async stuff in, it was too late: it was all dead easy to do with the early JS/CSS libs, which was always gonna be a better way to do it. This in turn created a "generation" of CFML devs - web devs - who couldn't actually do the front-end part of web development (and still frickin' can't!!). Great for vendor-lock-in I guess; rubbish for the CFML community.
e
The reason I "love" ColdFusion over many other web scripting languages is the ease of use. I admittedly am lazy and do not want to see another framework, I just want a function call. I do not care how it works under the hood until I am forced to care how it works. I like the simplicity of not having to write thousands of lines of code to do something, unlike many other languages out there.