3 ms·
Very important feature that. I usually choose my language based on such important considerations. Busy deleting my Scala code as I write this and rewriting it i
by thevegetarian 15y ago
Very important feature that. I usually choose my language based on such important considerations. Busy deleting my Scala code as I write this and rewriting it into Java code 5-10 times the size so I don't have to suffer from being confused between null and None. Something in the back of my head tells me it has something to do with the infamous null pointer exception...
- bwarp 15y agoI'm not confused between null and None. That's obvious and wholly pointless. You should know that you must initialise all types to a default value. Then you don't need a language feature for "None". Being lazy or stupid is not a reason to add a language feature. Oh and none of my code has thrown an NPE for over 10 years. That was when I started using pre and post condition checking which ultimately solves a lot more problems than some language feature. There is nowt wrong with null, if you truly understand what it is.
- thevegetarian 15y agoThat's a lot like arguing that since my C++ code hasn't segfaulted or leaked memory in 10 years that garbage collection in Java is essentially pointless. I also don't see much need for classes in that new-fangled C++ thing since my assembler code has a "solid" feel to it and has worked reliably for years. Being too lazy to initialize registers correctly is not a reason to add more features.