When you become too well known, or too widely used and too successful (and certainly being adopted by Microsoft means such a thing), suddenly you can’t change anything anymore. You get caught and spend ages talking about things that have nothing to do with the research side of things.
Boy isn’t that true. At the same time, in my experience ‘research’ mostly means figuring out what you can do. Note that that’s not what you should do or what you want to do, but what you can do. Productized languages, on the other hand, are mostly about taking well understood problems and trying to produce solutions. It’s an interesting dynamic and I think different people will fall on different sides of it. As for me, while coming out of grad school I would have said I would want to work on the research side, after being on the product side I can’t help that feel that most research is simply about producing abandonware that may eventually end up inspiring someone’s real solution. Personally, I’d rather be at the end of the pipeline, interacting with users and solving their problems.
This probably has as much to do with why Hoon isn’t getting much adoption as does Yarvin’s authoritarian politics.
Instead, we spend this strangeness budget on our major, core feature: ownership and borrowing.
And bat-shit crazy semicolon semantics. :-)