Live data from Hacker News

JavaScript: The Right Way

jstherightway.org

21–30 of 136 posts

Re: JavaScript: The Right Way

#21
post #5

Nice, I like what you're trying to do, but things like "Backbone.js: The most popular JS client-site framework" worry me. Most people I talk to avoid Backbone nowdays in favour of the other popular frameworks. Also: some descriptions appear to be lacking/missing & you definitely should mention Grunt under "Helpers". At least it's a GH repo and I assume you'll accept PR's? ;)

The most popular one right now is probably Angular. http://www.google.com/trends/explore#q=angularjs%2Cbackbonej...

As anther poster mentioned, search may not be an indication of popularity.

Personally, I've used Backbone, Angular and now Ractive, and I spent at least 10x the time Googling when using Angular.

Re: JavaScript: The Right Way

#22
"JavaScript has strong object-oriented programming capabilities"

What would be an example of a language with weaker OOP capabilities?

PS: "The bad parts" section did not fit the page?

Re: JavaScript: The Right Way

#23
Having recently started getting into Javascript, I have to say it is the most confusing ecosystem ever. Learning the basics of the language is easy enough, but as soon as you start trying to create a non-trivial application, bam, you're hit with information overload - X framework, Y library. It's different from Python, Ruby et all because at least with them, there are good consistent popular choices that you can rely on. With Javascript, more often than not, I'm left scratching my head as to what I should exactly use.

:/

Re: JavaScript: The Right Way

#24

Having recently started getting into Javascript, I have to say it is the most confusing ecosystem ever. Learning the basics of the language is easy enough, but as soon as you start trying to create a non-trivial application, bam, you're hit with information overload - X framework, Y library. It's different from Python, Ruby et all because at least with them, there are good consistent popular choices that you can rely…

If in doubt, just use Javascript without anything. Maybe add jQuery.

All those frameworks may be nice, but as soon as the tools get a distraction, I think it is useful to step back. And JS doesn't really need anything to be useful.

Re: JavaScript: The Right Way

#26
post #24

Having recently started getting into Javascript, I have to say it is the most confusing ecosystem ever. Learning the basics of the language is easy enough, but as soon as you start trying to create a non-trivial application, bam, you're hit with information overload - X framework, Y library. It's different from Python, Ruby et all because at least with them, there are good consistent popular choices that you can rely…

If in doubt, just use Javascript without anything. Maybe add jQuery. All those frameworks may be nice, but as soon as the tools get a distraction, I think it is useful to step back. And JS doesn't really need anything to be useful.

I'd say underscore needs to be there too

Re: JavaScript: The Right Way

#28
It funny, but clicking to this link caused high CPU usage for N seconds and message from Firefox:

A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.

Script: http://jstherightway.org/js/jquery.js:1144

Re: JavaScript: The Right Way

#29

Having recently started getting into Javascript, I have to say it is the most confusing ecosystem ever. Learning the basics of the language is easy enough, but as soon as you start trying to create a non-trivial application, bam, you're hit with information overload - X framework, Y library. It's different from Python, Ruby et all because at least with them, there are good consistent popular choices that you can rely…

There's a lot of choices, and that's not a bad thing necessarily. Javascript is in a heavy growth period right now. But I totally get the choice overload thing. There's a lot of people interested in javascript from all different areas of computer land, and they all have different ideas of what "best" is, and they all want to make javascript more like lisp, or more like ruby, or more like java, or more like c# or more like flash, and so on and so forth.

If you just need a choice, somewhere to start. I'll make some choices for you. Here's the zen selection. My view of the standard javascript library:

jquery ($)

underscore (_)

mustache ({{}}) (possibly accentuated by iCanHaz)

Backbone (Backbone)

And that's your basic starter pack. It's a confused ecosystem because it was only since about 2007 that people started to realise that javascript was an actual programming language and not just a stupid toy. I remember that year chatting with people on #javascript on IRC who simply didn't believe that I had an actual full time job writing server side javascript. the idea seemed too absurd. And so here we are, a mere 7 years later and we've pieced together a very humble ecosystem in the face of that level of bald hatred and misunderstanding. I remember it wasn't so long ago that flash was in a similar position, and not long before that, java, with its popular image being its slow crummy applets.

So, yes, in conclusion, you're right, and it's because it's young and every language goes through this stage.

Re: JavaScript: The Right Way

#30
post #26
post #24

Earlier quoted context omitted.

If in doubt, just use Javascript without anything. Maybe add jQuery. All those frameworks may be nice, but as soon as the tools get a distraction, I think it is useful to step back. And JS doesn't really need anything to be useful.

I'd say underscore needs to be there too

And this is exactly how it starts :-)
Post reply on HN