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/)N
Posts
17
Comments
77
Joined
2 yr. ago

  • I have adhd and my idle stim is shifting my weight from one foot to the other. I'm like a living metronome. Drives people crazy.

  • I would much rather learn a new word than slog through a glib deluge.

  • I use ! to sort to top, and Ω to sort to bottom. So far haven't had any compatibility problems.

    For the curious: the use case for this is when you want to reduce nesting but also want a sort of "soft hierarchy" within a folder. I could separate my music folder into albums and playlists, but then I'd have a mostly empty folder, so instead I put both in the same directory and use prefix naming to sort them.

  • if the states aren't obvious, use an enum with two values, and name them both. Thats what enums are for.

  • ah, yeah, if you have an android game without built-in controller support then you're out of luck right now, sorry.

  • Retroarch and Steam Link both have android apps and support controller mapping, but I don't know of any OS-level tools.

  • Tra-la-la!

  • Starting anything from scratch is a huge risk these days. At best you'll have something like the python 2 -> 3 rewrite overhaul (leaving scraps of legacy code all over the place), at worst you'll have something like gnome/kde (where the community schisms rather than adopting a new standard). I would say that most of the time, there are only two ways to get a new standard to reach mass adoption.

    1. Retrofit everything. Extend old APIs where possible. Build your new layer on top of https, or javascript, or ascii, or something else that already has widespread adoption. Make a clear upgrade path for old users, but maintain compatibility for as long as possible.
    2. Buy 99% of the market and declare yourself king (cough cough chromium).
  • Firefox had tab grouping first. Before Chrome. And then it broke support for it when they did the add-ons overhaul. I'm surprised bringing it back wasn't a high priority...

  • optional autocomplete is a nice-to-have, eager autocomplete is a pain in the ass. as long as it only completes when I ask it to, I don't mind.

  • My experience with pacman was via rwfus on steam deck. I was coming in as someone with experience with apt, npm, pip, even choco and winget on windows. My expectation from pretty much every other command line tool is that commands are verbs, flags are adverbs. So having to install with "pacman -S" (or is it "pacman -Sy"?) just feels unnecessarily cryptic. Same with "nix-env -iA". I understand that there are some clever internals going on under the hood, but you can have clever internals and sane defaults. For instance, "npm install foo" both downloads the package to node_modules and updates package.json for me, so I can see what change was made to my environment. Nix should do that.

  • I've also seen it as pacman -Sy and pacman -Syu and so on. I really just think "install" should be a subcommand, not a flag. That's really my only issue I guess, I've only ever used pacman via rwfus on steam deck so maybe my usability problem is with that.

  • pacman and nix are both really neat conceptually but they both fail at the most obvious usability test, which is "I just want to install a package"; its like exiting vim all over again.

    edit: yes, I know you can set an alias to pacman -Sy or whatever, but if you need to set up an alias for a command to be usable, then I can't in good faith recommend that OS to anyone, and I don't want to use an OS I wouldn't recommend to others.

  • If you're gonna dismiss it like that then I'd love to hear what your pain points are. What's so bad about containers for multi-platform applications?

  • Hey, don't claim to represent my opinion if you don't understand my reasoning. I don't think art is mystical or spiritual at all, not in the way you're describing it. Art is absolutely about patterns, and I agree that those patterns are inevitably going to be learned by computers.

    My objection is not to "AI Art" in general, but to the specific type of art which is brute-force trained to mimic existing art styles. When organic artists take inspiration, they reverse engineer the style and build it up from fundamentals like perspective and lighting. Stable Diffusion and other brute-force ML algorithms don't yet know how to build those fundamentals. What they're doing is more like art forgery than it is like art.

    And even then, I don't really take issue with forgery if it's done in good faith. People sell replicas of famous paintings, and as long as they're honest about it being a replica, that's cool too. Ethically my objection is that AI artists typically "hide their prompts" and try to sell their forgeries as originals.

  • Go look up the existing arguments against AI, and write your rebuttal to those, and then debate people about it. More productive for everyone involved.