3 ms·
I remember the old gcj (GCC/Java native backend) being terrible years ago (as far as performance). I haven't looked at it since. I agree with a lot of points i
by djsumdog 10y ago
I remember the old gcj (GCC/Java native backend) being terrible years ago (as far as performance). I haven't looked at it since.
I agree with a lot of points in this article. The JVM does a lot of nice stuff for you. One of the big, non discussed, advantages of compiling to native would be removing the JVM dependency (and hence the dependency on openjdk or the terrible Oracle JVM license).
As far as LLVM, I'll agree it's a technologically impressive. Still, I feel a clear tech implementation was only partially the motivation, and the other was getting away from GPLv3/FSF licensing. That bothers me a bit. I like the GPLv3, but I feel much of the industry wants to distance itself from the licensing that essentially helped pull Linux into what it is today.
- AlphaSite 10y agoLinux doesn't use GPLv3?
- antnisp 10y agoLinux is famously GPLv2.
- georgemcbay 10y agoI suspect the parent post is aware of that but worded the post in a confusing way for a medium in which you can't use tone to convey added meaning. By "Linux doesn't use GPLv3?", I think the poster meant essentially "But...? Linux doesn't use GPLv3". In any case, the idea is a valid point. The GPLv2 and the GPLv3 are substantially different and it isn't that surprising that some people who were okay with GPLv2 terms are not okay with GPLv3 terms.
- deleted 10y ago[deleted]