121–130 of 322 posts
Javascript. Not to remove it, but to make it better from the start. Current JS feels painful to me because it feels like piling hacks on top of a poorly-designed language to make it palatable. Doing it better from the start sounds amazing.
- 48-bit static IP addresses. 70 trillion should be enough. 128 bits was overkill.
- Nodes, not interfaces, have IP addresses, so you can use multiple paths.
- IPSEC available but initially optional.
- Explicit congestion notification, so packet loss and congestion loss can be distinguished.
- Everything on the wire is little-endian, byte oriented, and twos complement.
- You can validate a source IP address by pinging it with a random number. If you don't get a valid reply, the IP address is fake. Routers do this the first time they hear from a new address, as a form of egress filtering. This contains DDOS attacks.
- Routers will accept a "shut up" request. If A wants to block B, it sends to a router on the path, the router pings A to validate the source, and then blocks traffic from B to A for a few minutes. This also contains DDOS attacks. Routers can forward "shut up" requests to the next router in the path, for further containment.
- Fair queuing at choke points where bandwidth out is much less than bandwidth in.
- Explicit quality of service. At a higher quality of service, your packets get through faster, but you can't send as many per unit time.
- No delayed ACKs in TCP.
- Fast connection reuse in TCP.
- Mail is not forwarded. Mail is done with an end to end connection. Mail to offline nodes may be resent later, but the sender handles that. Mail, instant messaging, and notifications are the same thing. Spam is still possible but hard to anonymize. If you want your mail buffered, use an IMAP server at the receive end.
- One to many messaging uses a combination of RSS and notifications.
- Something like Gopher should be available early. The Web would not have fit in early machines. but Gopher would.
The most basic problems seem to be: 1. Everything being 'free' by default drives us to ad-supported centralized services. Economics aren't a separable concern. 2. Too few IP addresses. (At least one of the pioneers, I forget which, said he pushed for longer addresses but was overruled. So the technical constraints probably did not force this.) I'm not sure how to fix #1, but here's an approach from the 90s: https://c…
(html (head ...) (body ...))
Javascript. Not to remove it, but to make it better from the start. Current JS feels painful to me because it feels like piling hacks on top of a poorly-designed language to make it palatable. Doing it better from the start sounds amazing.
I'd give it a better name, which does not involve the word "java."
Pondering the implications is left as an exercise for the reader.
Earlier quoted context omitted.
I think they were being sarcastic, given that they're writing it under a pseudonym.
Are cellphone numbers a dystopia?
Failing that, Flash should have become open source and part of the W3 web standards, but opened up such that we could observe the code that's running.