No, I didn't mean that. I meant that since vars inline are in use and there is not too much debate about it (in Delphi community) I think it's something that was accepted, and may be asked too.
I don't think there was much choice given the forced subscription.
There are always other alternatives: don't use the new features, complain about it, don't renew teh subscription, move to another environment, etc ...
Decision about Delphi is only in the head of Embarcadero.
P.S.: I'm in favor of implementing inline vars, and I use them daily. But I understand the criticism and the position of those who oppose it.
I think it was mostly marketing. Probably on some top 10 vote list that mostly people migrating from other languages vote on as a knee jerk reaction. Marketing happy to have something relatively cheap to add to the list for the next release, as they must at least pretend to innovate for their subscription fee. Much more work is done in keeping volatile targets up to date and working (like mobile), but that is not very marketable .
I agree with you, but then again, Delphi is a paid product, and they have to somehow deliver.
In any case, there are features throughout Delphi's long history that the various "owners" have always maintained, such as maximum code compatibility, compilation performance, technology updates... and certainly also a lot of "sugar" to sweeten customers' appetites.
And then, it's worth remembering that Delphi is a product used for commercial purposes, and therefore some decisions, even if not shared, must also accommodate this aspect.
Recent
