4 ms·
> the JVM for a long time and many people have bad experiences with it And the only reason for this is that people don't have to maintain 15 yo Go code bases y
by aikah 11y ago
> the JVM for a long time and many people have bad experiences with it
And the only reason for this is that people don't have to maintain 15 yo Go code bases yet. But Go is verbose and will be a hell to maintain just like any other language that becomes 'enterprisey', just like big nodejs code bases, big rails code bases or big JEE code bases give people 'bad experiences'.
- kasey_junk 11y agoI dont disagree at all. The one thing I would say might mitigate this, is that the golang community and leaders are very much rooted in the Unix philosophy of doing one thing well. They push back very hard on things that enable code bases to get big. Its possible that golang will simply not be viable in use cases that require big code bases, and therefore won't deal with those problems. Its also possible that over time the focus on keeping things small will drift, and golang will just be Java.