blog

Personal blog
git clone git://git.laack.co/blog.git
Log | Files | Refs

constrained-software-revolution.html (6811B)


      1 <!DOCTYPE html>
      2 <html xmlns="http://www.w3.org/1999/xhtml">
      3 <head>
      4   <meta charset="utf-8" />
      5   <meta name="generator" content="pandoc 3.11" />
      6   <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
      7   <title>constrained-software-revolution</title>
      8   <style>
      9     /* Default styles provided by pandoc.
     10     ** See https://pandoc.org/MANUAL.html#variables-for-html for config info.
     11     */
     12     span.smallcaps{font-variant: small-caps;}
     13     div.columns{display: flex; gap: 1.5em;}
     14     div.column{flex: auto;}
     15     @media screen {
     16     div.columns{gap: min(4vw, 1.5em);}
     17     div.column{overflow-x: auto;}
     18     }
     19     div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
     20     /* The extra [class] is a hack that increases specificity enough to
     21        override a similar rule in reveal.js */
     22     ul.task-list[class]{list-style: none;}
     23     ul.task-list li input[type="checkbox"] {
     24       font-size: inherit;
     25       width: 0.8em;
     26       margin: 0 0.8em 0.2em -1.6em;
     27       vertical-align: middle;
     28     }
     29   </style>
     30   <link rel="stylesheet" href="style.css" />
     31 </head>
     32 <body>
     33 <h1 id="constrained-software-revolution">Constrained Software Revolution</h1>
     34 <p><a href="constrained.net">constrained.net</a></p>
     35 <hr />
     36 <p>General flow:</p>
     37 <ol type="1">
     38 <li>explain the issues today
     39 <ul>
     40 <li>slow software</li>
     41 <li>buggy software</li>
     42 <li>abusive software</li>
     43 </ul></li>
     44 <li>explain the reasons</li>
     45 <li>introduce constrained software
     46 <ul>
     47 <li>definition</li>
     48 <li>examples</li>
     49 </ul></li>
     50 <li>why not just xyz
     51 <ul>
     52 <li>suckless
     53 <ul>
     54 <li>too focused on advanced usage</li>
     55 </ul></li>
     56 <li>minimalist
     57 <ul>
     58 <li>minimalist is synonymous as long as it’s extended to computational minimalism. While less features / complexity is good, a python program with few features is still often not constrained</li>
     59 </ul></li>
     60 </ul></li>
     61 <li>moving forwards, how to contribute, stuff like that
     62 <ul>
     63 <li>is foreseen constrained software
     64 <ul>
     65 <li>it works from a termainal so accessible</li>
     66 <li>it works on low end devices</li>
     67 <li>I think distribution wise it’s limited, but that’s a nice to have not a requirement</li>
     68 </ul></li>
     69 </ul></li>
     70 </ol>
     71 <hr />
     72 <p>Software has been atrophying for years. Every release of Firefox is more bloated and complex than the last, every release of Chromium the same. New websites from today are slower than they were last month, year, and decade.</p>
     73 <p>For all of the claims about caring about inclusion, people seem to not notice how exclusive they are being. When you make software that’s slow, buggy, and complicated you’re excluding people. People who have slower computers, who use different operating systems, who have disabilities, and who want to make their own standards-compliant software. Slow down and consider this: Is you’re click-jacking website harming or helping people? Is adding that ill considered feature to Firefox that only slows down startup time by 5ms (on your computer) really worth adding? Every choice in this process leads to the atrophying of software, and leads to the here and now.</p>
     74 <p>In some ways, software is better now than it’s ever been before. My text editor, vim, is marginally better than it was 20 years ago, and if it wasn’t, I’d just build that version instead, but when people treat their software like milk that spoils quickly, we don’t have the luxury to go back in time and use what we had. Most people, misguidedly, interact with computing systems via the internet, a transient, spoiling, slow, inaccessible hellscape.</p>
     75 <p>It doesn’t have to be like this.</p>
     76 <h2 id="constrained-software">Constrained Software</h2>
     77 <p>Definition:</p>
     78 <ol type="1">
     79 <li>Performs a constrained set of functions</li>
     80 <li>Is usable on constrained systems</li>
     81 </ol>
     82 <p>This is the entire definition. Let’s break these down.</p>
     83 <blockquote>
     84 <p>Performs a constrained set of functions.</p>
     85 </blockquote>
     86 <p>A cohesive functions. A few things that come to mind:</p>
     87 <ol type="1">
     88 <li>Dillo</li>
     89 <li>Mpv</li>
     90 <li>Lagrange</li>
     91 </ol>
     92 <p>Dillo is designed to browse the web, with plugins to browse alternative protocols too. This is cohesive. It is for browsing, and the additional features aid in this.</p>
     93 <p>Mpv is a useful tool for displaying many video formats, coming from many sources. This is not a small task as there are many video file formats, and it supports video streaming from sites as well.</p>
     94 <p>This small set of functions must be cohesive, it wouldn’t make sense for your text editor to have an rss feed built into it, but conversely tools that are too small in scope become tedius to use directly.</p>
     95 <blockquote>
     96 <p>Respects the user</p>
     97 </blockquote>
     98 <p>To respect the user, software must be accessible. This means it works across a variety of system configurations and is usable by people with many types of impairments. It must also not do things they don’t want, like spy on them.</p>
     99 <blockquote>
    100 <p>Simple</p>
    101 </blockquote>
    102 <p>Complicated software is what has led to the situation we have now. Complicated software entrenched a duopoly of browser engines,</p>
    103 <h2 id="so-suckless">So Suckless?</h2>
    104 <p>Not quite.</p>
    105 <p>From their website:</p>
    106 <blockquote>
    107 <p>Our project focuses on advanced and experienced computer users</p>
    108 </blockquote>
    109 <p>This is one distinction. There is an underserved niche of software for experienced users, but I don’t believe constrained software should necessarily target this niche. Grandmas should be able to use constrained software; it’s built to be intuitive and simple.</p>
    110 <p>Consider Dillo. There are advanced features, facilitated by its plugins system, but the base browser is exceptionally approachable. I’d argue it’s more approachable than Chromium. I won’t claim it would be preferred by many users in its present state, but slight improvements to the usage experience to keep up with modern standards (some stuff with settings and first pass rendering missing css sometimes) would certainly make it as usable or more usable.</p>
    111 <p>The problem right now is most sites people patronize don’t work without j<strong><em>s</em></strong>**. I’ve accepted sites like that aren’t made for me, but it requires widespread disdain to make it known people are sick and tired of this.</p>
    112 <hr />
    113 <ul>
    114 <li>constrained software
    115 <ul>
    116 <li>this is a nice name, but it’s not a unique enough word</li>
    117 <li>if I search suckless, I find suckless.</li>
    118 </ul></li>
    119 <li>unflashy software</li>
    120 <li>workhorse software</li>
    121 <li>scopeful software
    122 <ul>
    123 <li>software with a sensible scope</li>
    124 </ul></li>
    125 <li>tractable software
    126 <ul>
    127 <li>software that is doable for an individual</li>
    128 </ul></li>
    129 <li>practical software</li>
    130 <li>bloatless software
    131 <ul>
    132 <li>software without the bloat</li>
    133 </ul></li>
    134 <li>respectful software</li>
    135 </ul>
    136 </body>
    137 </html>