W3C hate thread. It is, without a doubt, the most corrupt software standards organization

W3C hate thread. It is, without a doubt, the most corrupt software standards organization.
A conforming browser needs to support
>Video - mp4, ogg and webm - each one having a long list of video and audio codecs they support
>Audio - mp3, ogg and wav (at least there are only 3)
>A JavaScript interpreter
>WebGL - essentially need to rewrite an OpenGL ES implementation
>HTML
>CSS
>SVG
>and much more
practically making it impossible for small or indie developers to make a web browser from scratch. And if that wasn't enough, EME made it actually impossible for small developers to create a competing browser.
And do not forget the time when they introduced a new high level shading language (WGSL) instead of using something that the industry realized was the correct choice and use some kind of bytecode language like SPIR-V. Despite overwhelming negative feedback they doubled down on it and rejected SPIR-V because "Apple had an undisclosed legal dispute with Khronos and as such feels uncomfortable using Khronos' IP".

Attached: W3C.jpg (640x480, 35.78K)

Other urls found in this thread:

wicg.github.io/element-timing/
wicg.github.io/keyboard-map/
wicg.github.io/get-installed-related-apps/spec/
github.com/WICG/trust-token-api
wicg.github.io/file-system-access/
w3c.github.io/geolocation-sensor/
wicg.github.io/background-sync/spec/
github.com/WICG/raw-clipboard-access/blob/main/explainer.md
webbluetoothcg.github.io/web-bluetooth/
wicg.github.io/webusb/
wicg.github.io/serial/
wicg.github.io/idle-detection/
wicg.github.io/uuid/
wicg.github.io/hdcp-detection/
wicg.github.io/periodic-background-sync/
wicg.github.io/netinfo/
wicg.github.io/webhid/
wicg.github.io/background-fetch/
wicg.github.io/page-lifecycle/
wicg.github.io/js-self-profiling/
wicg.github.io/visual-viewport/
wicg.github.io/direct-sockets/
wicg.github.io/responsive-image-client-hints/
wicg.github.io/close-watcher/
wicg.github.io/sms-one-time-codes/
wicg.github.io/datacue/
wicg.github.io/shape-detection-api/
wicg.github.io/keyboard-lock/
wicg.github.io/intervention-reporting/
wicg.github.io/crash-reporting/
webassembly.github.io/spec/core/binary/instructions.html
twitter.com/NSFWRedditImage

Don't forget WebAssembly kek. Also when you say "W3C" you should really mean "Google employees inside the W3C"

W3C is owned by Google now. Blame them.

>instead of using something that the industry realized was the correct choice and use some kind of bytecode language like SPIR-V. Despite overwhelming negative feedback they doubled down on it
You get what you deserve. Nothing is stopping someone from making a new browser that breaks compatibility with a bunch of this shit. You could do something that supported:
>xhtml
>css before the botnet
>a replacement for javascript with less access to the local machine
and whatever other fancy shit you want that's broken in Chrome/Firefox. For example I don't really care about video/audio codec support. That should just be passed to whatever is on the local machine that can decode it. Same thing for graphics and interactive media. Just define a standard for sending it and develop small applications for it.

My point is nothing can stop us from developing our own better version of the web. No one is doing it because they're lazy. Google is LARPing as the W3C and pretending these are open standards defined by some org. In reality they're just maintaining a monopoly over web standards. It's Bill Gate's wet dream.

What do you think is broken about the modern web other than the CDNs and "javashit"? Make a list of things you think you could improve. Then start developing your new small browser. We need something better than gopher but not a bloated security hole like http.

What about WebAssembly? Please elaborate

based

What about WEBGPU? Also there are a lot of APIs like webRTC the crypto API, etc.

>practically making it impossible for small or indie developers to make a web browser from scratch
In no way does W3C decide what is a web browser or which browsers can be used to browse the web.
Just make something good without seeking W3C's validation.
Invent your own markup language or HTML tags.
Be more than (((they))) want you to be!

just refuse to conform
simple as

>My point is nothing can stop us from developing our own better version of the web. No one is doing it because they're lazy.
right now the big thing in this direction is gemini, but I’m not sure if it’s the right way

gemini is too gimped
there will be no buy-in from normies if you cant display cat pictures

>there will be no buy-in from normies
good

how about not implementing them?

too bad that the shit that they say is usually implemented in browsers (mostly in Chrome) and well used on websites across the world

your only choice is to not implement questionable shit in your browser/sites
you have no power beyond that

wicg.github.io/element-timing/
wicg.github.io/keyboard-map/
wicg.github.io/get-installed-related-apps/spec/
github.com/WICG/trust-token-api
wicg.github.io/file-system-access/
w3c.github.io/geolocation-sensor/
wicg.github.io/background-sync/spec/
github.com/WICG/raw-clipboard-access/blob/main/explainer.md
webbluetoothcg.github.io/web-bluetooth/
wicg.github.io/webusb/
wicg.github.io/serial/
wicg.github.io/idle-detection/
wicg.github.io/uuid/
wicg.github.io/hdcp-detection/
wicg.github.io/periodic-background-sync/
wicg.github.io/netinfo/
wicg.github.io/webhid/
wicg.github.io/background-fetch/
wicg.github.io/page-lifecycle/
wicg.github.io/js-self-profiling/
wicg.github.io/visual-viewport/
wicg.github.io/direct-sockets/
wicg.github.io/responsive-image-client-hints/
wicg.github.io/close-watcher/
wicg.github.io/sms-one-time-codes/
wicg.github.io/datacue/
wicg.github.io/shape-detection-api/
wicg.github.io/keyboard-lock/
wicg.github.io/intervention-reporting/
wicg.github.io/crash-reporting/

webassembly = binary code from random websites
webassembly.github.io/spec/core/binary/instructions.html

i agree
my issue with gemini is that it doesn’t even allow you to do basic interactive services like forums, etc
i guess drew would just tell us to use email but it’s a bit retarded

The W3C just standardises, it isn't the dictator of the web. The alternative is fully proprietary and incompatible tech in every browser like the IE6 days.

>using the web instead of just a list of your favorite bulletin boards
ishiggydiggy

Most of those are the WHATWG's doing.
W3C was bullied out of leading web standardization after XHTML's failure.

Email lists are so fucking garbage.
Gemini is to http as source hut is to github.
And inferior "minimal" clone that has a worse user experience and drops all the parts of it that made it popular/useful to begin with.

>Most of those are the WHATWG's doing.
yes, this is very noticeable

what was XHTML about?