Continue reading this article on SitePoint
I’ve been checking out the new Java SDK 8 with the Nashorn js engine and JavaFX. Very nice. Would love to see a good article on using it and bundling apps using it.
I think JS is going to become even more popular after ES6 comes in with its improvements. I read an interesting article on the tidal wave of frameworks though. Suggested that a more atomic style of using specific little libraries for specific things might be the future.
Wow - that’s equivalent to learning how to ride a horse and cart instead of getting a drivers license.
A number frameworks and libraries - should be a number of…
Definitely. The other problem is that it will still be some time before we see this JS being used everywhere, what with slow browser upgrade adoption etc.
There’s a bit about this in one of the later chapters in the book. I defnitely think the future will be all about small modules that do one thing very well, rather than huge monolithic frameworks that try to do everthing. This will definitely be easier when the module pattern from ES6 gets adopted.
You could even put lots of different modules together under an umbrella namespace using something like Ender or a build process, effectively creating your own custom bespoke framework.
Thanks - will try to get this changed!
I actually think that most modern browsers are updating quite quickly, so this isn’t as much of a problem as it used to be.
I love JSON! It hits the sweet spot between being a human and machine readable data format. And the fact that it can be encoded as a simple string makes it amazingly portable!
(I had to add (dot) because I’m only allowed 2 links in my answer)
To start, this rand it not targeted to you personally. I like your article, it shows that JS is indeed a very mature language. One that has been around for a long while. Also comparing it to Java’s all platform mission is a +1! But…
Talking about Object Oriented programming vs Functional programming in JS is simply not understanding JS.
To be honest, I’m sick and tired of all those ‘write OO in JS’-tutorials. They make for bad code, var self=this; crap and people panicking when this suddenly is not this but that, or window.
As long as people write articles about JS Objects and how to write ‘OO’ code in JS, it will stay in puberty.
You also state ‘Closure’ as being a cool feature of the language. Not sure you understand what a Closure is, nearly all languages have them, not so special imo.
A small snippet to end: typeof new String(‘foo’) != typeof ‘foo’ && new String(‘foo’) == ‘foo’. I rest my case, hard to learn
Thanks for your feedback - it’s always good to see the other side of things, and the links you sent made interesting reading.
I think that JS struggles with both an OO and functional approach, but the fact is that you can do both in JS, if you want to. I’d be interested to hear why you think the OO approach is so bad?
Yes I agree that the language itself isn’t asynchronous, but the way callbacks (and promises) are used makes the language behave as if it was asynchronous.
I still stand by my assertion that JS is a good language to learn for a first timer. I think the advantage is that people can learn JS using just their browser and it also gives them access to lots of other places to practice and see examples. Yes it has more quirks than most languages, but don’t all languages have some difficult ideas to get your head around? I think you can get the basics of programming without running into too many JS gotchas.
No more having to faff about with software such as DOSbox, just play in browser. After years of hating the language, I love it for the above sites alone!
I’ve just been reliving some childhood memories playing Chuckie Egg!
That is a blast from the past!
How many hours did I spend on that game?
I spent many childhood hours playing this - the shock when the giant bird started chasing you!