Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)WA
Posts
2
Comments
498
Joined
2 yr. ago

  • I wish philosophy was taught a bit more seriously.

    An exploration on the philosophical concepts of simulacra and eidolons would probably change the way a lot of people view LLMs and other generative AI.

  • The problem is that the road between creating a piece of software that does something well, and then creating simplification layers on top of it is typically much longer than just "edit a config file" and "here's a readme".

    You need extra documentation, config gating and workflow, warnings, UI/UX work etc.

    I know there are Linux elitists but kind of expecting that much extra work for what is still at it's core mostly volunteer software seems like it's own form of elitism.

  • Some additional nice things about guix:

    Everything is guile. The system definition, the service definitions for shepherd, everything.

    Shepherd is hands down the best init program I've ever used. It's just incredibly simplistic but because it just runs the guile definition you give it, you can do some incredibly complex things that systemd etc. can do as well.

    The OS documentation is built into the distro, with "info guix" you get reams of configuration information for the distro without ever needing to look it up online.

  • About a year and a half.

    To be honest it's not "easy" to use. The guiding principle behind mainline packages is that everything has to be built from source, so most somewhat unpopular things are missing from the mainline channels.

    To use it like any other distro you're going to need to learn how to write packages fairly quickly. Luckily the main draw of guix is the entire OS being based on guile so once you get a little under your belt you can just read the specs from other channels to see how a package is written.

    Took me maybe a week to start writing guix packages.

    There's also The toybox

  • From my experience it's quite the opposite, cause when something breaks in guix/nix/bazzite you basically need to know how the entire subsystem works to troubleshoot it.

    You can't just copy paste some nonsense from superuser to fix it.

  • Permanently Deleted

    Jump
  • You really gotta hope those 5-10% LLM interpretive miss rares don't hit your particular case.

    Also if it fucks up, the doctor is still liable for malpractice right? Or do they get to kick that ball down into the abyss of trying to get LLM companies to take responsibility for their products.

  • There's been a lot more evangelism about emacs lately.

    Also the fact emacs has doom and spacemacs to ease new users in while vim drops you into : and tells you to swim means that it's easier for emacs to get new users.

  • In terms of getting to an exact location, the most efficient is no vehicle, walking.

    Cars are less efficient, followed by busses, then probably trains, then boats, then airplanes (unless you parachute).

    Cars are the least efficient in terms of moving large numbers of people from places they can then walk from.

  • Weirdly enough because of the way mergerfs does writes across multiple drives, the main issue that FUSE filesystems face performance wise (namely writing a bunch of small files and their metadata) actually gets pretty well mitigated.

  • If you built a house in Japan now for the cost of 100k the house would be worth 50k in 30 years.

    Real estate in Japan appreciates like cars, unless you have an especially rare piece of land, it depreciates over time. It's a bad investment unless you're actively getting use out of it.

    Part of why there's so much cheap and abandoned land in Japan, there's no real estate investment structure outside of land near train stations.