Microsoft, Google, Mozilla, and Apple Formally Object to W3C Fork of DOM Spec
(submitted by tptacek)
@hntooter oh boy.
I'm seeing an analogy between the WHATWG's "living standard" and the ridiculousness of the evergreen browser where webdevs only feel the need to support browsers released in the past couple months.
Anyone else seeing that?
Ok, here seem to be explained the political reasoning: https://github.com/w3c/dom/issues/175#issuecomment-379754622
In practice it seems that the #W3C have simply realized that nobody delegated to WHATWG their work, and proposed an update Recommendation.
The #WHATWG got offended since they prefer to control a "Live Standard" that only large organization can implement.
Large companies are like that, you must always ask their permission.
Now I'd like to know what technical difference exists between the two DOM APIs.
@Shamar @varx @rysiek Since W3C pushed for standardisation of EME despite large community backslash, I don't think W3C is any different in this regard wen it comes to the influence of large companies. It seems like a much more likely explanation is simply that the W3C feels they outta have as much web standards under their umbrella as possible and they're not happy that the implemented DOM has so far not been the one they control.
#EME standardisation is a good point.
I remember the #EFF reaction: https://www.zdnet.com/article/eff-resigns-from-w3c-in-wake-of-eme-drm-standardisation/
So we have the most powerful companies of the planet on one side and an organization prone to lobbying on the other.
Take this #ScienceFiction!
@Shamar @varx @rysiek Yeah, surreal. The funny thing is, from a purely *technical* perspective, the W3C is trying to do the sane thing here, i.e. as developers etc. we should have a set DOM standard to target, rather than a document that is constantly changing under our feet as Google or MS wish, however W3C is an unreliable actor, so if they lack the big corps on this, they can't even turn to support from the community with a straight face, given their undemocratic history.
@Wolf480pl @Shamar @rysiek @varx Interesting, web apps have somewhat decoupled one from a particular OS, (but not 'ecosystem' unfortunately), so I feel they're a net positive, if not a large one. However people would still want to use/do web apps, so it would just be a question of who controls two separate standards now.
The distinction between a document and and an app can also be somewhat murky, (i.e. Wikipedia is technically an app).
I think it's a governance problem, not a technical one.
Anyway, I think it'd be cool to have some subset of the web specs suited for documents, that is relatively stable, and can be implemented by lightweight browsers made by smaller vendors.
What do you think #WebAssembly is for?
It's the one #Ring to rule them all!
I can't tell if it will succeed at this goal, but for sure that is the goal.
I hope they fail for the mountain of shit it's built upon.
Indeed I feel like we are at a very early stage of our field, at a primitive stage, and still big players are trying to lock everybody.
I don't think we are ready to build such universal computing environment.
But why not?
To attempt to answer your question, it's all a question of purpose and audience (which to be fair is a field full of context and nuance).
Different operating systems serve different audiences with different tastes in the sort of UI they like or need. And apps running on that operating system should be targetted to the cross section between it's own and that OS's audience.
@Shamar @alcinnz @rysiek @MatejLach @varx
judging by how good JS devs are at optimizing their code, nothing web-related will ever be good for low-end devices.
Eg. on Acer Aspire One, the only way to use Slack is through weechat with wee-slack plugin.
Also, in some cases commandline or curses-like text UI is better suited, and I don't see how anything could change that.
Moreover, the user should be able to set UI themes at OS/DE level, and apps should obey that. JS devs would never allow this.
@Shamar @alcinnz @rysiek @MatejLach @varx
Also, different users have different level of expertise, and need different level of features. Eg. I think Conversations is a way better XMPP client for newbies than Gajim, but if you're an XEP-reading nerd debugging the protocol, Gajim is way better suited.
Finally, I think that keyboard with good keybindings beats down mouse or touch input wrt. speed & precision, and touch UIs need different design than kbd or kbd+mouse ones (eg. smaller buttons).
We are a cute and loving international community Ｏ(≧▽≦)Ｏ !