I trust specs[1], multiple implementations[2], and how easy it is to bootstrap a compiler[3].
[2]: https://gcc.gnu.org/onlinedocs/gccgo/ (even if feature parity isn't quite there yet)
[3]: Instead of requiring double-digits compilation steps that each take too long to be reasonable.
New Jersey vs. what? I read about that phrase sometime earlier but forgot the rest of it. Is it vs. MIT / Stanford / West Coast / other? implying worse is better vs. other?
is it also related to neat vs. scruffy approaches in AI?
too much in tech to keep track of it all.
but asking out of interest.
As opposed to the "MIT style".
Related: Featuritis vs. YAGNI.
source?
https://news.ycombinator.com/item?id=40997745
https://news.ycombinator.com/item?id=40184763
Among others. Again I'm not saying I agree, I'm just saying you don't see the same with Go.
Can you name 3 apps/projects that use COBOL?
-- This is akin to asking, "Quick, name 3 books written in Persian. Huh, you cant name them? Must be a dead language"
Does this imply that you see COBOL as having a trustworthy future, making it a great choice for a new greenfield application?
iow, the first part does not imply the second part.
a lang could have a trustworthy future for maintenance of existing apps, like in terms of support from vendors, while not being a very good choice for greenfield applications, due to not having modern language features and libraries.
but there is so much cobol in critical infrastructure in the world that I don't think it is going away anytime soon. Google for some relevant threads on hn about it.
there is a good chance that some services critically important to you and your family rely on software written in COBOL running on mainframes. just like for everyone else in the developed world and some of the developing world.