Java is a Crypto-Lisp

Java sucks because it was designed by the Lispers James Gosling and Guy Steele.

The Lispers wanted the work and money that went into Java to benefit Lisp, unlike classical programming languages that would widen the gap even further. How can these Lispers get industry to fund garbage collection optimization? They created Java. Java also intentionally sucks in many more ways, which are designed to make dynamic typing, functional programming, and garbage collection more appealing.

There's also a Hegelian dialectic element there. OOP was the next big thing because it was better than functional programming. For example, Eiffel is OOP but it doesn't have the problems Java does. When people were talking about OOP, they meant languages like Eiffel and the overall OO design methodology. Java was created when the OOP hype was high to exploit the popularity of OOP.

The scripting languages like Perl, JavaScript, Ruby (MatzLisp), and Python are all garbage-collected Lisp dialects. They're all garbage too, because they're Lisp. Uninformed ``script kiddies'' think Lisp is good even though it's basically the same as JavaScript.

C is also garbage, but Lispers like it because it helps them implement Lisps and pushes people towards these Lisps. Anything beyond basic pointer arithmetic is unusable, which is why scripting languages are so much more popular now than they used to be.

Lisp is not about garbage collection, it is about representing code with lists and list-processing it in macros. GC makes things a lot simpler, but it is not required. Although even GCC uses garbage collection at compile time: https://gcc.gnu.org/onlinedocs/gccint/Invoking-the-garbage-collector.html

I've added Garbage collection header.
Its actually neat and has zero overhead.
https://www.reddit.com/r/frozenvoid/wiki/void2/garbage_h

you're still regurgitating the same bullshit while it's clear you have no idea what you're talking about. the important thing about lisp is that it's dynamic and homoiconic. python and js are the former but not the latter. java is neither.

java is more or less a type-safe (inb4 haskallites arguing that it's not REALLY static or type-safe), garbage-collected sepples. if we really have to compare it to a functional language then java8 adopts many ideas from the aforementioned haskell: stream API allows for monad-like computation pipelines, Optional<?> is a lot like Maybe etc.

Sepples17 got Optionals too
http://en.cppreference.com/w/cpp/utility/optional