Live data from Hacker News

JavaScript at 20

brendaneich.github.io

71–80 of 327 posts

Re: JavaScript at 20

#71
post #21

I find it very interesting that he says asm.js was "discovered" rather than "invented". Clues to a person's philosophy.

It's a minor quip.

Are numbers real? Would you say we discovered them, or invented them? Do ideas exist even if you haven't thought of them yet? If so then they are discoveries.

Re: JavaScript at 20

#72

Earlier quoted context omitted.

That's not what he's actually saying there; that's a list of technical bullet points, not market adoption. However, even if we talk about market adoption; how is Firefox OS holding up against iOS, Android, and Windows? > What part of that statement is incorrect? "Always bet on JS" from Brendan Eich really meant, for 16 years, starting in 1998 and during the time that Firefox was most influential over the future of th…

> That's not what he's actually saying there; that's a list of technical bullet points, not market adoption. The point is that if JS couldn't do these things, it would be eclipsed by a competitor. It instead grew the ability to do those things, and its competitors never gained widespread adoption. > However, even if we talk about market adoption; how is Firefox OS holding up against iOS, Android, and Windows? In term…

> The point is that if JS couldn't do these things, it would be eclipsed by a competitor. It instead grew the ability to do those things, and its competitors never gained widespread adoption.

REALLY?? JS can't do concurrency by any objective performance measure against systems providing shared state concurrency; how is a competitor going to eclipse it when the lowest-level syscall interface available to target is JavaScript?

> In terms of languages on the Web, JavaScript has always won. It's clear at this point that the Web isn't going anywhere, even though mobile apps are important.

It ought to be indicative of something that the web is faltering in market segments where programming languages do more than move DOM elements around.

Re: JavaScript at 20

#73

I have learnt that if I click a javascript post and see a title and author slash screen and nothing else apparently I must start using my right arrow button.

I think normally these are the actual slides that the presenter used. So they were created for easy presentation, not for web browsing.

Re: JavaScript at 20

#74

"Haters gonna hate." Anyone claiming that JS is the "worst thing to happen to the web" and/or that some other language would miraculously solve all of the problems present in JS should do the following, "Go create it." Don't whine about the barriers and how a new language would never be adopted because "JS is already everywhere." There are plenty of people already trying to solve this problem by actively doing someth…

There are no end of alternatives out there today, from mobile platforms to research languages exploring a myriad of aspects of computer science. Just let me know when browser vendors are going to break down the two-tiered system, and let us run the legion of alternatives alongside -- instead of under -- JavaScript. Or, they could take their own medicine, and try and write the browser in JS.

> Just let me know when browser vendors are going to break down the two-tiered system, and let us run those myriad of alternatives alongside -- instead of under -- JavaScript.

The complexity of doing that would be needlessly high compared to just improving JavaScript. Having to integrate a C++ DOM with a JS DOM is hard enough. Think about how you handle cross-language cycles…

> Or, they could take their own medicine, and try and write the browser in JS.

You mean like Firefox?

Re: JavaScript at 20

#75

Earlier quoted context omitted.

> That's not what he's actually saying there; that's a list of technical bullet points, not market adoption. The point is that if JS couldn't do these things, it would be eclipsed by a competitor. It instead grew the ability to do those things, and its competitors never gained widespread adoption. > However, even if we talk about market adoption; how is Firefox OS holding up against iOS, Android, and Windows? In term…

> The point is that if JS couldn't do these things, it would be eclipsed by a competitor. It instead grew the ability to do those things, and its competitors never gained widespread adoption. REALLY ?? JS can't do concurrency by any objective performance measure against systems providing shared state concurrency; how is a competitor going to eclipse it when the lowest-level syscall interface available to target is Ja…

> REALLY?? JS can't do concurrency by any objective performance measure against systems providing shared state concurrency

https://blog.mozilla.org/javascript/2015/02/26/the-path-to-p...

Re: JavaScript at 20

#76
post #8

I just wish the best language would win, not the accidentally ubiquitous one. And giving a real choice of language would been even better.

I spent a long time avoiding JS at pretty much any cost. Then I bit the bullet and learned how to work in it, really learned (in 2010 or so). I've liked it a lot more ever since, but a lot of that had to do with my previous ignorance to things like closures and first-class functions, which of course are not specific to JS at all.

Re: JavaScript at 20

#77

Earlier quoted context omitted.

There are no end of alternatives out there today, from mobile platforms to research languages exploring a myriad of aspects of computer science. Just let me know when browser vendors are going to break down the two-tiered system, and let us run the legion of alternatives alongside -- instead of under -- JavaScript. Or, they could take their own medicine, and try and write the browser in JS.

> Just let me know when browser vendors are going to break down the two-tiered system, and let us run those myriad of alternatives alongside -- instead of under -- JavaScript. The complexity of doing that would be needlessly high compared to just improving JavaScript. Having to integrate a C++ DOM with a JS DOM is hard enough. Think about how you handle cross-language cycles… > Or, they could take their own medicine,…

Works on OSes. We have a choice.

In browsers, the OSes of the web, nope, just a bad language designed in 10 days that resists all attempts to make it not bad.

It doesn't really matter if you like javascript, there's so many people who don't.

Why do you get to dictate whether we can or can't develop on the web? You leave us with a horrible choice, use what we consider to be one of the worst modern languages, or not develop. Why do you get to make our professional lives miserable?

Re: JavaScript at 20

#78

Earlier quoted context omitted.

> Just let me know when browser vendors are going to break down the two-tiered system, and let us run those myriad of alternatives alongside -- instead of under -- JavaScript. The complexity of doing that would be needlessly high compared to just improving JavaScript. Having to integrate a C++ DOM with a JS DOM is hard enough. Think about how you handle cross-language cycles… > Or, they could take their own medicine,…

Works on OSes. We have a choice. In browsers, the OSes of the web, nope, just a bad language designed in 10 days that resists all attempts to make it not bad. It doesn't really matter if you like javascript, there's so many people who don't. Why do you get to dictate whether we can or can't develop on the web? You leave us with a horrible choice, use what we consider to be one of the worst modern languages, or not de…

> Works on OSes. We have a choice.

The kernel doesn't have a DOM. On the Web, the number of GC'd objects that every "process" has to deal with exceeds the number of file descriptors by an order of magnitude.

Also, you do have a choice: you can compile your favorite language to JS, even low-level ones via asm.js.

> Why do you get to dictate whether we can or can't develop on the web? You leave us with a horrible choice, use what we consider to be one of the worst modern languages, or not develop. Why do you get to make our professional lives miserable?

That's not the choice: you can compile your favorite language to JavaScript. That's what source maps, asm.js, and the like are for. And JS is being improved all the time; it's not static.

Trying to add another language has been tried multiple times and has always failed, because having two languages that both interact with the DOM is much more difficult than just improving JS.

Re: JavaScript at 20

#80

I wonder whether `let` should be used everywhere now making `var` effectively obsolete? Mixing both declaration styles looks bad.

As I understand it, yes, 'var' is now obsolete. 'let' does the same thing with less confusing semantics.
Post reply on HN