is marked as deprecated on Lucee (ref: https://docs.lucee.org/reference/functions/valuelist.html). Is it really for Lucee to be deprecating something in CFML, given it's up to Adobe what is and is not deprecated in their language? What's the perceived gain in marking it thus, other than making devs writing cross-platform from going "oh FFS". Which to me is not a gain.
(yes, I have read https://docs.lucee.org/reference/deprecated.html. That is not what I am asking).
sknowlton02/18/2022, 12:47 PM
websolete02/18/2022, 1:52 PM
Matt Jones02/18/2022, 2:21 PM
sknowlton02/18/2022, 6:38 PM
websolete02/18/2022, 6:51 PM
bdw429s02/18/2022, 7:43 PM
unclear what the motivation for deprecating something as uncontroversial as valueList isThe answer is more simple and boring them you may imagine. And is solely that the functionality of
overlapped with that of
so it was "necessary" (per Micha) to ensure one of the two was deprecated.
also, weren't we supposed to have the 'lucee language' by now? is that not on the books anymore?LuceeLang was put "on the shelf" indefinitely quite a few years ago when LAS realized they didn't have near the resources to keep up with normal Lucee CFML, let alone an entire new language with • no docs • no frameworks • no users • no formal language spec • no public mindshare and until they came into a few million dollars of lottery money, it just wasn't going to be feasible.
or whatever (and I've had clients refuse to allow me to use it!) just because Micha flipped a coin once 8 years ago and decided he like
instead as his personal preference.
websolete02/18/2022, 7:52 PM
bdw429s02/18/2022, 7:52 PM
websolete02/18/2022, 7:54 PM
bdw429s02/18/2022, 7:57 PM
websolete02/18/2022, 7:57 PM
bdw429s02/18/2022, 7:57 PM
websolete02/18/2022, 7:58 PM
setVariable("hypocrisy","for the win");
Personally, I never saw anything wrong with having two ways to accomplish the same thing and I really wish Lucee had never felt the need to slap a deprecation label on anything just for the sake of a "_their can only be one_" sort of attitudeAgreed. Also: not his decision. Micha (et al) really need to get that these choices are not even theirs. It's Adobe's language. They are doing everyone a disservice (and being self-indulgent) by thinking otherwise. If you wanna copy someone else's work then by all means do it. But do that.
because Micha felt it improper to ever have two ways of doing the same thing. i.e., two BIFS that accomplish the same task.Following this logic, the BIF is
should never have been created in the first place.
Whether or not it's a better implementation (it is) is neither here nor there, following his own premise
should never have been created.
And "deprecating" the one that is common to both "dialects" in favour of his own special one is simply misapplied hubris.