• 3 Posts
  • 118 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2024

help-circle

  • Honestly this made me really sad that we’re stuck with this archaic, awful language as a primary way of programmatically interacting with our computers. And I don’t mean to say anybody has done anything wrong here - sh and bash were revolutionary and amazing for their respective times, and maintainers who are keeping bash alive now are heroes who deserve praise. However, many decisions made when sh was originally developed turned out to be footguns, still creating bugs today (despite shellcheck et al).

    nushell is somewhat promising but flawed (because it has to be built on the same system interfaces as sh, after all). The most annoying is that there’s no facilities for setting any metadata on data streams (in particular there’s no way to set the format of the data) so everything has to be marshalled manually, which would be OK for a proper programming language but really annoying for a shell. At least it fixes most of the quoting, escaping, interpolation, substition etc awfulness, and allows for manipulating data in a more structured way.

    I really don’t know if it’s even possible to make a language that would be a good convenient shell and at the same time not prone to bugs which are easily noticeable in other languages. I hope that something like this becomes a reality at some point.




  • There should be no updating unless enabled <…> and never nag the user.

    I disagree, at that point you might as well continue using Win10. Security updates are the #1 reason to do this. Most computer use nowadays is networked (actually in a browser), and it’s super important we keep that updated.

    If updating is turned on, it should be very conservative, updates hand curated by grandmasnixos, basically never uses software that hasn’t been proven rock solid for at least 6 months

    Eh, this sounds like a lot of work. Probably just use the stable channels, and only manually test when switching to a new stable channel.

    Rolling back any update should be one-click-trivial

    Agreed, should also be very obvious (like a label on the desktop that says “Issues after update?” and gives you a button to roll back and reboot)

    The desktop environment should be something occasional win10 using grandma will not get lost in

    This is the main question IMHO. I’ve not used any DEs for a while, so don’t really know which one would fit this best while also being simple and robust.


  • I think we can be even simpler than that. Don’t ask any questions. Simply generate the hardware-configuration.nix and have a single configuration.nix that is unchanged:

    • Some easy-to-use and simple DE. I’m thinking something like lxqt or xfce, maybe Pantheon - but that would be more familiar to Mac users than Windows. KDE seems way too complicated to just have it in configuration.nix without touching it, and it can sometimes break on updates.
    • Chromium (with pre-installed ublock origin)
    • Libreoffice
    • Some flatpak store (so that people can install apps without touching configuration.nix)
    • Make a simple “update” app that just pops up once in a couple weeks or so, prompts you to click a button and then runs npins update and nixos-rebuild boot, and finally annoys you until you reboot (it should also update to the next stable channel when that becomes available, and make that a big deal so that a user understands it might change some of their workflows)
    • Set up the bootloader so that if a generation “fails” (some script in the autostart of the DE doesn’t set a flag somewhere) on the next boot it boots a previous generation, kinda like Android’s A/B slot system but better. I don’t think systemd-boot allows this sort of thing, but I think it’s possible with a GRUB script
    • Maybe add a shortcut to open tmate and copy the URL to clipboard, so that you can send it someone in the know and they can help you troubleshoot
    • Finally, use impermanence to make sure everything outside /home, /nix, and wherever flatpak are stored, is wiped on every reboot and recreated from the generation, so that “reboot it” is a viable troubleshooting strategy.



  • Most consumer hardware on earth does already (Android phones). The problem is those drivers are usually proprietary bullshit that’s very difficult to integrate with anything but OEMs kernel fork & Android version. Unfortunately I don’t really foresee that changing in the near future, hopefully if Linux becomes more mainstream, Linux phones become too and then we get some progress.

    And for laptops/desktops, I think the situation is pretty good already as well. Many mainstream OEMs have an option with Linux pre-installed now, and the drivers there are mostly FOSS. I’m hoping that the problematic part vendors e.g. NVidia and Broadcom step up and provide sources for their drivers - otherwise they will continue to be a buggy mess that most people hate.



  • Physical media is the only media you really own.

    Hard disagree. You can own any file encoded with an open standard. And it’s easier to index, search, manipulate, back up, etc. It feels more like owning than having the data on a micrometer-thick metal layer sandwiched in a fragile plastic disc that can easily scratch or discrot. There is a reason people have been ripping CDs since PC CD drivers became a thing.





  • Honestly I don’t think that’s tru. There were very few kids who truly tinkered with their computers in the old days too - first because not many kids had computers in the first place, and then because computers started being useful without any tinkering. There are still a lot of youths (12-16) today who are flashing LineageOS on their phone or installing Linux on their Chromebook, or whatever. I know because they keep flooding the NixOS Telegram chat that I’m managing - and I try to welcome them with open arms!


  • smartphones are a black box.

    Many Android phones still have a bit of that tinkering ability to them (you kinda have access to the file system, and you can root them/flash custom android distros), but it’s quickly diminishing because (1) OEMs are locking the bootloaders, (2) it’s getting harder and harder to get hardware working without proprietary OEM hacks, (3) bank apps and other proprietary garbage that’s becoming a necessity in modern times refuses to run on an unlocked phone.