Monthly Archives: September 2015

Is Scala the true heir for Java?


Answer by Yang Zhang:

Here's what the JVM language leadership has to say about Scala:

  • James Gosling, one of the people behind Java, when asked "Which Programming Language would you use now on top of JVM, except Java?", gave an answer that was "surprisingly fast and very clear: Scala"…
  • Neal Gafter, Java language designer, endorses Scala in the Programming In Scala book: "Will Scala be the next great language? Only time will tell. Martin Odersky and his team certainly have the taste and skill for the job. One thing is sure: Scala sets a new standard against which future languages will be measured."
  • Charles Nutter, creator of JRuby: "Scala, it must be stated, is the current heir apparent to the Java throne. No other language on the JVM seems as capable of being a "replacement for Java" as Scala, and the momentum behind Scala is now unquestionable."…
  • James Strachan, creator of Groovy: "I can honestly say if someone had shown me the Programming in Scala book by by Martin Odersky, Lex Spoon & Bill Venners back in 2003 I'd probably have never created Groovy."…

Is Scala the true heir for Java?

What is the appeal of server-side JavaScript?


Answer by Ryan Grove:

There are several reasons why server-side JavaScript is rapidly gaining momentum:

  • It allows you to use the same language on the server and the client. This increases the amount of code that can be shared and decreases the cost and effort required to hire developers, since you don't need to hire different people to write code in different places. An expert in client-side JavaScript can quickly become an expert in server-side JavaScript. Plus, JavaScript is the most popular programming language in the world, so there are quite a few people who are already good at it.
  • It's crazy fast. Node.js (which is where most of the server-side JS buzz is these days) is an incredibly fast evented IO framework that makes it a cinch to write highly scalable network programs.
  • JavaScript is awesome. Although it has many notorious "bad parts", JavaScript is pretty awesome on the whole. It's object-oriented, dynamically typed, prototypal, and it supports lambdas and closures. This allows for rapid development and makes the language flexible enough and expressive enough to meet a wide range of needs.
  • The recent revival of the browser wars means that there are several excellent JavaScript engines all competing with one another to get faster and better. Since many of these engines can also be used to run server-side JS, this means there's a good selection of excellent JavaScript engines to choose from (although Node.js currently only runs on V8).
  • Node.js showed up at the right time. PHP, currently the most popular server-side language, has been mired in community squabbling amidst a large effort to refactor its character encoding support, while also losing developer mindshare to the many excellent Ruby web frameworks that have appeared in the last few years. But Ruby web frameworks, and the language itself, have become notorious for having performance issues and sometimes being hard to scale (although some of this perception is based on misinformation), so the appearance of a new highly performant, highly scalable evented IO framework built on top of the world's most popular programming language couldn't have been better timed.

What is the appeal of server-side JavaScript?

Miss Italia e il tizio che guarda il dito e non la luna


Al di là del Buco


di Inchiostro


E’ un pochino che non scrivo nulla e scommetto che non vi sono mancato.
Stavo giustappunto pensando di scrivere qualcosa riguardo la percezione dei corpi, solo che poi si è sollevato il gran macello riguardo le dichiarazioni di Miss Italia, e quindi.

Ragazzi, devo dirlo, certe cose mi fanno ammattire.
Ammattire nel senso che vengo colto da momenti di ilarità incontrollata, nel senso che sono proprio divertito.

View original post 720 more words

Is the “you have ruined JavaScript” article a solid argument against Angular.js?


Answer by Mattias Petter Johansson:

Angular is fine.

Yes, I do agree with the original article that Angular has an obvious Java heritage that is stronger than it needs and should be. Factories (Factory method pattern) is a pattern that is very common in most Java because of it's very structural nature, but in JavaScript it's rare that you need to use them, and it's actually more of a code smell if you find yourself making factories. However, this is just one aspect of Angular and it is in general much nicer than what came before and Angular is a necessary step in evolving JavaScript. 

The fine part about JavaScript is that it's incredibly elastic. You can code it in whatever way you want. It's few languages where you actually implement class.
This is also one of the most problematic aspects of JavaScript – unlike Java or .NET, there isn't an obvious idiomatic way to code JavaScript. When someone new to JavaScript asks "How do you make a class?" the answer is sort of "How do you want to make a class? And maybe you don't want to make a class at all?"

Angular is nicer than what came before and Angular is a necessary step in evolving JavaScript.

JavaScript has a seemingly inevitable reign as king of scripting languages, so a lot of people are flocking to it. The problem is, JavaScript itself offers no guidance on how to write it, so people look elsewhere when starting out. This is where Google entered, with Angular. It offers a clear and sort-of-familiar way of dealing with building JavaScript apps. It's built by Google, filled with Java kings of over-engineering, so it's going to be bound to have at least a few FactoryProviderProviders in it, but it's pretty okay.  Angular offers a decent way of structuring your applications.  At least it's a huge step up from Google Web Toolkit (GWT), their former Java monster. It's also a step up from Backbone, which held this crown before, that promised minimalism but in reality tended to result in surprisingly large code bases.

Just like we moved from random hacking to jQuery plugins to Backbone to Angular, I believe the culture around JavaScript will evolve again in a year or two, and leave our AngularFactoryProviderFactoryEnterpriseServices behind.

