&gt; An MIT-style language would be Rust, which indeed struggled to get to v1.0 and Go vs. Rust plays out quite similarly to what worse-is-better would predict.<p>Not having to implement a userland OS scheduler, a production-quality garbage collector, and an industrial-strength compiler backend from scratch strikes me as a fairly New Jersey-style approach, don&#x27;t you think?<p>(I think this whole &quot;Rust vs. Go&quot; as &quot;MIT vs. New Jersey&quot; argument is pretty silly. There are many factors going into why Go released 1.0 before Rust did, and both communities have consensus that you shouldn&#x27;t treat Rust vs. Go as a horse race anyway.)