News for hackers. Stuff that matters.
Re:Better Java – Resources for Writing Modern Java by userbinator on Saturday September 19, 2015 @09:22PM (#10246207)
Despite what he says, I don't think Hoare actually invented the "null pointer", as address 0 for "not exists" or "end of list" was probably a common convention ever since linked structures existed and independently discovered by many others. (The other convention would be the all-bits-1 value, but I'd assume that testing for 0 was easier and thus more widely adopted. Also, "0 = nothing" makes great sense.)

IMHO Optional just feels like another typical Java dogmatic overabstractionism. "Null pointer exception? So what? Just catch it." Then again, I mostly use C/Asm.

Re:Better Java – Resources for Writing Modern Java by harryh on Saturday September 19, 2015 @09:37PM (#10246247)
Given that the Option type has existed in programming languages other than Java for decades I don't think it makes sense to call it a "typical Java" thing.

I can see how a C/Asm programmer wouldn't like it though. Very different mindsets. :)

Re:Better Java – Resources for Writing Modern Java by userbinator on Saturday September 19, 2015 @11:11PM (#10246449)
The difference is that other languages which originally had the Option type don't have null, so it's the only option. I meant it's typical of Java to take features from other languages, resulting multiple slightly-different-but-incompatible ways to achieve the same thing.
Re:Better Java – Resources for Writing Modern Java by harryh on Sunday September 20, 2015 @03:19PM (#10248655)
I certainly agree that Java would be a much better language if NULL could be eliminated completely. Backwards compatibility though...

sigh

Re:Better Java – Resources for Writing Modern Java by adevine on Saturday September 19, 2015 @10:19PM (#10246335)
Yeah, Optionals came from other languages, not originally Java.

IMO the problem with Optionals is that they'll never suffice unless they are part of the language itself, like in Swift. As this article pointed out, Optionals aren't supported in any existing APIs, so you still have to do a ton of null-checking everywhere. And there is nothing that guarantees an Optional reference itself can't be null, which is why you really want language-level support.

Re:Better Java – Resources for Writing Modern Java by lomnakkus on Sunday September 20, 2015 @12:22AM (#10246552)
I'm probably being a bit too pedantic here, but strictly speaking they don't need to be part of the language at all. You just need basic support for (generic/parametric) algebraic data types.

For example, Haskell has Maybe which is not part of the language nor treated specially by the compiler in any way. It is part of the Prelude (think "standard library"), so that (basically) all libraries can agree on what "Maybe a" means.