Professional software engineer, musician, gamer, stoic, democratic socialist

  • 3 Posts
  • 141 Comments
Joined 2 years ago
cake
Cake day: July 2nd, 2023

help-circle


  • Pretty sure my journey looked something like:

    1. Ubuntu for a while
    2. A furious bout of hopping experiments: Debian, ElementaryOS, Crunchbang, MX Linux, Fedora
    3. Arch for a bit, but it was too much struggle
    4. Ubuntu for a while, embracing the “vanilla” lifestyle
    5. Manjaro for a while. It seemed to solve my previous issues with vanilla Arch.
    6. EndeavourOS, basically a better Manjaro.
    7. NixOS, which had a significant learning curve but ultimately gives me the most control and repeatability for all of my machine configs. Still daily driving this on my desktop, router, and some web servers.
    8. Tried out Fedora Atomic on my old laptop out of curiosity. Installing packages was ultra slow. Workflows were too annoying.

    So I think the graph is actually pretty reflective of my own experience, aside from some of the specific distro choices during my peak ignorance phase, and obviously I ended up at NixOS which isn’t even on here.



















  • If you can achieve the desired UX on web, I see few reasons to build a native app. But of course it can be hard to work with web technology sometimes; Javascript and WASM can’t do everything and they aren’t the best developer experience compared to more moderns languages.

    Even for offline usage, there is increasing support for progressive web apps. For example, I don’t even need to be connected to the internet to use Exaclidraw after I’ve loaded the app once and installed it as a PWA.

    Then there are times when you simply need access to native platform APIs. SQLite is a a very important technology that isn’t easily used from a web app. Most of the powerful APIs you get from an OS like the file system or graphics APIs are extremely watered down for the web.