aboutsummaryrefslogtreecommitdiff
path: root/build/future-os-google/index.html
diff options
context:
space:
mode:
authorBradley Taunt <bt@btxx.org>2024-07-02 14:22:21 -0400
committerBradley Taunt <bt@btxx.org>2024-07-02 14:22:21 -0400
commit3f6a9546ec13063d0d5bdf21d30a93d3e8aa6050 (patch)
tree947985c4eda1bceb1910bc01739c32fd0baad181 /build/future-os-google/index.html
parent14074019d62d98885c4c764401a9e7e1fd129f79 (diff)
Rebuild changes based off latest barfHEADmaster
Diffstat (limited to 'build/future-os-google/index.html')
-rw-r--r--build/future-os-google/index.html96
1 files changed, 96 insertions, 0 deletions
diff --git a/build/future-os-google/index.html b/build/future-os-google/index.html
new file mode 100644
index 0000000..5940e7b
--- /dev/null
+++ b/build/future-os-google/index.html
@@ -0,0 +1,96 @@
+<!doctype html>
+<html lang="en">
+<head>
+ <meta charset="utf-8">
+ <meta name="viewport" content="width=device-width, initial-scale=1">
+ <meta name="color-scheme" content="dark light">
+ <link rel="icon" href="data:,">
+ <title>Chrome OS Could Become the Future Leader of Computing</title>
+ <link href="/atom.xml" type="application/atom+xml" rel="alternate" title="Atom feed for blog posts" />
+ <link href="/rss.xml" type="application/rss+xml" rel="alternate" title="RSS feed for blog posts" />
+<style>*{box-sizing:border-box;}body{font-family:sans-serif;line-height:1.33;margin:0 auto;max-width:650px;padding:1rem;}blockquote{background:rgba(0,0,0,0.1);border-left:4px solid;padding-left:5px;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style>
+</head>
+
+<nav>
+ <a href="#menu">Menu &darr;</a>
+</nav>
+
+<main>
+<h1 id="chrome-os-could-become-the-future-leader-of-computing">Chrome OS Could Become the Future Leader of Computing</h1>
+<p>2022-01-06</p>
+<p><strong>FOSS Enthusiasts</strong>: This article discusses the use of proprietary software and places it in a <em>positive</em> light. You have been warned. No angry emails please&#8230;</p>
+<hr/>
+<p>Google has created one of the best operating systems designed with the everyday user1 in mind: <a href="https://www.google.com/chromebook/chrome-os/">Chrome OS</a>. It is undeniably simple, reliable, easy to setup, and ships with several years of support before any form of EOL kicks in. New models have built-in support for the Google Play Store and Android applications, which is helpful for application development and debugging.</p>
+<p>In addition, Chrome OS devices allow you to run Linux in a separate container alongside the main OS (on supported devices). You can&#8217;t complain about that!</p>
+<p>Let&#8217;s take a quick look at other positive features worth mentioning:</p>
+<ul>
+<li>Verified boot</li>
+<li>Sandboxed environment (similar to how Chrome tabs work)</li>
+<li>Automatic updates[^2]</li>
+<li><em>Incredible</em> battery life (were talking 10+ hours with heavy usage)</li>
+</ul>
+<h2 id="my-personal-experience">My Personal Experience</h2>
+<p>A handful of months ago I snagged the Lenovo Chromebook Duet when it was on sale for my wife. Since she does all her work directly through an Android phone, I thought of this as a nice companion device. And indeed it was&#47;is.</p>
+<p>In that time, I played around with the tablet myself to have a better grasp of the ecosystem and it&#8217;s obvious limitations. But a funny thing happened. I found that those &#8220;limitations&#8221; slowly started to disappear the longer I worked with the device.</p>
+<p>I decided to get my own Chrome OS device and snagged the <a href="https://www.lenovo.com/ca/en/laptops/lenovo/student-chromebooks/Lenovo-10e-Chromebook-Tablet/p/82AM000EUS">Lenovo 10e Chromebook Tablet</a> (on sale).</p>
+<ul>
+<li>10.1&#8221; display (1920 x 1200) &#47; 400 nits</li>
+<li>4GB of RAM</li>
+<li>32GB of eMMC storage</li>
+<li>Processor: MediaTek MT8183 Processor (2.00 GHz, 4 Cores, 1 MB Cache)</li>
+</ul>
+<p>Now, I know that your initial reaction is likely: &#8220;Wow, those specs are pretty barebones!&#8221; and you would be correct. But it&#8217;s all you need for this ecosystem to work. As cringe-inducing as it may sound, everything you plan to do on these devices should happen <em>in the cloud</em>. (Let&#8217;s take a moment to avoid vomiting in our collective mouths)</p>
+<p>Instead of using a few marketing buzz words, let me breakdown how I personally tailor Chrome OS to my needs as a designer &#47; developer:</p>
+<ol>
+<li><a href="#daily-tasks">Daily Tasks</a></li>
+<li><a href="#programming">Programming</a></li>
+<li><a href="#design">Design</a></li>
+<li><a href="#gaming">Gaming</a></li>
+</ol>
+<h2 id="daily-tasks">Daily Tasks</h2>
+<p>I feel like going into <em>great</em> detail explaining how to do basic, daily computing tasks is a little overkill here. Spreadsheets, word documents, Zoom meetings, and streaming media work as expected. You have the ability to use Google&#8217;s own web apps for these things or reach for other vendors such as Microsoft and Libre Office. Not being &#8220;locked in&#8221; to Google software is nice and I appreciate the Chrome OS team being flexible.</p>
+<h2 id="programming">Programming</h2>
+<p>This one is a mixed bag and your own mileage may vary depending on your specific requirements. Personally, I use Github for almost all my main development work. Because of this, I utilize <a href="https://github.com/features/codespaces">Codespaces</a>. For those unfamiliar with the service, you are running your Github repo in VSCode through the browser. It&#8217;s pretty impressive.</p>
+<p>If you happen to be a user who uses GitLab or BitBucket to store your project files, <a href="https://www.gitpod.io/">Gitpod</a> is a similar product to Codespaces (which I&#8217;ve used on occasion). This works if your prefer.</p>
+<p>Others may not like this programming setup but for me it works great. If running code remotely isn&#8217;t your jam, you could always take a look at running <a href="https://vscodium.com/">VSCodium</a> locally via Linux.</p>
+<h2 id="design">Design</h2>
+<p>There is flexibility yet again in this category. Personally, I tend to use Figma almost exclusively as my main design tool. The best thing about Figma? It runs directly in the browser. A perfect fit for Chromebooks[^3].</p>
+<p>I do open Gimp periodically for photo-specific work. It runs in its own Linux container and chugs along smoothly, even with 4GB of available memory. If all else fails, one could use <a href="https://www.photopea.com/">Photopea</a> to keep everything working through the browser (if Linux isn&#8217;t your cup of tea).</p>
+<p>Those of you in love with MacOS specific apps like Sketch - I can&#8217;t help you. You&#8217;re stuck with Apple&#8217;s ecosystem. (Not that there is anything wrong with Sketch!)</p>
+<h2 id="gaming">Gaming</h2>
+<p>There are other options (that we will get into) but the main gaming champion here is <strong>Stadia</strong>[^4]. As long as your internet speeds are over 10mbps, mind you. I use garbage satellite internet (counting down the days for Starlink to become available here&#8230;) with an average speed of 18-20mbps and Stadia runs like a dream. Even <em>wirelessly</em>. Now pair this with the portability of a Chromebook device and you&#8217;ve got yourself a beefier Nintendo Switch.</p>
+<p>You have solid secondary options like <a href="https://play.geforcenow.com/mall/#/layout/games">GeForce Now</a> and <a href="https://www.xbox.com/en-CA/xbox-game-pass/cloud-gaming">Microsoft&#8217;s xCloud (beta)</a> for an even larger catalogue of games. Not to mention the ability to play a lot of Android games natively on Chromebooks that support Play Store applications.</p>
+<h2 id="eye-rolling-scoffing">Eye Rolling &#38; Scoffing</h2>
+<p>I can hear the screeching across the interwebs: &#8220;<em>Wait - this is Google! They are literally Satan in disguise! No one can use products from that evil mega corporation!</em>&#8221;. And while I agree with the sentiment, I think going down this pure, 100% elitist approach to software <em>doesn&#8217;t work</em> with the everyday casual user. Not to mention the large swath of developers&#47;designers screaming &#8220;Google is bad!&#8221; while working off an <em>Apple</em> device&#8230;</p>
+<p>Hell even I, a vocal advocate for open source software and privacy, can see the great benefits to using Chrome OS as a daily driver. </p>
+<p>Testing out Chrome OS with your non-technical friends and family could help reduce a lot of headaches found in more &#8220;popular&#8221; systems. That doesn&#8217;t mean advanced users have to switch over. Use what works the best for you. For my immediate family members and social circles, I have nothing but positive things to say about Chrome OS.</p>
+<p>I have no crystal ball to see what the future of Chrome OS holds but it looks pretty promising to me.</p>
+<h2 id="refs">Refs</h2>
+<ol>
+<li>&#8220;Users&#8221; referring to those mainly using their devices for word documents, spread sheets, media consumption, programming, messaging, minor interactivity (no heavy video or production editing)</li>
+<li>These updates go unnoticed, compared to that of MacOS or Windows&#8230;</li>
+<li>Your mileage may vary depending on how much RAM you have on your device</li>
+<li>Although, Stadia&#8217;s current game selection leaves a lot to be desired</li>
+</ol>
+<footer role="contentinfo">
+ <h2>Menu Navigation</h2>
+ <ul id="menu">
+ <li><a href="/">Home</a></li>
+ <li><a href="/projects">Projects</a></li>
+ <li><a href="/uses">Uses</a></li>
+ <li><a href="/wiki">Wiki</a></li>
+ <li><a href="/resume">Resume</a></li>
+ <li><a href="/colophon">Colophon</a></li>
+ <li><a href="/now">Now</a></li>
+ <li><a href="/donate">Donate</a></li>
+ <li><a href="/atom.xml">RSS</a></li>
+ <li><a href="#top">&uarr; Top of the page</a></li>
+ </ul>
+ <small>
+ Built with <a href="https://barf.btxx.org">barf</a>. <br>
+ Feeds: <a href="/atom.xml">Atom</a> & <a href="/rss.xml">RSS</a><br>
+ Maintained with ♥ for the web. <br>
+ Proud supporter of <a href="https://usefathom.com/ref/DKHJVX">Fathom</a> &amp; <a href="https://nextdns.io/?from=74d3p3h8">NextDNS</a>. <br>
+ The content for this site is <a href="https://creativecommons.org/licenses/by-sa/2.0/">CC-BY-SA</a>.<br> The <a href="https://git.sr.ht/~bt/bt.ht">code for this site</a> is <a href="https://git.sr.ht/~bt/bt.ht/tree/master/item/LICENSE">MIT</a>.
+ </small>
+</footer> \ No newline at end of file