Live data from Hacker News

Poll: Preferred alternate JVM language

thecodegeneral.wordpress.com

21–28 of 28 posts

Re: Poll: Preferred alternate JVM language

#21
post #12

I know this is about the alternatives, and I'm probably absolutely mad, but I still prefer Java over all the new alternatives. It still feels "solid" and dependable and without much fluff.

http://stackoverflow.com/questions/2952732/samples-of-scala-...

I only have one comment to reply to that with:

null, Null, None, Nil

At least I know which null I'm referring to in Java!

Re: Poll: Preferred alternate JVM language

#22
post #21

Earlier quoted context omitted.

http://stackoverflow.com/questions/2952732/samples-of-scala-...

I only have one comment to reply to that with: null, Null, None, Nil At least I know which null I'm referring to in Java!

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...

Re: Poll: Preferred alternate JVM language

#23
post #21

Earlier quoted context omitted.

I only have one comment to reply to that with: null, Null, None, Nil At least I know which null I'm referring to in Java!

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...

I'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.

Re: Poll: Preferred alternate JVM language

#24
post #15

I did vote on Scala, but actually I would rather that we return to languages that compile direct to native code.

I agree, I much prefer native compiled languages. I really like clojure and used it for about a year. I stopped because In doing a lot of embedded development so I need to use C and Ive been using C++/qt for desktop gui apps. Since then, though, Ive been kinda put off going back to clojure because its not native compiled even though I like the language itself.

There quite a few Lisp environments that compile to native code as well. Have you explored that route?

Re: Poll: Preferred alternate JVM language

#25

A rather useless question. The word "prefer" is much too vague. I'd be rather interested in how much experience people actually have with these languages and whether they plan to continue using that language in future projects.

The popularity of a language is important. If developers don't like a language they won't use it. Look at Ruby a few years ago as an example of a popular language which was hardly used which became on of the most widely used scripting languages in modern times.

"If developers don't like a language they won't use it."

Do you have any reason to believe that's true?

Re: Poll: Preferred alternate JVM language

#26

Earlier quoted context omitted.

Not so fast... Clojure also getting some votes.

Xtend and Ceylon faring extremely badly, Kotlin only slightly better. Looks like a 2 horse race with Scala and Clojure in front.

The JVM is already crowded.

Personally I think Xtend, Ceylon and for that matter Kotlin are "me too" languages, just trying to get some piece of the pie, and most likely won't go nowhere.

Re: Poll: Preferred alternate JVM language

#27
post #23

Earlier quoted context omitted.

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...

I'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…

That'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.

Re: Poll: Preferred alternate JVM language

#28
post #24

Earlier quoted context omitted.

I agree, I much prefer native compiled languages. I really like clojure and used it for about a year. I stopped because In doing a lot of embedded development so I need to use C and Ive been using C++/qt for desktop gui apps. Since then, though, Ive been kinda put off going back to clojure because its not native compiled even though I like the language itself.

There quite a few Lisp environments that compile to native code as well. Have you explored that route?

Not really. I've toyed with both Common Lisp and Scheme and while I love Scheme for its simplicity and minimalism (at the core, anyway), in my mind they're both really quite different from what Clojure provides. Common Lisp seemed much too clunky and patched together to me, compared to how Clojure is designed to cleanly sit on top of its sequence abstraction, Clojure's notion of time and concurrency and even just how Clojure eliminates the need for some of the parentheses that are required in CL.

I'm sure its a matter of taste (and I actually do quite like Scheme, I guess just not enough to try and make it work for me right now...).

Having said that and ignoring Clojure, I also appreciate languages with a little more syntax sometimes, so I guess that's also held me back a bit. I should give Scheme or Common Lisp another try and see if I can't use it for my current work, but its hard to set the time aside, I guess.

Post reply on HN