JavaScript at 20 • Hacker News Board

Re: JavaScript at 20

#31

Post by brlewis » Fri, May 15, 2015, 4:46 PM UTC

sker wrote: post #23

I 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?

This one was maybe 15% useless. Most slides made sense without the audio.

Slide-size chunks of information can be a really good format.

Re: JavaScript at 20

#32

Post by theandrewbailey » Fri, May 15, 2015, 4:47 PM UTC

Rainymood wrote: post #30

Interesting, really interesting stuff, but for the love of god - PLEASE - just me use my mouse and scroll! (!!)

Ironically, if you turn off javascript, you can scroll right on through.

Re: JavaScript at 20

#33

Post by peter303 » Fri, May 15, 2015, 4:47 PM UTC

Why did they ever have to confuse the named with the Java programming language? They are quite different.

https://www.w3.org/community/webed/wiki/A_Short_History_of_J...

Re: JavaScript at 20

#34

Post by vezzy-fnord » Fri, May 15, 2015, 4:48 PM UTC

aikah wrote: post #29

bitL wrote: post #18

I 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.

Lua is a sane ECMAScript in many ways.

Re: JavaScript at 20

#35

Post by lol768 » Fri, May 15, 2015, 4:48 PM UTC

Dirlewanger wrote: post #4

Cool presentation, but holy shit, taking ~2 minutes to load on FF and freezing the browser is not.

My issue with it is that I click on the Hacker News link, step through the slides and then want to return back to the hacker news discussion to read the comments. Unfortunately, each slide is treated as a new history item and Firefox only remembers a finite amount of them so I then get stuck on the presentation with no way to get back to the site I was on before. Tempted to just inject this into each page I visit since the feature annoys me so much:

    history.pushState = function (){};

Re: JavaScript at 20

#36

Post by s_dev » Fri, May 15, 2015, 4:48 PM UTC

sker wrote: post #23

I 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 on the slides really - you're right though some of them need their context to be meaningful. Doesn't have to be audio a scrollable transcript could suffice.

Re: JavaScript at 20

#37

Post by tambourine_man » Fri, May 15, 2015, 4:50 PM UTC

I'm really curious to read this, but after crashing mobile safari more than 20 times, I've given up.

Edit: It seems to be Safari's fault, as Chrome handled it nicely.

Re: JavaScript at 20

#38

Post by macspoofing » Fri, May 15, 2015, 4:50 PM UTC

bitL wrote: post #18

I 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

You got it. ES6, ES7 are making JS look better and better.

Re: JavaScript at 20

#39

Post by vbezhenar » Fri, May 15, 2015, 4:51 PM UTC

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

Re: JavaScript at 20

#40

Post by knightofmars » Fri, May 15, 2015, 4:51 PM UTC

"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 something. I've worked with enough engineers that love to criticize every design choice made but when it comes to asking them what the better alternative is they have nothing to say. They just "know" there's a better way. Well, stop using your intuition based rationalizing that there's a problem and start using your creative and logical faculties to actually solve the "perceived" problem before presenting a criticism. Or at a minimum present a well thought out and actionable direction towards the solution.