Conversation

Notices

1. Embed this notice
   Rich Felker (dalias@hachyderm.io)'s status on Sunday, 23-Jul-2023 14:38:45 JST Rich Felker

   • Enron Hubbard

   @enron And more generally, Chromium is malware.

   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Sunday, 23-Jul-2023 14:38:42 JST Rich Felker

     in reply to

     • Enron Hubbard
     • Morgan Gangwere (job-seeking)

     @indrora @enron Well my point is that "it's Chromium based but not Chrome so it's ok" is flawed thinking. Chromium is the malware by which Google's web monoculture gets reach into enclaves of resistance against Chrome.

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Morgan Gangwere (job-seeking) (indrora@social.sdf.org)'s status on Sunday, 23-Jul-2023 14:38:43 JST Morgan Gangwere (job-seeking)

     in reply to

     • Enron Hubbard

     @dalias @enron it’s the symptom of a greater disease.

   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Sunday, 23-Jul-2023 14:50:12 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • Enron Hubbard
     • Morgan Gangwere (job-seeking)
     @indrora @dalias @enron Process model is far from being the only issue, sure it plagued Firefox and other engines, but Chromium also was the one that introduced a lot of performance differences like a *really* fast JavaScript engine.
     
     But I think the real thing that made Firefox turn into irrelevance: They threw themselves out of the embedded market (with killing off mozembed) and quite failed to get a good mobile browser out.
   • Embed this notice
     Morgan Gangwere (job-seeking) (indrora@social.sdf.org)'s status on Sunday, 23-Jul-2023 14:50:13 JST Morgan Gangwere (job-seeking)

     in reply to

     • Enron Hubbard

     @dalias @enron that monoculture is the result of Mozilla, Apple, and Microsoft infighting while at the table of the w3c.

     When none of them could agree on common things, Google ramrodded many of their ideas through. Many of the APIs that we criticize Google for were proposed by Mozilla for Firefox OS, then taken up by Google, who went and implemented them such that Chromium’s process model was the only valid way to implement it.

     You now cannot be standards compliant without being Chromium.

   • Embed this notice
     Morgan Gangwere (job-seeking) (indrora@social.sdf.org)'s status on Sunday, 23-Jul-2023 14:50:13 JST Morgan Gangwere (job-seeking)

     in reply to

     • Enron Hubbard

     @dalias @enron see also this post from my other account https://furry.engineer/@indrora/110735776918486996