rene wrote: ⤴
Fri Dec 07, 2018 2:11 pm
xenopeek wrote: ⤴
Fri Dec 07, 2018 1:32 pm
And we should be afraid for the same reasons.
Frankly I'm not so sure about that. In what manner do we suffer when an open-source engine unites the web?
...was reading this article
earlier today, it appears to make the round in social networking platforms...
It's quite spot on, and yeap, i'd agree it's more or less 'Game Over' for Mozilla.
But the thing is not a this-engine vs that-other-engine, or even more one-engine-to-rule-them-all vs numerous ones.
A single engine 'per se' could possibly be just fine 'as is',
eliminating as well those absolutely irrelevant under every aspect dinosaurs,
that even on 2018 insist of maintaining...XUL (that Mozilla itself has depreciated - referring to some Firefox clones / forks).
Nothing wrong with such per se...in a sense, quite the contrary.
The issue from now on would be the even more extended control,
that Google will quite likely have in defining the web standards per their own internal interests.
I copy / paste from the linked article above for the sake of simplicity / for those into tldr...
The longer term faith of the open web, it hangs in the balance.
I don’t believe implementers can break the dominance anytime soon via an actual browser or browser engine,
which is why I’ll reiterate what I already said:
there must be equal representation in the process where web standards get created,
as well as in the decision making process where priorities for implementation get set.
We’d then have less engines, basically only one, yet what gets build for it in which order would be shared.
An open decision making process, followed by implementation in a single engine. It would be a kind-of open web.
No, not even that is ideal, I know. I’m keeping it real.
A kind-of open web is superior to the situation of having a single engine with a single private organization calling the shots.
The idealistic scenario of a multi-engine open web is dead or dying, as discussed above.
The underlined / bold emphasis is strictly mine...
And indeed, the 'web standards' part above, somehow brought to mind the not-so-old story with W3C & EME
https://www.theinquirer.net/inquirer/ne ... x-with-drm
If such previous attempts / proposals at defining 'web standards' were already successful,
even when there existed other players with different implementations that were still to be taken seriously as 'competitors',
then surely things feel somewhat dystopic from here on.
Remains to be seen...