Live data from Hacker News

We Should Stop Using JavaScript According to Douglas Crockford (2023)

old.reddit.com

1–10 of 77 posts

Re: We Should Stop Using JavaScript According to Douglas Crockford (2023)

#2
20 years ago, I was advocating for javascript.

0:03 My story was that javascript is a much better language than anybody knows.

0:10 And that if we use it properly, we can do amazing things about it and it can change the world and in fact that happened.

0:19 But now my evangel is that we should stop using javascript that it has so many congenital defects.

0:28 It really is a smelly language.

0:31 There's just a lot of crap in it and it still may be for its field of application, the best language in the world for doing that kind of stuff.

0:44 But that's not good enough.

0:45 We should be moving on to the next generation of languages.

0:48 It used to be that we'd get a new computer languages about every generation I started with FORTRAN and then C and C and java and javascript and so on.

1:01 And then it kind of stopped.

1:03 There are still people developing languages, but nobody cares, one person can make a programming language, a really good one, but you can't get adoption for it.

1:12 There are lots of terrible mistakes in the way that the web works in the way our operating systems work.

1:19 And we can't get new ones.

1:22 We're just stuck with this crap and, and they keep piling new features on everything and the new features always create new problems and it doesn't have to be like that.

1:33 We could be using really clean operating systems with really clean languages and really clean runtime and doing all this stuff in a much more reliable way.

1:45 But, but we don't seem to want to do that.

1:49 I've done javascript for a generation.

1:53 It's time for the next thing.

1:55 I, I don't think that should be AAA, considered a radical point of view.

1:59 I think it should be a normal evolutionary, view.

Re: We Should Stop Using JavaScript According to Douglas Crockford (2023)

#4
post #3

How about making WASM actually work for its target use-case (the browser) rather than needing to be chaperoned around by Javascript stubs?

https://andrewarrow.dev/frame/wasm everything I do now for the web is backend go, AND frontend go wasm

Re: We Should Stop Using JavaScript According to Douglas Crockford (2023)

#6

20 years ago, I was advocating for javascript. 0:03 My story was that javascript is a much better language than anybody knows. 0:10 And that if we use it properly, we can do amazing things about it and it can change the world and in fact that happened. 0:19 But now my evangel is that we should stop using javascript that it has so many congenital defects. 0:28 It really is a smelly language. 0:31 There's just a lot of…

> It's time for the next thing.

It's https://caniuse.com/wasm

Re: We Should Stop Using JavaScript According to Douglas Crockford (2023)

#7
post #5

Sharing a reddit link for the purpose of sharing a youtube video seems weird. WHat's the point of that? Is it to game the HN algorithm somehow?

~that's a reddit video~

update: confirmed it's a youtube video posted to reddit

I was able to download it with:

yt-dlp "https://www.reddit.com/r/programming/comments/1eht39z/why_we..."

The point is the comments on reddit, this is a big news story.

Re: We Should Stop Using JavaScript According to Douglas Crockford (2023)

#9
post #3

How about making WASM actually work for its target use-case (the browser) rather than needing to be chaperoned around by Javascript stubs?

https://andrewarrow.dev/frame/wasm everything I do now for the web is backend go, AND frontend go wasm

I think what the original comment means is that WASM is heavily sandboxed in the browser environment, and cannot interact with the DOM APIs directly. You still need JS for that.

Re: We Should Stop Using JavaScript According to Douglas Crockford (2023)

#10

Earlier quoted context omitted.

https://andrewarrow.dev/frame/wasm everything I do now for the web is backend go, AND frontend go wasm

I think what the original comment means is that WASM is heavily sandboxed in the browser environment, and cannot interact with the DOM APIs directly. You still need JS for that.

not all all. I just have:

    document.addEventListener("DOMContentLoaded", function() {
            const go = new Go();
  WebAssembly.instantiateStreaming(fetch("/assets/other/json.wasm.gz"), go.importObject).then((result) => {
                go.run(result.instance);
                WasmReady('welcome.html');
            });
});

and

and that's it! Then from go there's nothing I can't do in the DOM.

Post reply on HN