Hacker News new | ask | show | jobs
by jshen 5351 days ago
It isn't about how much you type, but how much noise your brain has to parse when you read it later.
1 comments

My brain has to either parse or guess every time I read JS or Ruby code due to lack of information located near the subject code.

Obviously this is a neverending debate.

Nine times out of ten I'm looking at something like this.

http://jaydonnell.com/blog/2011/08/07/is-your-idea-clearly-e...

Agreed. I spend way more time in the debugger in CoffeeScript than I do with Java, simply because I have no idea what type of object I'm dealing with at that particular instant. I also tend to write pages of Java code and it runs the first time because I can read it and see exactly what it is doing before it runs. The compiler also tells me what typos I have in my code before I even have to run it.
I don't buy this for a second for many reasons. First, in Java I have to deal with a lot of other headaches. Heaven forbid I have to customize maven! Or, I'm using some annotation based framework, let's say jax-rs, and I'm trying to figure out why the annotations I'm putting on something aren't having the effect I think they should be having. Then there is the fact that my java project will likely have more lines of xml than lines of code in the equivalent ruby project.

But, at the end of the day I'll bet money that I can write a non trivial website faster with rails using notepad than the vast majority of java people can with their favorite IDE and java framework.

All of your complaints are about frameworks and tools, not the language itself.

Have you ever tried Play?

I have tried play, and my comment with a link is about the languages.
Sorry, I'm not groking what you mean. You mentioned problems with Maven, Jax-RS, and XML, then countered that with Rails in notepad.

None of these is a language, they are all frameworks and tools.