3 ms·

I'm not even sure I follow the premise of this article, perhaps someone can enlighten me. Seems like it's all based on "I don't like Javascript, so we should r

I'm not even sure I follow the premise of this article, perhaps someone can enlighten me. Seems like it's all based on "I don't like Javascript, so we should replace it because no one wants to write it"... whoa hold on a second there professor! I love Javascript. It's fast, full-featured (you can do what Flash can do in Javascript, just don't try to support IE6 -- hardly Javascript's fault), it looks pretty, it's easy to understand, it takes a lot of load off my back-end servers, etc, etc, etc. I write Javascript all day long and I'm happy about it. Anyway. I hope Javascript does get more usage, although I think it's already approaching use on 100% of websites as it is... so... mission accomplished!

robotron 17y ago
I am no great fan of Javascript but it definitely has it's place and I'm knee-deep in it at the moment. It works and is useful. Should it be used for everything? Of course not. This article is little more than a rant against a language the author personally doesn't like. That's okay. Maybe he can come up with something better.
- gdp 17y ago
  HN provides again! Why read past the first paragraph when you can reply straight away! You did see that the second half of the article was dedicated to reasonably concrete strategies that would be an improvement over the status quo, right?
gdp 17y ago
That's fine, you can keep writing Javascript. The article is about how we choose to do general-purpose computing on the browser platform. Javascript is a natural fit for a large number of applications - it just doesn't make sense to end up in a situation where everything runs in a web browser, and therefore everything would have to be written in Javascript. The alternative that is sketched in the article presents a language agnostic means of achieving much of what Javascript is used for, and some of what we might want to do with the browser platform in the future.

robotron 17y ago

I am no great fan of Javascript but it definitely has it's place and I'm knee-deep in it at the moment. It works and is useful. Should it be used for everything? Of course not. This article is little more than a rant against a language the author personally doesn't like. That's okay. Maybe he can come up with something better.

gdp 17y ago
HN provides again! Why read past the first paragraph when you can reply straight away! You did see that the second half of the article was dedicated to reasonably concrete strategies that would be an improvement over the status quo, right?

gdp 17y ago

That's fine, you can keep writing Javascript. The article is about how we choose to do general-purpose computing on the browser platform. Javascript is a natural fit for a large number of applications - it just doesn't make sense to end up in a situation where everything runs in a web browser, and therefore everything would have to be written in Javascript. The alternative that is sketched in the article presents a language agnostic means of achieving much of what Javascript is used for, and some of what we might want to do with the browser platform in the future.