Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Friday March 20 2020, @08:41PM   Printer-friendly
from the Do-No-Evil-Poof!-Gone. dept.

Moonchild, the lead developer of the Pale Moon browser writes:

"Dear Web Developer(s),

While, as a software developer ourselves, we understand very well that new features are exciting to use and integrate into your work, we ask that you please consider not adopting Google WebComponents in your designs. This is especially important if you are a web developer creating frameworks for websites to use.
With Google WebComponents here we mean the use of CustomElements and Shadow DOM, especially when used in combination, and in dynamically created document structures (e.g. using module loading/unloading and/or slotted elements).

Why is this important?

For several reasons, but primarily because it completely goes against the traditional structure of the web being an open and accessible place that isn't inherently locked down to opaque structures or a single client. WebComponents used "in full" (i.e. dynamically) inherently creates complex web page structures that cannot be saved, archived or even displayed outside of the designated targeted browsers (primarily Google Chrome).
One could even say that this is setting the web up for becoming fully content-controlled."

https://about.google/: "Our mission is to organize the world's information and make it universally accessible and useful"

Useful to... whom?


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 4, Insightful) by Arik on Saturday March 21 2020, @11:59AM

    by Arik (4543) on Saturday March 21 2020, @11:59AM (#973789) Journal
    "These new standards are open, not proprietary."

    Open malware; I'm not sure that's really better.

    "Nothing is stopping other clients from implementing these standards except lack of manpower."

    Since none of them have any ethical or moral standards, you're probably right about that.

    "The same argument could have been used to stop image support in web browsers, because some web browser developers didn't have the manpower to add image support."

    Yes, that's a flawed argument, designed to fail. The much better argument is because not all browsers have a display device capable of displaying images, and not all humans have eyes capable of seeing them.

    Therefore images must always be optional elements, with appropriate alt tags.

    "Web Components is basically for web apps."

    Exactly why they shouldn't exist.

    "Web apps can't really be saved or archived anyways; e.g., what does it mean to save the HTML view for a Google Doc?"

    You really don't understand what it means to save a view?

    "getting rid of Web Components won't stop websites from doing that."

    It would be a good start, but yes, all the common browsers are loaded with other junk that would also need to be removed.

    "One might object to web apps as a concept. Great! You are not going to stop people from wanting web apps."

    True, it's computer literacy that stops that. Too bad it's in decline.

    "Web devs are just going to import a 5 MB JavaScript library that basically does the same thing."

    Which is why javascript should never be allowed by default.

    --
    If laughter is the best medicine, who are the best doctors?
    Starting Score:    1  point
    Moderation   +2  
       Insightful=1, Interesting=1, Total=2
    Extra 'Insightful' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   4