undefined | Better HN

0 pointsbearcherian4y ago0 comments

If you're main problem with a new language is that it's not written like the language you are used to, you're not going to be happy with the new language.

0 comments

8 comments · 3 top-level

Aeolun4y ago· 4 in thread

Hence I’m not happy with anything that doesn’t look like Java.

Go seems amazing otherwise, but I cannot get over the fact that it forces me to capitalize or not capitalize my variables, and has types in the wrong order.

rob744y ago

Well then I guess it's Java for you until retirement. Go can feel a bit alien if you only know "C-style" languages, because its creators took inspiration from a wide array of languages, including Pascal. Actually Pascal-style declarations are easier to read, but you have to keep an open mind and not just go "doesn't look like what I'm used to, so it must be bad"...

runarberg4y ago

C/Java style of annotating the return type of a function first, and then annotating the argument types before the name feels really old school at this point. Python, TypeScript, Go, Rust, etc. all opted for annotating after the name.

Since this is so prevalent in newer languages, despite a pretty strong tradition in the other direction, I wonder if there is a pretty good reason for this which language design experts are keenly aware of when they design new languages.

2 more replies

zerocount4y ago

I can't stand the capitalization thing. I see this in C# methods and boolean values in Python every day and it sucks. I think Java got it right on that one.

skybrian4y ago