I find it very interesting that he says asm.js was "discovered" rather than "invented". Clues to a person's philosophy.
JavaScript at 20
21–30 of 327 posts
Re: JavaScript at 20
#22I 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 only figured this out because about a year ago I ran into a similar issue and poked around the source for 10 minutes to figure out what was going on. This time only took me 1 minute :) Of course, just like last time, after I realized it was another useless slide deck with no context I left the page.
Re: JavaScript at 20
#23I 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
#24I 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.
Thanks, I genuinely couldn't figure out how to see more than the title before I read your comment.
Re: JavaScript at 20
#25If you haven't seen a Brendan presentation, they are quite enjoyable. Last time he was playing some zombie video game in the middle of his presentation. He insisted on not killing zombies with a shovel using instead deployable automatic turrets. I'm sure he uses the shovel when he plays alone though.
Javascript's is actually growing very well and fast. It's quite surprising how soon it will have everything.
In a way it can be compared to PHP - soon it will be a giant toolbox. The difference is that every tool was chosen and added one at a time. It ends up being a very good toolbox. I'm sure productive programmers aren't complaining. Pure FP programmers can always compile their ClojureScript to Javascript. For me, ES7 Javascript is already making me happy.
Re: JavaScript at 20
#26this page crushes my iPhone's Safari, Am I the only one ?
Re: JavaScript at 20
#27So good to see String.prototype.startsWith and String.prototype.endsWith in ES6. I've ended up implementing these in too many projects. I look forward to using these in 2020 or 5 years after that, when IE 8 finally sunsets. (I joke of course, since you can use ES6 to 5 with IE 8 caveats with the modern taskrunners). EDIT: Blockscope... what? More than a few of these changes point to JS being a functional version of P…
No, because you have to use the new 'let' keyword to get block scoping. So you have to opt-in to it.
Re: JavaScript at 20
#28I 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?
Depends. Sometimes people write slideshows for internet sharing, in which case they're crappy presentations but text-heavy enough to be effective. Netflix's classic "Culture Deck" is a decent example there.
But the ones that are good for presentations--that is to say, visual interest hooks, not the info being repeated--yeah, not great unless they include an audio track or something.
Edit: this one's somewhere in the middle.
Re: JavaScript at 20
#29I 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.
Re: JavaScript at 20
#30Interesting, really interesting stuff, but for the love of god - PLEASE - just me use my mouse and scroll! (!!)