2 ms·

Thanks. > when the user base is still slim you have much more freedom to be a bit more adventurous, add and deprecate things more freely When designing a lang

by Rochus 4y ago

Thanks. > when the user base is still slim you have much more freedom to be a bit more adventurous, add and deprecate things more freely When designing a language, it's hard to get rid of the initial sins, so if in doubt, leave a feature out, so you don't regret it later; once enough people are involved with the language and writing code with it, any change that isn't backwards compatible is an imposition on everyone involved.

ZoomZoomZoom 4y ago
I agree completely. Playing the devil's advocate: On the other hand, making a whole new language is rarely a way to GTD now, it's usually an investment in the future. For surviving into that future the language usually needs the involvement of the community. And for that one has to consider what new/different/radical things does the language offer to the public to hook them on. May be it's OK to sin a little and get straight closer to v1.0? Of course, a few will hurt but they'll live.