Post AXyaxaTTwEA3bl8SW0 by indrora@social.sdf.org
(DIR) More posts by indrora@social.sdf.org
(DIR) Post #AXyaxZoiNnYFZK3tyK by dalias@hachyderm.io
2023-07-23T04:52:22Z
0 likes, 0 repeats
@enron And more generally, Chromium is malware.
(DIR) Post #AXyaxaTTwEA3bl8SW0 by indrora@social.sdf.org
2023-07-23T05:01:17Z
0 likes, 0 repeats
@dalias @enron it’s the symptom of a greater disease.
(DIR) Post #AXyaxbDv9ZJ9vmrXto by dalias@hachyderm.io
2023-07-23T05:15:14Z
1 likes, 0 repeats
@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.
(DIR) Post #AXybz74sJ1xky6uvWy by indrora@social.sdf.org
2023-07-23T05:20:42Z
0 likes, 0 repeats
@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.
(DIR) Post #AXybz7jdrSZZ0XzU4e by indrora@social.sdf.org
2023-07-23T05:26:01Z
0 likes, 0 repeats
@dalias @enron see also this post from my other account https://furry.engineer/@indrora/110735776918486996
(DIR) Post #AXybz8GFuCf0dhFWuO by lanodan@queer.hacktivis.me
2023-07-23T05:49:54.550899Z
0 likes, 0 repeats
@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.