aboutsummaryrefslogtreecommitdiff
path: root/build/posts/monitor/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/posts/monitor/index.html
parent14074019d62d98885c4c764401a9e7e1fd129f79 (diff)
Rebuild changes based off latest barfHEADmaster
Diffstat (limited to 'build/posts/monitor/index.html')
-rw-r--r--build/posts/monitor/index.html79
1 files changed, 0 insertions, 79 deletions
diff --git a/build/posts/monitor/index.html b/build/posts/monitor/index.html
deleted file mode 100644
index d3379c6..0000000
--- a/build/posts/monitor/index.html
+++ /dev/null
@@ -1,79 +0,0 @@
-<!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>Why I Stopped Using an External Monitor</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="why-i-stopped-using-an-external-monitor">Why I Stopped Using an External Monitor</h1>
-<p>2023-03-03</p>
-<p>For the longest time I&#8217;ve been using a Samsung 27&#8221; UHD monitor as my main display. This monitor was connected to my ThinkPad X260 (in clamshell mode) through the official Lenovo dock. It wasn&#8217;t a bad setup, but I have since changed my ways.</p>
-<p>Instead, I now <em>only</em> use the X260&#8217;s panel as my main display. Let me explain my reasoning&#8230;</p>
-<h2 id="the-switch-to-suckless">The Switch to Suckless</h2>
-<p>Over the past year I switched away from a traditional desktop environment to a window manager - <a href="https://dwm.suckless.org/">dwm</a> to be specific. This also involved changing most of my daily software programs to utilize the full suckless &#8220;suite&#8221;. In doing so, the shift away from floating windows and virtualized desktops happened quickly.</p>
-<p>I continued to use my UHD monitor with this new environment but slowly started running into minor (yet still inconvenient) roadblocks:</p>
-<ul>
-<li>Tiled mode was not the most optimized for such a large monitor. I found myself defaulting into &#8220;floating&#8221; mode which defeats the purpose of a WM.</li>
-<li>The screen was almost <em>too</em> large - making content placed on the far edges of the screen difficult to view at a glance.</li>
-<li>I stopped using tags, since I ended up piling applications on top of one another in a single view. Again - defeating the point of a WM.</li>
-</ul>
-<p>All of these issues were close to making me ditch the external monitor altogether, but it was my day-to-day job that struck the final blow&#8230;</p>
-<h2 id="designing-for-everyday-users">Designing for Everyday Users</h2>
-<p>As a UX&#47;UI front-end designer by trade, my job requires me to create and tweak interfaces that essentially go <em>unnoticed</em> by the end-users. If you finish a task you sought out to complete without even thinking about <em>how</em> you did it - then I succeeded at my job. The problem is, we designers and developers tend to forget the constraints a majority of our users experience. In this case - screen resolution.</p>
-<p><a href="https://www.browserstack.com/guide/ideal-screen-sizes-for-responsive-design">A study performed by BrowserStack via statcounter (2022)</a> shows the worldwide market share based on device type:</p>
-<ul>
-<li>58.33% mobile</li>
-<li>39.65% desktop</li>
-<li>2.02% tablet</li>
-</ul>
-<p>The mobile aspect is certainly important, but we are focusing on the desktop data. Of that total the top two screen resolutions are:</p>
-<ul>
-<li>1920×1080 (9.94%)</li>
-<li>1366×768 (6.22%)</li>
-</ul>
-<p>That is a fairly significant chunk of desktop users. Although almost 10% have access to screens set at <code>1920x1080</code>, I found the amount of those stuck at <code>1366x768</code> to be quite shocking. Here I was, developing large-set interfaces on an UHD 4K monitor while a large portion of my end-users would never benefit from those &#8220;pixel-perfect&#8221; designs. </p>
-<p>Hell, some of these users were being shown the <em>tablet</em>-based view of the applications since our breakpoints were so ridiculously large. Yikes.</p>
-<p>So, I said screw it and retired the external monitor. Now my X260 is propped up and proudly showing off its 1366x768 display. It only took a day or so to adapt to this new setup and I don&#8217;t think I could go back to another massive display.</p>
-<p>Here are some benefits at a glance:</p>
-<ul>
-<li>I no longer have to worry about &#8220;context switching&#8221; if I decide to un-dock my laptop and work somewhere mobile. The desktop experience remains intact.</li>
-<li>Working inside <code>dwm</code> is a much cleaner experience. I mostly operate single applications within their own confined tag - with some exceptions of course.</li>
-<li>I&#8217;m able to instantly understand frustrations of everyday users while developing new features or tweaking existing UIs. Being able to advocate for our end-users by using legit use cases is extremely helpful. (Removes the &#8220;design by gut-feeling&#8221; mistakes)</li>
-</ul>
-<h2 id="a-little-extreme">A Little Extreme</h2>
-<p>Yes, I am aware that I could simply keep the UHD monitor and perform my work within a constrained portion of the screen. The problem that remains is &#8220;quality&#8221;. Most 1366x768 panels are not even close to the level of hi-res found on most 4K monitors. By using such a display I would be cheating myself of the standard experience a good portion of my end-users endure. </p>
-<p>I want to see the fuzzy text, slightly blurred imagery and muted button shadows. I want to see these things because that&#8217;s how some <em>users</em> will experience it.</p>
-<p>Maybe that&#8217;s extreme - but it works for me.</p>
-<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