Live data from Hacker News

JavaScript at 20

brendaneich.github.io

301–310 of 327 posts

Re: JavaScript at 20

#301

"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…

"Don't talk about it: be about it"

-Bob Burns

Re: JavaScript at 20

#302
post #154
post #14

Earlier quoted context omitted.

JavaScript is further from an ideal language than many out there.

Self was bad because prototype based languages are not intuitive. This is why we get the endless years of people trying to explain why it's good or how to use it and endless "discoveries" and "frameworks" to leverage "new" tricks. JS is a mess because it's prototype based, to start. Same reason Pony is more progressive than Erlang (Prolog syntax?).

JS is a mess because it's prototype based, to start.

It's internals are prototype based. The user-visible layer is essentially class-based, but lacks syntactic support for both inheritance and composition.

Re: JavaScript at 20

#303

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,…

>> Or, they could take their own medicine, and try and write the browser in JS. >You mean like Firefox?

This is a very strange comment, especially coming from you.

Everybody knows that the bulk of Firefox is not written in JS. You personally have spent years of your life working on a new programming language precisely because JS is not suitable for writing a web browser.

I'll take your position on JS seriously when you abandon Rust and begin writing the bulk of Firefox in JS.

Re: JavaScript at 20

#304

"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…

The simplest solution would be to specify a VM for the web - that way people could use whatever language they like. Using JS for this purpose is suboptimal.

This would require people like Eich to entertain alternatives to his diseased progeny.

Re: JavaScript at 20

#305

Earlier quoted context omitted.

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…

I think the web is getting better in this regard. Since the introduction of emscripten and asm.js there have been some improvements to the tooling and runtime to make it so you can just write your app in C or C++ without really thinking about JavaScript. It's only a matter of time before other languages can have the same level of support.

I think you are onto something ;-).

Re: JavaScript at 20

#306
post #289
post #270

Earlier quoted context omitted.

> The differences between these languages aren't that big and they're largely aesthetic. They are pretty big. At work I work on a Django-backed project that has a very fat JavaScript front-end client, and JavaScript is incredibly painful to work with compared to Python. It's not merely aesthetics, but JavaScript in the browser is severely lacking in language features that allow it to scale to larger code-bases.

I also came from a Python (Django, Flask, …) background and had the same issues. Tried CoffeeScript and it helped a little but eventually fell in love with Dart. Give it a try. I like that it comes with a useful and well designed standard library (like Python).

Thanks. I did try Dart and our team spent a full month giving it our best for our client.

It was a dream to use compared to JS. One show-stopper though: browser support. At the time, IE11 was just released and Dart had issues with IE11. Also, the Dart supported browser window is only the latest 2 versions of a given browser.

This totally killed our Dart prospects, as our target users in our business are generally non-tech savvy and we need to support older browsers like IE8/IE9.

Re: JavaScript at 20

#307

So 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…

It's just for "let" AFAICT.

Only for let, const, class, and function in block. Like the slide says!

Re: JavaScript at 20

#308
post #306
post #289

Earlier quoted context omitted.

I also came from a Python (Django, Flask, …) background and had the same issues. Tried CoffeeScript and it helped a little but eventually fell in love with Dart. Give it a try. I like that it comes with a useful and well designed standard library (like Python).

Thanks. I did try Dart and our team spent a full month giving it our best for our client. It was a dream to use compared to JS. One show-stopper though: browser support. At the time, IE11 was just released and Dart had issues with IE11. Also, the Dart supported browser window is only the latest 2 versions of a given browser. This totally killed our Dart prospects, as our target users in our business are generally non…

I hope we all will be able to target evergreen browsers sooner rather than later. Microsoft seems to go into the right direction at least.

Re: JavaScript at 20

#310

JavaScript at 20... apparently doesn't work. I load the page and get a big rectangle that says "JavaScript at 20" and "Brendan Eich" with a link to his Twitter, and nothing I do on the page takes me to the rest of the presentation.

Its insane but press the right arrow button.

That doesn't work on my personal laptop. Works on my work laptop though.
Post reply on HN