• 0 Posts
  • 68 Comments
Joined 10 months ago
cake
Cake day: December 16th, 2023

help-circle

  • “releasing the modified version to the public” would cover them re-closing the source and then subsequently releasing that newly closed source, so they can’t relicense it and then release the built version of the code.

    At least not easily, this is where court history would likely need to be visited because the way it’s worded the interpretability of “modified” in this context would need to be examined.




  • The problem is that the Linux kernel is monolithic so introducing rust into it does have certain repercussions about downstream compatibility between modules.

    Right now the rust code in the kernel uses c bindings for some things and there’s a not-insignificant portion of C developers who both refuse to use rust and refuse to take responsibility if the code they write breaks something in the rust bindings.

    If it was pure C there would be no excuse as the standard for Linux development is that you don’t break downstream, but the current zeitgeist is that Rust being a different language means that the current C developers have no responsibility if their code refactoring now breaks the rust code.

    It’s a frankly ridiculous stance to take, considering the long history of Linux being very strict on not breaking downstream code.


  • Well part of what it does is grab your actual desktop background to use, and there’s a couple different ways to do that on Linux afaik

    Also I guess the file dialogs would open only to the wine prefix? My experience with wine applications and dialogs is mostly through bottles, so I’m not sure of the sandboxing…







  • WalnutLum@lemmy.mltoMemes@lemmy.mlZen Z
    link
    fedilink
    arrow-up
    2
    ·
    1 month ago

    Yea that’s kind of what I was thinking when I said eventually handwriting will go the same way.

    If people never encounter it and do all their writing on keyboards, it’ll eventually be a useless skill as well.


  • WalnutLum@lemmy.mltoMemes@lemmy.mlZen Z
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 month ago

    From a practicality standpoint, a round clockface is easier to create a mechanical drive system for.

    You can create a digital mechanical face (see: Flipboard style numerical displays) but they usually require more gears and are more susceptible to wear and tear than the gears of a round clock face.

    The simplest designs for mechanical digital displays actually just take 24 hour and 60 minute/second circular displays and hide the other numerals as the clock face spins around. Technically this I suppose counts as both analog and digital?

    Example:

    Image

    As for electronic displays? Nah not much of a reason to use a round display unless again, you have an electric-mechanical drive and want to save on gears and parts.


  • WalnutLum@lemmy.mltoMemes@lemmy.mlZen Z
    link
    fedilink
    arrow-up
    4
    arrow-down
    2
    ·
    1 month ago

    It floors me just how many people in this thread feel like analog clock reading is a useless/outdated skill.

    But I’m of the opinion that there’s no such thing as a truly outdated and useless skill, so I’m not sure I have the capability to empathize with those people…




  • You can use nix alongside guix, it’ll just double-up the dependencies on disk:

    services (append (list (service nix-service-type))
                        %base-services)))
    

    Services are, in guix terms, any configuration change to a computer, so creating your own service 99% of the time is just extending etc-service-type and creating a variable interface to fill in the config file text yourself

    Creating a service as in a daemon of some kind uses shepherd and involves extending shepherd-service-type or home-shepherd-service-type with your service description, depending on whether the service runs in root or user space.

    Shepherd service configurations aren’t actually part of the guix spec(https://www.gnu.org/software/shepherd/manual/shepherd.html#Defining-Services), but still use Guile, so you can interoperate them super easily.

    It’s important in guix to understand lisp pretty thoroughly, and knowing how to program lisp is still a very useful skill to have so I’d recommend learning it even if you never touch guix.


  • I use guix because, while it has a small community, the packaging language is one of the easiest I’ve ever used.

    Every distro I’ve tried I’ve always run into having to wait on packages or support from someone else. The package transformation scheme like what nixos has is great but Nixlang sucks ass. Being able to do all that in lisp is much preferred.

    Plus I like shepherd much more than any of the other process 0’s