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: 3, Interesting) by Anonymous Coward on Friday March 20 2020, @10:30PM

    by Anonymous Coward on Friday March 20 2020, @10:30PM (#973661)

    Angular and "SPA all the things" was the wave of the previous decade.
    Fortunately, I'm starting to see more people talking about server-side rendering, combined with JS loading the data-driven portions. That means the first request can contains a full page again, and the page updates can be served as HTML fragments, rather than JSON parsed and converted to HTML at the client side.

    Static pages do still make sense, and hopefully this decade we'll not see so many static pages delivered as SPAs.

    Starting Score:    0  points
    Moderation   +3  
       Interesting=2, Informative=1, Total=3
    Extra 'Interesting' Modifier   0  

    Total Score:   3