It’s difficult to exaggerate the damage that has been caused to the original vision of the web through the commercialisation of domain names. Imposing artificial scarcity and the complexity of commerce systems on a fundamental identifier makes it orders of magnitude harder to self host. Domain names should be a public good. We should embrace https://www.opennic.org/ in the EU and mandate that all browser vendors implement support and get Let’s Encrypt to provide TLS support.
@aral Under what legal theory can a liberal government micromanage all browser vendors?
And we're not just talking about commercial entities here, but open source developers as well.
Food safety laws have been used to squash independent food production fairly effectively. The same will happen with open source once we start regulating software.
@freakazoid @aral the majority of web users use Chrome, from Google, or Firefox, from Mozilla which takes large corporate donations. literally what's being proposed is regulating these large corporate entities to stop them from leveraging their power to wrest money from individuals. exactly what regulation is intended to do. I fail to see the issue, nor the novelty, in this aside from being astounded that it hasn't happened sooner given the level of harm caused
You are pretty naive if you think that regulation constraints big existing players.
The problem with regulating software now ia that it is still too primitive. We would hurt innovation that occurs on free software.
The solution for these issues is very simple: cap company size. Split Google, Facebook, Amazon and friends in a few thousands little company. Problem solved.
No wait, I was there.
IE6 had 92% of the market.
I hate to admit this, but had they won we wouldn't have this dystopia.
ActiveX weren't doing much well back then. The two contenders for the "#Web as a Application Deployment Platform" were #Java Applets and #Flash.
And later, Microsoft moved to .NET and WPF: they didn't consider the Web as a viable architecture for a distributed operating system. They were right, but nobody want to admit this now (not even them).
No it doesn't.
> WASM turns the web into a viable application deployment platform.
This is not a theorem proof or a scientific result. It's just YOUR own opinion.
An opinion that is very hard to sustain technically (at least if you give a shit about users' security) but if you want we can discuss the matter: it's possible than in 20 years of Web development / deployment practice I missed something.
@walruslifestyle @alcinnz @aral @Shamar And again, we're still talking about what YOU think is a viable platform versus what app deployers would be willing to use. I'm not arguing that it's not a shit show; just that WASM is an improvement over JS that in app deployers eyes will make it sufficient for their needs.
JS is no more transparent than WASM; obfuscated JS is no easier to read than disassembled WASM.
@Shamar @aral @alcinnz @walruslifestyle I guess what I'm really trying to understand is why/how you think the computing world would have come with something better than the web for application deployment rather than just inventing an equally bad shitshow. All the other popular ones, they're all a shitshow on one or more axes.
As for #Plan9 as application deployment platform it's very simple: make everything a file system that can be transparently exported through a network and composed of several services all visible as files and folders with properly manageable permissions and visibilities and then... enjoy.
Now the user can safely export a piece of its screen to make a weather service draw the forecast there.
A social network for the 19A0s.