2 ms·
"And you're right: we were not out to win over the Lisp programmers; we were after the C++ programmers. We managed to drag a lot of them about halfway to Lisp.
by nabla9 11y ago
"And you're right: we were not out to win over the Lisp programmers;
we were after the C++ programmers. We managed to drag a lot of them
about halfway to Lisp. Aren't you happy?"
-- Guy Steele - Sun Microsystems Labs (about Java)
source: http://www.ai.mit.edu/~gregs/ll1-discuss-archive-html/msg04045.html http://www.ai.mit.edu/~gregs/ll1-discuss-archive-html/msg040...
- pjmlp 11y agoBack then I was disappointed with the state of C++ compilers across vendors and OSes (the standard was still being defined). Meanwhile, I also had discovered that it was possible to use a GC enabled systems programming language for writing OS (Oberon and Modula-3). And was exposed to Prolog, Caml Light, Smalltalk and Eiffel. So Java seemed a nice compromise for industry adoption. Our university adopted it right away for its distributed computing and compiler development classes. However I never liked the religiosity about a JIT, preferring the .NET way of having a choice between JIT and AOT. So I still like C++ a lot, but unless I am shaving off ms or bytes from a specific algorithm or writing portable code for mobile devices, I tend to use other languages.
- munificent 11y ago> However I never liked the religiosity about a JIT, preferring the .NET way of having a choice between JIT and AOT. I wonder how much of this comes down to the fact that Java methods are virtual by default and in C# they are not. The former makes devirtualization more important and is harder to do ahead of time.
- pjmlp 11y agoMight be. Most other OOP languages back then (mid-90's) used static by default.