Update webpage "Blog - #3" from version 5.0.0+26 to 5.0.1
This commit is contained in:
parent
e9871e6d0d
commit
ceb3c1ad0e
@ -5,7 +5,7 @@
|
||||
<!-- Copyright 2022 Jake Winters -->
|
||||
<!-- SPDX-License-Identifier: BSD-3-Clause -->
|
||||
|
||||
<!-- Version: 5.0.0+26 -->
|
||||
<!-- Version: 5.0.1 -->
|
||||
|
||||
|
||||
<html>
|
||||
@ -14,7 +14,7 @@
|
||||
<link rel="stylesheet" href="../main.css">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
</head>
|
||||
<!-- Navigation bar -->
|
||||
<body>
|
||||
<div class="sidebar">
|
||||
<a href="../index.html"><img src="../asset/img/logo-inferencium-no_text.png" width="110px" height="110px"></a>
|
||||
<a href="../index.html" class="title">Inferencium</a><br>
|
||||
@ -28,12 +28,10 @@
|
||||
<div><a href="../key.html">Key</a></div>
|
||||
<div><a href="../changelog.html">Changelog</a></div>
|
||||
</div>
|
||||
<body>
|
||||
<h1>Blog - #3</h1>
|
||||
<h2>The Chromium Monopoly</h2>
|
||||
<p class="update_date">Posted: 2022-12-20 (UTC+00:00)</p>
|
||||
<p class="update_date">Updated: 2022-12-20 (UTC+00:00)</p>
|
||||
<!-- Table of contents -->
|
||||
<p class="update_date">Updated: 2023-11-11 (UTC+00:00)</p>
|
||||
<section id="toc">
|
||||
<h2 id="toc"><a href="#toc">Table of Contents<a/></h2>
|
||||
<ul>
|
||||
@ -44,56 +42,68 @@
|
||||
</section>
|
||||
<section id="introduction">
|
||||
<h2 id="introduction"><a href="#introduction">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
|
||||
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
|
||||
browser, despite its security features.</p>
|
||||
<p>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
|
||||
the large monopoly Chromium has in the web browser market;
|
||||
<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 they run, and, while I am not
|
||||
too interested in high performance, it is a very performant web browser, despite
|
||||
its security features.</p>
|
||||
<p>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 the large monopoly Chromium has in
|
||||
the web browser market;
|
||||
<a href="https://en.wikipedia.org/wiki/Usage_share_of_web_browsers#Summary_tables">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
|
||||
realise that the second-place web browser, Safari, has only an 18% market share.</p>
|
||||
<p>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
|
||||
the standards which are implemented, which all other web browsers must comply with in order to have
|
||||
a fully working web.</p>
|
||||
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.</p>
|
||||
<p>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 the standards which are implemented,
|
||||
which all other web browsers must comply with in order to have a fully working
|
||||
web.</p>
|
||||
</section>
|
||||
<section id="solution">
|
||||
<h2 id="solution"><a href="#solution">Solution</a></h2>
|
||||
<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;
|
||||
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
|
||||
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
|
||||
succumbs to its own demise; the demise it caused itself.</p>
|
||||
<p>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
|
||||
we do and how the web should be designed and used?</p>
|
||||
<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
|
||||
independent of Chromium and Firefox.</p>
|
||||
<p>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>
|
||||
<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; 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 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 succumbs to its own demise;
|
||||
the demise it caused itself.</p>
|
||||
<p>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 we do and how the web should be
|
||||
designed and used?</p>
|
||||
<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 independent of Chromium and
|
||||
Firefox.</p>
|
||||
<p>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>
|
||||
</section>
|
||||
<section id="conclusion">
|
||||
<h2 id="conclusion"><a href="#conclusion">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.</p>
|
||||
<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.</p>
|
||||
</section>
|
||||
</body>
|
||||
</html>
|
||||
|
Loading…
x
Reference in New Issue
Block a user