Since Tim Berners Lee basically opened his ass cheeks for big corporations and the web was already pretty screwed anyway, is it time for us to replace W3C?
ITT: We correct W3C
Other urls found in this thread:
whatwg.org
tools.ietf.org
whatwg.org
citizencodeofconduct.org
docs.racket-lang.org
ronja.twibright.com
web-artanis.com
web.archive.org
github.com
kernel.org
contributor-covenant.org
blog.plan99.net
w3.org
wiki.mozilla.org
media.urbit.org
youtube.com
youtube.com
youtube.com
stackoverflow.com
twitter.com
The time is to replace the web, not the consortium that standardizes it.
If you can get normies to use your implementation of whatever autistic standard this board is capable of coming up with, sure.
these guys:
If that "gif files shouldn't be allowed" discussion is anything to go by, you can bet you life on that never happening.
Why would you want to have normies in the first place? It's not like they produce any useful content anyways. You'll also attract corporations to push ads to "new web", you'll basically have same thing we have now. People will get bribed and sell out if enough money is involved (sir/cuck Tim Berners Lee), nobody can be trusted 100%.
Why don't we just build standalone applications? Web technology is bloated (support for lots of things only few sites use but browser has to include them anyways) and most of the time you have to fight it to achieve anything. With standalone applications you can do whatever you want.
What we should do is remove javascript and expand HTML. HTML should have features that allow for instance loading more content and replacing old content when a button is pressed or you hover over something, and changing the css classes upon button press or based on a timer so you could make interactive elements without scripts.
To be honest I'd rather just start over and rebuild the entire web standard from scratch. HTML is bloated shit and the syntax is gay, CSS is broken and makes no sense at times, and javascript should be replaced by userscripts (see: if you want the website to work like an app, you must install a script for that site).
YES
Key words for use in RFCs to Indicate Requirement Levels
tools.ietf.org
Standard 1: The web browser shall render text.
Standard 2: The web browser shall render non animated images.
Standard 3: The web browser shall not under any circumstance execute code.
THOU SHALT NOT EXECUTE CODE IN THE CLIENT
It's dead
whatwg.org
Keep your greasy hands off my internet.
Web
What ?