There is something to be said for ease of distribution and deployment, as well as playing well with the larger infrastructure/software world. Smalltalk, which was one of the major progenitors of the managed environments you were talking about, didn't do the above. I think that had a lot to do with its downfall.
When your system interacts well with the larger world, this results in more "commerce" with the larger world, which tends to result in greater recognition and larger and healthier communities. It's a virtuous cycle.
Having the best, most well developed developer tools is a win for the individual developer, but fitting in well with the larger world is a win for the entire developer community. The latter is going to be 10X more visible than the former. (Also, think about which communities manage to have both!)
Also, get off my lawn.
Yeah, kids, get off my lawn! At least do enough research to know what's gone before! (Re: Alan Kay's quip about "almost a field.")
Fair enough, but I don't think you addressed the parent's concern.
Most mainstream programming languages fit in well with the larger world, that's why a lot of people use them.
They also have working debuggers, a ton of libraries and tools.
When your system interacts well with the larger world, this results in more "commerce" with the larger world, which tends to result in greater recognition and larger and healthier communities. It's a virtuous cycle.
Having the best, most well developed developer tools is a win for the individual developer, but fitting in well with the larger world is a win for the entire developer community. The latter is going to be 10X more visible than the former. (Also, think about which communities manage to have both!)
Also, get off my lawn.
Yeah, kids, get off my lawn! At least do enough research to know what's gone before! (Re: Alan Kay's quip about "almost a field.")