No.22118
"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."
- Guy Steele, Java spec co-author
No.22132
There is no language without macros. Programmers will either poorly reimplement eval or suddenly start to write m4 or even C preprocessor.
No.22139
>>22118I know Guy Steele definitely has some idea what he was talking about when he said this since he literally made scheme and was involved with Common Lisp standardization efforts but I really have no idea what he could have meant by this
No.22140
>>22139Just some guesses from the top of my head:
>garbage collection<unheard of at the time in general purpose languages outside of lisp and smalltalk>dynamic typing<casting between sub- and superclasses<before generics many data structures casted specific types into generic objects and vice-versa>strong typing<exceptions on invalid casts>bytecode<native compilation as a form of caching>kitchen sink standard library<see greenspun's tenth law No.22145
>>22142Forth programs will hate you, they spent years thinking that everything is a stack and routine in reverse polish notation. It is still used because it is one step above assembly.