4 ms·

> You cannot predict the future from the presents past. Every time you open your lungs in the expectation that they will fill with 20% oxygen and nothing toxic

by tragic 12y ago

> You cannot predict the future from the presents past. 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 past is the only basis for forming expectations about the future, even if you're dealing with smaller probabilities, such as the rise and fall of programming languages. > Also, and this is an important point go was invented by Google and Google is not the cool hip company it used to be it is. Ow the complete opposite and part of orwells vision... Really? Go is obviously very trendy right now, and Angular - in my anecdotal experience - is on top in the front-end wars. Google is coming up with plenty trendy technology at the moment. Unless the Go compiler's phoning home, the Orwell stuff is just laughably irrelevant, and will be treated as such by the bulk of developers. 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. It depends on whether it allows developers to solve the next decade of engineering problems in a satisfying way, relative to its competitors. We shall see.

aikah 12y ago
> 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.

by tragic 12y ago

aikah 12y ago

> 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.