• 8 Posts
  • 122 Comments
Joined 1 year ago
cake
Cake day: May 31st, 2023

help-circle
  • So, OK, I’m willing to learn: please show me good brands then.

    They need to resist to mud (thick mud, the kind with a ton of suction that will keep your soles when you try and move), seawater, rocks and sand, and pretty dense vegetation.

    They also need to have steel toe caps, good soles (vibram or equivalent if possible) that don’t slip, and that aren’t too hard (wet stone is enough of a female dog as it is), and to go higher than my ankle.

    The best brand I tried so far was caterpillar, but they lasted only 3 years. That’s a far cry from “a decade or more”.




  • Yeah so, the amount of meals is correct. But that’s about it. I mean, I can’t say about the taste, to each their own, but one kg of cow meat needs two dozen kg of grain.

    That’s about as inefficient as it gets.

    As for the leather, the industry doesn’t like products that last a decade, so it isn’t actually using the leather in such a way. Industrial leather boots last a year tops.

    Finally, pet food is made out of discarded cuts of meat, the uglies, etc. But also lots of cereals, and vegetables.

    So we could really afford eating less meat. It isn’t good for anything. Not for us, not for the other species (certainly not for the cows, that get often half assed butchered in a hasty way because of quotas and profit), and absolutely not for the ecosystem.

    But I guess the taste is all that matters.








  • I’d argue that what is holding the Linux GUI back is the amount of options, combined with the lack of proper interoperability testing (not for the lack of trying, but between the amount of options and the amount of versions, it is absolutely unfeasible), and the lack of strong design choice on the side of distributions: everyone wants to have and support everything under the sun, even if it means having 4 or 5 different flavours or editions of a particular distribution.

    Don’t get me wrong, I salute the intention and the initiative, but concretely, this almost always (and I put “almost” to be safe, I’ve never seen a counter example) means a clunky, unpolished experience in most cases.

    I usually describe it as:

    If GUIs were doors:

    • Mac OS would be selling literally only one kind of door, that is super slick, brushed metal, glass and white, fancy, with a black glass and brushed metal handle, has a great feel to it, good heft, great handling, satisfying sound and feedback, etc, but then you need to buy everything else from them (including your lights, flooring, etc) or it just won’t open. Of course they sell everything at a premium.
    • Windows would be your standard wooden office door with the standard metal handle and the standard automatic door closer; but anyone can open it even when locked, it needs to be changed every other year, if you “customise” (i.e. adapt it in any way) it it will wear out 10x faster, and any adjustment you do (handle spring tension, automated closer strength and kickback, hinges adjustment, etc) will be reset at night randomly every other week, the door will get new “features” (like microphones, a search prompt, an assistant, etc) randomly, and you can use any kind of furniture you want, but during the “night resets” (aka “upgrades”), all the furniture in the office will be reset to be “Microsoft furniture”, and you will need to exchange it all back in the next morning. And for various unpredictable reasons, once in a while, when going through the door, it will close unexpectedly and violently, slamming you in the face with full force.
    • Linux and FOSS in general is a collection of community made IKEA inspired doors. You can mix and match anything. Any kind of door, any kind of hinge. Any kind of handle. Want a door that opens sideways? Go for it. Want a door that slides up? Do it. Want a butterfly door? Sure. A proximity sensor as a handle? Totally. A carbon fibres and ceramic door? Absolutely. All at once? Why not. In the end, no door is exactly the same, even across the same building, and you often need a few minutes to figure out how new doors work in new buildings. And of course, lots of doors are ill designed, with completely unnecessary features, and conflicting options, like both a sideways and butterfly hinge. Still works, but has caveats. But hey, if it breaks, or doesn’t fit, you can change it any time, get parts anywhere, and there is an absolutely insane amount of community made documentation on most of it (except the internals, some of it is hard to understand, some of it is absolutely obscure, and most of it is documented by people who made it exclusively for people who made it)

    IMHO what we would need is for distributions to “adopt” a given GUI (or DE), and stick to that. Do not even carry the packages for something else. If it is needed, another distribution will be made. That would simplify things a lot, and would greatly relieve the stress on maintainers.

    And it would make for a much more approachable user experience.



  • 7heo@lemmy.mltoLinux@lemmy.mlWhat distro should I use on my potato?
    link
    fedilink
    arrow-up
    8
    arrow-down
    4
    ·
    edit-2
    3 months ago

    Note: this comment is long, because it is important and the idea that “systemd is always better, no matter the situation” is absolutely dangerous for the entire FOSS ecosystem: both diversity and rationality are essential.

    Systemd can get more efficient than running hundreds of poorly integrated scripts

    In theory yes. In practice, systemd is a huge monolithic single-point-of-failure system, with several bottlenecks and reinventing-the-wheel galore. And openrc is a far cry from “hundreds of poorly integrated scripts”.

    I think it is crucial we stop having dogmatic “arguments” with argumentum ad populum or arguments of authority, or we will end up recreating a Microsoft-like environment in free software.

    Let’s stop trying to shoehorn popular solutions into ill suited use cases, just because they are used elsewhere with different limitations.

    Systemd might make sense for most people on desktop targets (CPUs with several cores, and several GB of RAM), because convenience and comfort (which systemd excels at, let’s be honest) but as we approach “embedded” targets, simpler and smaller is always better.

    And no matter how much optimisation you cram into the bigger software, it will just not perform like the simpler software, especially with limited resources.

    Now, I take OpenRC as an example here, because it is AFAIR the default in devuan, but it also supports runit, sinit, s6 and shepherd.

    And using s6, you just can’t say “systemd is flat out better in all cases”, that would be simply stupid.






  • 7heo@lemmy.mltoxkcd@lemmy.worldxkcd #2916: Machine
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    3 months ago

    It’s being DDOSed. Too many users. Too many submits. The rendering code is light enough on the server that it still works (most of the work is client side, the sever just serves a bunch of json files), but the submitting code definitely crashes.


  • 7heo@lemmy.mltoxkcd@lemmy.worldxkcd #2916: Machine
    link
    fedilink
    English
    arrow-up
    10
    ·
    edit-2
    3 months ago

    Cool, but it’s now impossible to submit anything, as the server is being DDOS’d. Not out of malice, mind you, there are just too many geeks out there, and this is a Sunday…

    Still, one can read the titles of the already posted rooms with:

    env URL=https://incredible.xkcd.com \
    curl -SsL $URL/machine/current \
    | jq .grid[][] | grep -v '^null$' | tr -d '"' \
    | while read uuid; do printf '%s: ' "$uuid"; \
    curl -SsL $URL/folio/$uuid \
    | jq .blueprint.title; done
    

    (Useful to find out if your room made it to the public set)