Inferencium/website
1
0
Fork 0
Code Issues Activity

Update Blog #3 webpage from version 4.0.1.12 to 4.1.0.21.

Browse Source
This commit is contained in:
inference 2023-06-27 22:10:11 +01:00
parent cf66a66e6a
commit 052d2d2a28
Signed by: inference
SSH Key Fingerprint: SHA256:9Pl0nZ2UJacgm+IeEtLSZ4FOESgP1eKCtRflfPfdX9M
1 changed files with 87 additions and 116 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

107
blog/the_chromium_monopoly.html
View File

@ -5,22 +5,19 @@
<!-- Copyright 2022 Jake Winters --> <!-- Copyright 2022 Jake Winters -->
<!-- SPDX-License-Identifier: BSD-3-Clause --> <!-- SPDX-License-Identifier: BSD-3-Clause -->
<!-- Version: 4.0.1.12 --> <!-- Version: 4.1.0.21 -->
<html> <html>
<head>
<head>
<title>Inferencium - Blog - The Chromium Monopoly</title> <title>Inferencium - Blog - The Chromium Monopoly</title>
<link rel="stylesheet" href="../inf.css"> <link rel="stylesheet" href="../inf.css">
<meta name="viewport" content="width=device-width, initial-scale=1"> <meta name="viewport" content="width=device-width, initial-scale=1">
</head> </head>
<!-- Navigation bar -->
<!-- Navigation bar. --> <div class="sidebar">
<div class="sidebar"> <a href="../index.html"><img src="../asset/img/logo-inferencium-no_text.png" width="110px" height="110px"></a>
<img src="../asset/img/logo-inferencium-no_text.png" <a href="../index.html" class="title">Inferencium</a><br>
width="110px" height="110px">
<a class="title">Inferencium</a><br>
<br> <br>
<br> <br>
<div><a href="../about.html">About</a></div> <div><a href="../about.html">About</a></div>
@ -29,76 +26,54 @@
<div><a href="../source.html">Source</a></div> <div><a href="../source.html">Source</a></div>
<div><a href="../key.html">Key</a></div> <div><a href="../key.html">Key</a></div>
<div><a href="../changelog.html">Changelog</a></div> <div><a href="../changelog.html">Changelog</a></div>
</div> </div>
<body>
<body>
<h1>Blog - #3</h1> <h1>Blog - #3</h1>
<br>
<br>
<br>
<h2>The Chromium Monopoly</h2> <h2>The Chromium Monopoly</h2>
<br>
<p class="update_date">Posted: 2022-12-20 (UTC+00:00)</p> <p class="update_date">Posted: 2022-12-20 (UTC+00:00)</p>
<p class="update_date">Updated: 2022-12-20 (UTC+00:00)</p> <p class="update_date">Updated: 2022-12-20 (UTC+00:00)</p>
<br> <!-- Table of contents -->
<br> <section id="toc">
<h2 id="toc"><a href="#toc" class="h2">Table of Contents<a/></h2>
<!-- Table of contents. -->
<h2 id="toc"><a href="#toc" class="h2"
>Table of Contents<a/></h2>
<ul> <ul>
<li><a href="#introduction" class="body-link" <li><a href="#introduction" class="body-link">Introduction</a></li>
>Introduction</a></li> <li><a href="#solution" class="body-link">Solution</a></li>
<li><a href="#solution" class="body-link" <li><a href="#conclusion" class="body-link">Conclusion</a></li>
>Solution</a></li>
<li><a href="#conclusion" class="body-link"
>Conclusion</a></li>
</ul> </ul>
<br> </section>
<br> <section id="introduction">
<br> <h2 id="introduction"><a href="#introduction" class="h2">Introduction</a></h2>
<h2 id="introduction"><a href="#introduction" class="h2"
>Introduction</a></h2>
<p>It's no secret that I'm an advocate of Chromium and will use it for the foreseeable future. It is <p>It's no secret that I'm an advocate of Chromium and will use it for the foreseeable future. It is
a highly secure web browser which provides strong protection against malicious wesbites and the code a highly secure web browser which provides strong protection against malicious wesbites and the code
they run, and, while I am not too interested in high performance, it is a very performant web they run, and, while I am not too interested in high performance, it is a very performant web
browser, despite its security features.<br> browser, despite its security features.</p>
<br> <p>However, the intention of this blog post is not to promote Chromium for any reason, but rather show
However, the intention of this blog post is not to promote Chromium for any reason, but rather show
an issue with it; an issue which is larger than may be realised by web-surfing users. That issue is an issue with it; an issue which is larger than may be realised by web-surfing users. That issue is
the large monopoly Chromium has in the web browser market; the large monopoly Chromium has in the web browser market;
<a class="body-link" href="https://en.wikipedia.org/wiki/Usage_share_of_web_browsers#Summary_tables" <a href="https://en.wikipedia.org/wiki/Usage_share_of_web_browsers#Summary_tables" class="body-link">Chromium's market share is around 65%</a>,
>Chromium's market share is around 65%</a>,
making it the largest slice of the cake. The issue becomes even deeper and more problematic when you making it the largest slice of the cake. The issue becomes even deeper and more problematic when you
realise that the second-place web browser, Safari, has only an 18% market share.<br> realise that the second-place web browser, Safari, has only an 18% market share.</p>
<br> <p>The main issue with this type of monopoly is the large amounts of power and influence it gives
The main issue with this type of monopoly is the large amounts of power and influence it gives
Chromium, which can lead to, and is leading to, excessive authority of how the web should work, and Chromium, which can lead to, and is leading to, excessive authority of how the web should work, and
the standards which are implemented, which all other web browsers must comply with in order to have the standards which are implemented, which all other web browsers must comply with in order to have
a fully working web.<p> a fully working web.</p>
<br> </section>
<br> <section id="solution">
<h2 id="solution"><a href="#solution" class="h2">Solution</a></h2>
<h2 id="solution"><a href="#solution" class="h2"
>Solution</a></h2>
<p>In order to combat the Chromium monopoly, users typically go over to Chromium's classical rival, <p>In order to combat the Chromium monopoly, users typically go over to Chromium's classical rival,
Firefox. However, Firefox is dying and has lost almost all of its userbase over the last 2-3 years; Firefox. However, Firefox is dying and has lost almost all of its userbase over the last 2-3 years;
the reason for this is a tale of selfishness and greed, caused by Firefox's parent company to go off the reason for this is a tale of selfishness and greed, caused by Firefox's parent company to go off
course and lose its original goal of providing a freedom-respecting, open web. Mozilla caused course and lose its original goal of providing a freedom-respecting, open web. Mozilla caused
self-inflicted damage which it cannot recover from, and, to me, is already dead. The vultures are self-inflicted damage which it cannot recover from, and, to me, is already dead. The vultures are
simply waiting for the final, small group of users to abandon the project before Firefox finally simply waiting for the final, small group of users to abandon the project before Firefox finally
succumbs to its own demise; the demise it caused itself.<br> succumbs to its own demise; the demise it caused itself.</p>
<br> <p>If attempting to increase Firefox's market share to previous levels will be in vain, what is the
If attempting to increase Firefox's market share to previous levels will be in vain, what is the
solution? How can we prevent Chromium from completely taking over the web and dictating everything solution? How can we prevent Chromium from completely taking over the web and dictating everything
we do and how the web should be designed and used?<br> we do and how the web should be designed and used?</p>
To find the answer to these important but difficult questions, we must go to the alternatives which <p>To find the answer to these important but difficult questions, we must go to the alternatives which
still have a fighting chance. Safari, developed by Apple, is based on WebKit, an engine completely still have a fighting chance. Safari, developed by Apple, is based on WebKit, an engine completely
independent of Chromium and Firefox.<br> independent of Chromium and Firefox.</p>
<br> <p>Just using a non-Chromium-based web browser is not enough; the choice must already have enough
Just using a non-Chromium-based web browser is not enough; the choice must already have enough
market share to still be relevant, and be capable of gaining new users. Safari, being preinstalled market share to still be relevant, and be capable of gaining new users. Safari, being preinstalled
on Apple devices including iPhone and Mac, already has a great advantage over Firefox. Apple on Apple devices including iPhone and Mac, already has a great advantage over Firefox. Apple
devices, especially iPhone, is abundant in streets everywhere on the planet. Safari is the default devices, especially iPhone, is abundant in streets everywhere on the planet. Safari is the default
@ -111,17 +86,13 @@
supporting the second-place alternative is, in order to keep the one you don't want out of power, supporting the second-place alternative is, in order to keep the one you don't want out of power,
giving the party you do want in power an advantage. To win this war against the Chromium monopoly, giving the party you do want in power an advantage. To win this war against the Chromium monopoly,
we must be tactical, not emotional.</p> we must be tactical, not emotional.</p>
<br> </section>
<br> <section id="conclusion">
<h2 id="conclusion"><a href="#conclusion" class="h2">Conclusion</a></h2>
<h2 id="conclusion"><a href="#conclusion" class="h2"
>Conclusion</a></h2>
<p>Supporting Safari is the first step in supporting WebKit and promoting usage of the independent <p>Supporting Safari is the first step in supporting WebKit and promoting usage of the independent
web engine. Buying time while supporting and contributing to WebKit browser projects is the best and web engine. Buying time while supporting and contributing to WebKit browser projects is the best and
only chance anyone has at competing with Chromium, and preventing it from increasing its dominance only chance anyone has at competing with Chromium, and preventing it from increasing its dominance
to unstoppable levels, at which point there will be no return. to unstoppable levels, at which point there will be no return.</p>
<br> </section>
<br> </body>
</body>
</html> </html>