> Every time you open your lungs in the expectation that they will fill with 20% oxygen and nothing toxic, you are 'predicting the future from the presents pas

> Every time you open your lungs in the expectation that they will fill with 20% oxygen and nothing toxic, you are 'predicting the future from the presents past'. The fact that one is breathing right now doesnt mean one will still be breathing 5 minutes from now. You can predict the future.You can maximize chances something happen,you just cant be sure 100%. Yet chances are that : - Business arent going to drop the JVM "en masse" for Go,just because Go is cool. And frankly , from a syntax perspective , Go is not that great. It has almost no functional features, and a very weak OO model. > I have no idea if Go is destined for really big things. But the fact that it's a small ecosystem now doesn't matter - Java was pretty small back in '95. Nothing like what the Java ecosystem is today existed before Java, that's a huge difference. And the fact that the JVM runs multiple languages makes it unlikely it will be obsolete,ever. Concurrency backed in a language is cool,but not necessary. concurrency can easily be a lib or a framework. I've been in enterprise long enough to know that enterprise likes boring enterprise languages for most part(java) and glue languages (scripting languages) because deadlines ... while Go might have been great at replacing C,which it doesnt, I still think there is some room for a safer C for system programming. I dont think Go features are interesting enough for entreprise solutions. There is nothing Go can do that the JVM cant.