3 ms·

" It's slower than Java, doesn't have anywhere near the same level of deep monitoring, doesn't have any live code loading capabilities, and has really bad inter

" It's slower than Java, doesn't have anywhere near the same level of deep monitoring, doesn't have any live code loading capabilities, and has really bad interoperation with other languages. " Curious, what projects have you worked on where Go's runtime performance was slow, requiring a Java rewrite? Link to your scrapped repo or didn't happen. " I use it when I need a simple script to run faster than Python," Same thing, source to a situation where Python was too slow and it necessitated a Go rewrite for you? "OpenJDK's JVM is not only the most advanced runtime environment around by a longshot," Most advanced for memory usage? I'm not sure what your point is about being "advanced". MIT theory at it's worst. "but let's not compare its power to that of the JVM" Why not? JVMs are overengineered piles. Simple is better. "It (Go) is a nice tool -- with excellent beginner friendliness -- but it doesn't offer any technical breakthroughs." And thank Zeus it doesn't. I think I've had enough "technical breakthroughs" with OpenJDK's JVM, Node.js and whatever else is being sold today. Few are building new product on Java, other than those already entrenched. Android is the biggest draw and once Go is a 1st class citizen there, expect the life to be sucked out. Even with OpenJDK's JVM being the best thing since sliced bread.

pron 11y ago
I don't think you know what JVMs do if you think they're overengineered. Go's "simplicity", while great for small apps, means we don't get anywhere near the same level of monitoring we get with Java, slower performance (though not a dramatic difference), and much less flexibility (no polyglotism, no hot code swapping, no dependency-conflict resolution) -- not that you should notice the JVM's "overengineering" if you don't need it. Besides, everything is overengineered until you need exactly what it's engineered to do. A helicopter may seem "overengineered" if all you need is a car, but if you need a helicopter, then a car may be seriously lacking. In the case of JVM vs Go, if you need large data sets in memory, interesting concurrent data structures (even concurrent hash maps), or even if you need to know exactly what your server is doing -- the JVM doesn't seem so overengineered any more. As to new projects being written in Java vs other platforms (Go included), you have no idea what you're talking about. All of Android doesn't even amount to 5% of Java developers.

pron 11y ago

I don't think you know what JVMs do if you think they're overengineered. Go's "simplicity", while great for small apps, means we don't get anywhere near the same level of monitoring we get with Java, slower performance (though not a dramatic difference), and much less flexibility (no polyglotism, no hot code swapping, no dependency-conflict resolution) -- not that you should notice the JVM's "overengineering" if you don't need it. Besides, everything is overengineered until you need exactly what it's engineered to do. A helicopter may seem "overengineered" if all you need is a car, but if you need a helicopter, then a car may be seriously lacking. In the case of JVM vs Go, if you need large data sets in memory, interesting concurrent data structures (even concurrent hash maps), or even if you need to know exactly what your server is doing -- the JVM doesn't seem so overengineered any more. As to new projects being written in Java vs other platforms (Go included), you have no idea what you're talking about. All of Android doesn't even amount to 5% of Java developers.