2 ms·
specially to dispel the idea C or C++ are required to be anywhere in a compiler stack. According to the sibling comment, the compiler is written in Java. The J
by userbinator 7y ago
specially to dispel the idea C or C++ are required to be anywhere in a compiler stack.
According to the sibling comment, the compiler is written in Java. The Java compiler is written in Java and runs in a JVM which is itself written in C/C++, and we all know how C compilers were created...
- pjmlp 7y agoAlmost there, then a wrong turn. Java has multiple implementations, some of them happen to be fully done in Java, like JikesRVM, MaximeVM and Graal. Naturally you might say, that you only care about OpenJDK, which incidentally now has the Project Metropolis with the long term roadmap to use Graal and SubstrateVM to replace those C/C++ parts. As for C, many probably aren't aware that BCPL was originally designed to bootstrap CPL, a memory safe systems programming language based on Algol, which due to mismanagement never took off, while BCPL bare bones as it was, took a life of its own. Also well into the mid 90's there were quite a few OSes where C was still far from doing its mark, thus it was not even an idea to use it when bootstrapping a compiler.
- coldtea 7y ago>Java has multiple implementations, some of them happen to be fully done in Java, like JikesRVM, MaximeVM and Graal. Yes, but most of them, including Graal atm, are insignificant curiosities (as far as developers working with them are concerned. If they were a different language, they wouldn't even be on TIOBE 100, whereas Java in C/C++ is in the top 5). So pointing them out gives mainly "well, actually" pedantic points, than illuminates any real importance they have.
- pjmlp 7y agoJava the programming language is in the TIOBE top 5, not OpenJDK. Just like we don't have gcc, clang, msvc, whatever-cc on the TIOBE top 5. Apparently mixing languages with implementations keeps being a thing. Maybe we should also start arguing that C requires C++ to be implemented, given that all major mainstream C compilers are now written in C++.
- coldtea 7y ago>Java the programming language is in the TIOBE top 5, not OpenJDK. Yes, I'm obviously familiar with the distinction between language and implementation. My point is that regarding Java, it doesn't matter, as there's a single (well, 2 if you count Oracle - OpenJDK as different) and an insignificant assortment of others. The concrete implementation of "Java the programming language" actually used by enough people to put it in the TIOBE index is the Oracle/OpenJDK one. If we took all the other Java implementations mentioned, called them a different name (e.g. Jakarta) and added their users together, the new "language" user-base wise, they wouldn't even have made it to the Top 100. (Google's Java-copied Android APIs aside of course -- those do have tons of users and matter) >Apparently mixing languages with implementations keeps being a thing. Apparently the distinction between language and implementation is pedantic in most cases, where the alternative implementations are niche products and hobby projects, and as far as one is concerned Java is 99.9% a specific implementation.
- pjmlp 7y agoIt is a little more than two. OpenJDK, IBM J9, PTC, Aicas, Ricoh, Xerox, Gemalto, SAPVM, GraalVM (delivering your tweets) Niche products that have been in business since Java is around, which are a couple of years now. So they do matter, on a age where many developers don't want to pay for software while feeling entitled to be paid for. Yes it is pedantic, which is why Linux happens to be written in GCC C, not C. Good luck compiling it with another ISO C 100% standards compliant compiler. Regarding TIOBE, neither Ctrl+F Oracle nor Ctrl+F OpenJDK turn out to find anything, just plain old Java, zero references to implementations. https://www.tiobe.com/tiobe-index/programming-languages-definition/ https://www.tiobe.com/tiobe-index/programming-languages-defi...
- coldtea 7y agoI usually don't pay attention to names on HN (usually answer blind or don't remember if I talked again to someone), with a few exceptions that have a distinctive style or comment very frequently. I can almost always tell when I'm reading something from you based on two things: 1) It will mention some experimental/research languages from the 60s-90s (if Oberon is mentioned, there's pjmlp for example). 2) It will mention some otherwise niche commercial compilers/IDEs. I enjoy that you dug into all this history, and remind people of the legacy and innovations of all those research/minor/forgotten languages. And that you also remind people that paying for software can help sustain some high quality products we don't have as FOSS at all (though it's a bitter pill to swallow when you're a student for example, or a programmer making much less than the US/EU devs somewhere else in the world, not a consultant where the customer pays for your software). But, personally, I find that you have a tendency to not account for the niche factor, and all it means, talking about some products/languages/implementations as if they're an equally valid and even common choice with the stuff people actually use. E.g. "Who said Java doesn't do X? There's the commercial JVM/compiler "Foobar" that does X!", yeah, only that has like 1000 users and costs $10K, and 99.999% of the people when they want Java to do X, they want the Java implementation they actually use to do it. So my comment above was in that spirit... >Regarding TIOBE, neither Ctrl+F Oracle nor Ctrl+F OpenJDK turn out to find anything, just plain old Java, zero references to implementations. Missed my point, the "plain old Java" in TIOBE depends on programmers using particular implementations, not the abstract idea of Java or the Java specs. And those implementations are Oracle/OpenJDK by a far far far margin. If you take the companies programmers that use Oracle/OpenJDK out of the picture, remove their Google searchers, Stack Overflow questions, blog posts, conventions, job postings, etc there wouldn't be any mention of Java on the TIOBE index, even if there would still be 20+ additional implementations. Same way that if the Python community was reduced to just the PyPy users, Python would be nowhere in TIOBE -- even though TIOBE says "Python" and not "CPython".