I find it very interesting that he says asm.js was "discovered" rather than "invented". Clues to a person's philosophy.
JavaScript at 20
61–70 of 327 posts
Re: JavaScript at 20
#62I find it very interesting that he says asm.js was "discovered" rather than "invented". Clues to a person's philosophy.
Re: JavaScript at 20
#63I 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.
Re: JavaScript at 20
#64I wish JavaScript "committed a teenager suicide" and we finally got a more sane language for the web. It's startling how much energy is spent to work around its bad design every day and it's not getting any better, people are just getting used to it (which is akin to voluntarily agree with having most of one's brain blown off). Even seeing Brendan showing off that he hacked the language in 10 days makes me sick to th…
> I wish JavaScript "committed a teenager suicide" and we finally got a more sane language for the web. While javascript has obvious flaws, nobody would ever agree on what a sane language would be. I would also say that, personally, I think that how the DOM is implemented is itself the biggest pain point of web development, not really javascript.
My biggest gripe would actually be CSS. I mean, wtf.
Re: JavaScript at 20
#65Earlier quoted context omitted.
"Always bet on JS" is short for "There have been dozens of challengers to JavaScript over the last 20 years, and they have all failed to gain traction". What part of that statement is incorrect?
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…
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 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.
Re: JavaScript at 20
#66Cool presentation, but holy shit, taking ~2 minutes to load on FF and freezing the browser is not.
Re: JavaScript at 20
#67But could you please fix the damn boolean logic? And while at it, get rid of most implicit conversions.
Or forget all those features and bake in a macro system, so that we can fix anything without having to wait for the next ES[N] standard to get adopted.
Re: JavaScript at 20
#68I never understood why HN likes slideshows so much. Am I the only one who finds them completely, 100% useless without the audio of the presentation?
Re: JavaScript at 20
#69Re: JavaScript at 20
#70I wish JavaScript "committed a teenager suicide" and we finally got a more sane language for the web. It's startling how much energy is spent to work around its bad design every day and it's not getting any better, people are just getting used to it (which is akin to voluntarily agree with having most of one's brain blown off). Even seeing Brendan showing off that he hacked the language in 10 days makes me sick to th…