• 5 Posts
  • 1.22K Comments
Joined 5 years ago
cake
Cake day: May 31st, 2020

help-circle
  • Ephera@lemmy.mltolinuxmemes@lemmy.worldLinux and Chill
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 hours ago

    I would not throw Rust and C together in this.
    Rust is low-level in terms of being usable for kernel and embedded development (due to not needing a runtime), but it’s rather high-level in terms of the syntax offering lots of abstraction from the weirdness of the hardware.

    Some of that not-needing-a-runtime does bleed into the syntax, but in my opinion, it’s still higher level from a syntax perspective than Bash et al, because it brings in many functional aspects.

    I guess, I’m also just bothered by you saying, you don’t ‘need’ Rust for writing CLIs, when it’s my favorite language for this.
    To some degree, I do just find it ridiculous to launch a whole runtime when the user just wants the --help, but the argument parsing in Rust is also just really nice: https://rust-cli.github.io/book/tutorial/cli-args.html#parsing-cli-arguments-with-clap



  • Ephera@lemmy.mltolinuxmemes@lemmy.worldLinux and Chill
    link
    fedilink
    English
    arrow-up
    21
    arrow-down
    1
    ·
    15 hours ago

    Did he actually say that he likes it? My impression was that it’s not his comfort zone, but he recognizes that for the vast majority of young programmers, C is not their comfort zone. And so, if they don’t hop on this Rust train, the Linux kernel is going to look like a COBOL project in a not too distant future. It does not happen very often that a programming language capable of implementing kernels gains wide-spread adoption.




  • Ephera@lemmy.mltoComic Strips@lemmy.worldEndorphins
    link
    fedilink
    English
    arrow-up
    29
    ·
    4 days ago

    Different people have different levels of heat resistance. My dad will abort mission, if you shake the pepper shaker more than once. Obviously, he doesn’t have it in him to go back for seconds. I do, but having grown up in that household, it takes a while for the same heat resistance to build up. I bought sriracha for the first time a few months ago, and you could certainly still melt my face off with it, despite me using it again and again.


  • Ephera@lemmy.mltolinuxmemes@lemmy.worldDistro Focuses
    link
    fedilink
    English
    arrow-up
    1
    ·
    5 days ago

    Sure, it’s still just certainly a choice. It took me multiple years to realize why it’s so broken on TTYs, as well as when you run newgrp and probably other places.

    I thought Linux just sometimes goes into this buggy state, where you can’t make any typos. At one point, I broke my GUI session and had to fix it, typing commands off of my phone screen, without making any typos.

    Learning that this is Working As Intended™ just killed me…

    These days, I know that you can just run bash (or your shell of choice) to get out of this buggy state, and I still set bash as the system shell when I have to use a Debian-based system, because I just do not care about however much performance it brings in.


  • Ephera@lemmy.mltolinuxmemes@lemmy.worldDistro Focuses
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    1
    ·
    6 days ago

    I think, a more serious attempt to summarize openSUSE would probably be: Functionality

    Debian, Arch, Fedora and such are all weirdly similar in that they focus so much on minimalism. For example, Debian uses dash as the default shell, which breaks TTYs, but possibly squeezes out a tiny bit of performance, so I guess, that’s worth it…?


  • I think, your expectations are off for what a native integration would achieve. A kernel which has both a Linux API and a Windows API would be an insane maintenance effort. You’d naturally want the Windows APIs to simply be translated to the respective Linux API calls. This is what WINE does.
    In theory, if it’s directly integrated, you could do some dirtier stuff, i.e. call kernel-internal APIs, but you want to avoid that as much as possible, since those kernel-internal APIs are not nearly as stable as the public APIs.
    It should also be said that writing kernel-level code is hard. You cannot ever crash, you cannot ever make mistakes when managing memory, you cannot allow yourself any vulnerabilities. Again, you want to avoid writing kernel-level code, if you can.

    WINE has some additional ugly workarounds, like a virtualized filesystem. There’s not terribly much you can do about that. Windows applications may simply expect certain folders to be in certain paths. You can’t directly map that to a UNIX filesystem.

    As far as I can tell, pretty much the only advantage of natively integrating it, would be that it’s installed by default, which can be achieved in other ways (distros), and due to those ugly workarounds will not be popular at all. As much as I’m touting its horn right now, I do not want WINE on my system, unless I need it.

    It’s easy to be frustrated with WINE, because it does not handle all applications perfectly, and then think that the approach is just wrong. But yeah, no, some really smart folks came up with that approach. It’s just insanely hard to get the exact (undocumented) behavior of the Windows kernel APIs correct, whether you do a mapping or implement them natively.


  • Ephera@lemmy.mltoComic Strips@lemmy.worldWide Cars
    link
    fedilink
    English
    arrow-up
    6
    ·
    7 days ago

    Yeah, I was expecting it to be a joke like:

    • Introducing Longtrucks. 🚌
    • Impress even more strangers of the superior person-hauling capabilities with 32 seats.
    • Includes a light-up sign 🚍 so you can proudly show to strangers where you’re headed.
    • Access a world-wide network of pick-up bays 🚏 for you to pick up strangers from.