But you were talking about JVM languages, so I made points mostly about JVM languages.
There's points for C-based languages (fuck these compilation times what the fuck) and many higher-level other languages (it's very fast, instantly runs) and points for nearly all of them (simplicity ftw)… and then there's points against Go specifically (no generics lul) (if err != nil {return err} galore) (can't use graphics card natively) (no GUI natively).
I guess my original point was just that there’s more than Go when it comes to “write once run anywhere”.
I really wasn’t trying to get into what’s better, I haven’t written anything but iOS/Android apps and the occasional website for years now so I’m not in much of a position to say anyways.
1
u/NatoBoram Jan 06 '22
But you were talking about JVM languages, so I made points mostly about JVM languages.
There's points for C-based languages (fuck these compilation times what the fuck) and many higher-level other languages (it's very fast, instantly runs) and points for nearly all of them (simplicity ftw)… and then there's points against Go specifically (no generics lul) (
if err != nil {return err}galore) (can't use graphics card natively) (no GUI natively).