This is such a tricky subject.
On the one hand, it's laudable to want to move the language forward and to
cut and slash the cruft along the way, modularizing where it makes sense,
etc. Personally, I am 100% for this.
However, I imagine - and perhaps I am completely wrong - that Lucee hopes
to (eventually anyways) grab members from the ACF community to "seed" its
base. Those of us who migrated over to Railo years ago have no problem
making this move, but it has always been a rather painless transition from
a codebase perspective primarily due to the backwards compatibility. Over
the years I've witnessed person after person post to the Railo forum about
being on ACF 8/9/etc. and moving now to Railo, etc. - rarely (ever?) have I
seem similar posts from someone outside this already small community post
in that forum.
So, while stripping away a lot of cruft and paring down and branching out
in new directions and being less concerned with backwards compatibility,
etc. sounds wonderful to me, personally - and to those who've already made
the switch or at least played in these waters - I wonder how likely it is
to be an impediment or pause for concern for those still in the ACF
community to make the jump or even test the waters?
Getting management to try something new is rarely an easy task, I would
presume that from a Lucee product marketing standpoint the desire would be
to make that barrier to entry be negligible/non-existent? That management
team needs to balance the cost of preservation of investment (existing
codebase) vs. cost of switching... were I in that position, I think the
greater that cost of switching, the more likely I would strongly consider
another more established language that would make my business life simpler
- and frankly more stable - down the road.
What's the plan to garner that all-important critical mass to get this
thing to the next level and beyond?
So as I said, I am of two minds here: I want the lean, mean, modular,
innovative, fast, hip machine that Lucee could become - indeed I am excited
for it! But I'm also concerned that as a niche of a niche of a niche, it
may just be me and a few others who will be playing with it.