structural typed, concurrent, interfaces and dynamic arrays, why #golang of course i literally was using this type of language 30 years ago, aside from assembler and BASIC there was this language Amiga E, which was a lot like a blend of pascal and C, and that's what Go is... C style, but pascal mind, and Pike concurrency using coroutines and atomic queues the formalism and irrelevancy of so much of the stuff in these languages i listed does nothing but create friction against the free flow of thought about how to actually implement something saying features like objects and macros are helpful in languages is like filling your house with water and then saying that people who don't want to slosh around in water all day long and constantly have problems with fungus are crazy