The day will come when people will grumble their old 64-bit computers are still working fine and yet they are being forced to replace everything with 128-bit computers.

That seems unlikely, even even with a bus speed of 1 terabytes per second it would take over 200 days to visit all bytes in a 64-bit address space once, and with processor frequencies being stuck in the GHz range it seems unlikely we'll have processors that can consume terabytes of memory per second. Of course we can simply keep adding more processors, but transistors simply can't get smaller than one atom so there is a hard limit to Moore's law.

There are various annoying physical limitations that limit how powerful computers can be. There is a maximum information density (bits per volume), the minimum required energy to process information, etc. You can't count to 2^256.

Since you feel so strongly about this subject, and you're posting on slashdot, I'm sure you (or someone you hired?) have audited the 29k lines of code at https://a.fsdn.com/sd/all.js which get loaded on this very page (well, actually https://a.fsdn.com/sd/all-minified.js gets loaded, but I'm dangerously assuming that the former is the original version of the latter). So did you find anything suspicious? When was the last time those files got updated?

If you haven't actually inspected that JavaScript file, would you agree that your concerns are completely theoretical and that nobody is really going to bother to spend hours reading JavaScript for every new domain they visit (or spend thousands of dollars hiring a consultant to do so)? Given that the vast, vast, vast majority of people have come to like and expect the kind of behavior that scripts in the browser provide, wouldn't it be much more effective to do things such as lobby for user/browser tracking to be outlawed, inventing better tracking protection, etc.? Opposing scripts in the browser sounds like a technical solution to a social problem, which rarely work.

If you can minimized JavaScript I'm sure you can learn to read WebAssembly (with a bit of effort).

I'm speaking to the point that they will be exploited for their processing power by WebAssembly. It wasn't until recently that it became a real option.

If it's the processing power you fear, I'm sure it's trivial for browsers to slow down WebAssembly execution so it matches that of comparable JavaScript code. If cryptocoin mining through WebAssembly/JavaScript becomes so widespread that average users really start to suffer, I'm sure browser vendors will find some sort of solution. E.g. throttling scripts that originate from a different domain than the website you're currently visiting, or throttling all scripts by default and having a button that enables unthrottled execution, which can be toggled per domain or url. Or perhaps they'll take some inspiration from virus scanners and build scanners that detect cryptocoin mining code and refuse to run it (with an opt-out for the false positives?).

WebAssembly will probably change some things about the web, but I don't think the future is as dark as you predict. Perhaps we'll go through a period where things will be a bit worse, but I fully expect the browser vendors to strike back when/if things get too bad: there is market share to be gained there.

It's the most important because it's the final nail in the coffin for readable JavaScript.

Clearly you haven't been reading minified JavaScript recently. JavaScript hasn't been readable for years, and the world didn't end.

JavaScript as we know it is now over

I'd love to hear how you "know it" today, because the JavaScript served by most websites might as well have been a big binary blob.

Downthread you mention:

You're missing the point, this about more than just advanced users.

Surely that is a completely separate concern? Non-advanced users have never been able to read JavaScript. And when WebAssembly becomes more popular, the non-advanced users won't be able to read that, too. So from their perspective nothing changes.

What are you talking about? As far as I'm aware nobody is working on rewriting Firefox's javascript in engine in Rust. Various other parts? Yes, but not IonMonkey.

And if that index would be 'out of bounds' for the object as the C abstract machine understands it, that's UB, and an optimizing compiler can do very unexpected things.

Surely Apple isn't an American company! It's head office is in Ireland, and almost all of its profits are made there.

But outbound connections to port 80 and 443 are guaranteed to be allowed in almost every environment, and an attacker can usually control the remote server, including on which port it listens and which protocol it speaks. And an attacker could also easily disguise communication as normal http or https traffic. In addition, a protocol has been created, standardized, and implemented in all modern browsers designed to work around the annoying port blocking restriction: websockets. So can we all stop pretending that blocking outbound connections to certain ports is actually helpful, rather than just making things harder and less efficient for everyone, without posing a significant barrier to actual attackers?

So be it, if that is what these companies desire. But they should keep in mind that it will become increasingly expensive to keep their software running on newer machines (and their old ones will fail, eventually), and if they even require new features, it might be very hard and expensive to find someone who is willing and able to implement them. I'm not saying they should rewrite everything in a new language every few years (which would be expensive and foolish busywork), but if you're stuck to one vendor and they announce they will no longer support the language you're using, that seems like a great time to start moving on. The longer you delay updating, the more expensive it gets.

How is JavaScript even remotely comparable to a dead languages like VB or COBOL? Sure, no language will truly be dead as long as there are still applications running and being supported, but nobody in their right mind would start a new project in 'classic' VB or COBOL. Some might say the same about JavaScript, but even they must admit they hate JavaScript for a different reason.

Well given that he is paralyzed, I imagine even a small child wielding a pillow could kill him quite easily. So why don't you ask him what it's like going down any street at any time of the day, in any area, and having to worry about being mugged or raped or killed by anyone who isn't also in a wheelchair.

And how would you maintain a friendly, safe, and welcoming environment without removing people who would make that environment unfriendly, unsafe, or unwelcoming?

I think it's quite clear that 'all' involves only those people who obey the rules. If the code of conduct stated "We will exclude you from interaction if you murder anyone", would you then be complaining that they are such hypocrites because they fail to provide a "friendly, safe, and welcoming environment" for people who really like to murder?

Yes it's so terrible, that's probably why so many people who try out Rust mention how friendly and helpful the community is. A code of conduct is not like the law. When you are banned from the community (or leave it voluntarily) the code stops applying to you and you can happily complain about how unfairly you were treated on your blog, or slashdot, or wherever. There is no Rust-police that will come to your house and kidnap you. And the whole project is open source, anyone is free to fork it and start their own community.