This heading is delightfully ambiguous: 1) we should stop using Javascript the way Douglas Crockford is using it/teaches us to use it 2) Douglas Crockford says Javascript should be not used
We Should Stop Using JavaScript According to Douglas Crockford (2023)
11–20 of 77 posts
Re: We Should Stop Using JavaScript According to Douglas Crockford (2023)
#12How 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)
#13Sharing 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)
#14Re: We Should Stop Using JavaScript According to Douglas Crockford (2023)
#15But there still isn't a technology that can do what js does. That is, distribute apps in a truly cross-platform, zero-install way. So people will keep using it at least as long as that's true.
I'm still bitter that he kept comments out of the JSON syntax out of a fear they would be used for processing directives. I want to have comments in my config files, so I've been left with having almost-JSON config files, or even weirder hacks like "_comment" properties. (which could also be used processing directives FWIW)
Re: We Should Stop Using JavaScript According to Douglas Crockford (2023)
#16There are many better languages than JS, and the browser ecosystem has shut down innovation in PLs, but there are some pretty large upsides to the era of language stability that we have now. I'm wary of incrementally improving a root layer and throwing out the enormous ecosystem of tooling and libraries in the process.
Re: We Should Stop Using JavaScript According to Douglas Crockford (2023)
#17Earlier quoted context omitted.
~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.
The reddit post is just an embedded youtube video: https://www.youtube.com/watch?v=lc5Np9OqDHU&t=1s
Re: We Should Stop Using JavaScript According to Douglas Crockford (2023)
#18Earlier quoted context omitted.
https://andrewarrow.dev/frame/wasm everything I do now for the web is backend go, AND frontend go wasm
I think GP was referring to running wasm directly rather than using (as your website does with WebAssembly.instantiateStreaming) JS APIs to bootstrap it and JS APIs every time it needs to do something with the browser's built-in functionality (like manipulate the DOM).
Re: We Should Stop Using JavaScript According to Douglas Crockford (2023)
#19Without JavaScript, all popups are gone
Re: We Should Stop Using JavaScript According to Douglas Crockford (2023)
#20Earlier quoted context omitted.
I think GP was referring to running wasm directly rather than using (as your website does with WebAssembly.instantiateStreaming) JS APIs to bootstrap it and JS APIs every time it needs to do something with the browser's built-in functionality (like manipulate the DOM).
can you link me to example that does wasm in browser without calling instantiateStreaming?