Inferencium/website
1
0
Fork 0
Code Issues Activity

Update Blog #3 webpage from version 4.0.1.12 to 4.1.0.20.

Browse Source
This commit is contained in:
inference 2023-06-27 22:04:06 +01:00
parent ef81d9c062
commit 745205dc0f
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

203
blog/the_chromium_monopoly.html
View File

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