Oh, and if you like my writing, don't miss out on more of it – 
follow me on Quora and Twitter (

Is the "you have ruined JavaScript" article a solid argument against Angular.js?

Is React killing Angular?


Answer by Kamil Przeorski:

I made already 4 commercial reactJS apps (btw. ping me via email on github, I could be for hire).

1) One of the serious killer feature is server-side rendering. It's very unique and useful feature of react, especially for high-traffic websites where the user experience must be a top-notch.

2) ReactJS Reddit popularity stats are growing on average 40%+ per month (sic!)

CHECK THE reddit /r/reactjs/about/traffic GROWTH STATS:

NOTE: angularJS has stagnated in terms of popularity. Check the /r/angularjs/about/traffic as well

3) ReactJS is easier to grasp in order to be efficient – when hiring an experienced JS/angularJS an average CTO/manager wants a developer to become work-efficient in reactJS in just 7-14 days. It's not the case when you are going to learn monolith's angularjs.

You can learn a lot from my reactJS-flux starter kit (przeor/react-router-flux-starter-kit) and other my github repositories on: przeor (Kamil Przeorski)

4) Web-componization is the future: reactJS allows it so you could have more modular and clean code which saves a lot money for web-enterprises especially in bigger projects which has to be maintained for years.

A summary: reactJS is slowly "killing" angularJS because has much more opportunity in terms that it's still a young library which has a great growth rate where angularJS has stagnated.

Of course the word "killing" can't be used here literally. I believe that "react is killing angular" is a good analogy what may happen in next few years. We will see.

Is React killing Angular?

Just Bangkok Things


This Labyrinth I Roam

I have come across some really bizarre things in my month in Bangkok – enough to know that there is never a dull day in this city. Here are a few things that make Bangkok what it is –

Dry Ice Drink at Steam Pug Bangkok Smoky Drinks

AIS Scratch Card Scratch Cards for Mobile Phone Top Ups

Makura Cat Cafe Bangkok Caffiene and Cats at Cafes.

Rod Fai Market Bangkok Vintage Bikes at Hipster Markets

Seacon Square Bangkok Food, so much colourful food!

Secon Square Bangkok Roosters in Malls

Brewtopia II Bangkok Nerdy Craft Beer

Brewtopia II Freaky Graffiti

Seacon Square People colouring themselves black to represent tribals (no such thing as politically correct here!)

Rod Fai Market Bangkok Aliens – not immigrants, we are talking about the x-files variety

Rambutans Hairy, juicy fruits

Quirky Eats Bangkok Mmmm Pork

Artbox Bangkok Fish Ice-Cream anyone?

Seacon Square For all your knife needs. Not dangerous at all!

Chatuchak Market BTS Bangkok This sort of sunset every night!

Gateway Ekkamai Erm, yes.

Art Box Bangkok For when you need to mainline alcohol – the Doctor’s Order. A drip bag cocktail!

Chatuchak Weekend Market Bangkok When your mantelpiece is missing phallic shaped art!

Artbox Bangkok Markets! So many markets!

Love at First Sit Bangkok Toilet Lorries…

View original post 21 more words

Is Node.js declining already?


Answer by Alexandre Morgaut:

Maybe your question is related to recent posts like:

More globally, with the buzz, some developers considered node.js as something that might be the best and unique solution to solve almost everything. At the end, they have to figure out sometime that other technologies can be more mature or more adapted for their specific projects.

Maybe you ask it because io.js did let fear some potentially dangerous split in the community.


Regarding that:

The near future of node.js looks more to be the start of the same competition we have on client-side, than the start of a decline.

Even if it had been painful at start, the client-side JavaScript/HTML5 competition has been very productive in innovation & performances

At the difference of the client-side, we don't have to wait for the W3C, WHATWG or ECMA to be created nor to wait for the vendor leaders to be part of them.

CommonJS work stopped but we now have this Node.js Foundation with already on board representatives from:

  • Joyent
  • IBM
  • Microsoft
  • SAP
  • Paypal

but also more recently

  • Intel
  • GoDaddy
  • Digital Ocean
  • Groupon

As this foundation was just created, I would not be surprised if Mozilla, Google, and Oracle ultimately join them (and who knows… maybe also Apple).
Note also that:

JavaScript itself shows a bright future in its evolutions with things like

If we take a look at node.js Job trends, they appear to be almost non-existent compared to other one. Actually, node.js is just shyly starting to rise up

Now, looking to relative percentage grow, you see that, not only node.js is the one with biggest progression percentage,  but also that each time it started to decline, it finally grew up again a bit later.

See last updates there (you can test with other skills):
php, ruby, rails, python, java, scala, erlang, .NET, node.js Job Trends

If you look at top 10 job trends, you will see HTML5 (1st), MongoDB (2d), and jQuery (8th) which like node.js are all based on JavaScript. So even if you don't end up with a node.js Job, using it will make you learn JavaScript which will still be very valuable.

Node.js is still a young technology, and while some of its use cases might have been invalidated (at least partially), it still get regularly new use cases going on and then still has market-share it can conquers.

So, yes, node.js & npm will probably see lot of changes,
 but they should result in great enhancements for the whole community.

My conclusion is then that no, Node.js is not declining

It is now growing at a higher level, a more mature one

If you want more reading on that topic, I invite you to get a look at this article: Why Node.js is hitting the big time in Enterprise Markets

PS: All of us can contribute to enhancements of the Web platforms and Web Standards. I invite you to get a look to this other answer I wrote: What is an anonymous function in JavaScript? from which I invite the readers to vote for a better JavaScript closure scopes inspection in developer tool 😉

Is Node.js declining already?