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

help-circle
  • Ephera@lemmy.mltolinuxmemes@lemmy.worldDistro Focuses
    link
    fedilink
    English
    arrow-up
    1
    ·
    14 hours 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
    ·
    20 hours 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.





  • On KDE, there’s actually a separate feature which provides essentially virtual desktops with changing wallpapers (and widgets and a few other things), which is called “Activities”. You can also then use multiple virtual desktops per Activity.

    I think, that’s kind of the main reason: Many people use virtual desktops differently.
    For some folks, they represent different larger topics, where the Activities feature would match very well.
    For others, virtual desktops are more like a second monitor, so they just want to see different windows, nothing more. In fact, some desktop environments like GNOME, create and destroy virtual desktops per demand. They couldn’t really remember the wallpaper for those workspaces.


  • Well, they’re similar in the widest sense, that they’re both strategy games, you have to produce resources and fight battles to capture land.

    But within the strategy genre, they’re actually pretty different. Civilization is turn-based, Widelands/Settlers is real-time strategy. I guess, the latter is at least still relatively slow-paced.
    Widelands/Settlers puts a lot more focus on managing supply chains. To produce bread, you’ll need a baker, which needs flour and water, and possibly coal, so you need a mill and a farm and a well and a coal mine, and then you need people to actually carry the resources between the buildings, and yeah, it starts to become pretty busy pretty quickly.
    If you ask fans of these games, that’s kind of what they love the most, that your settlement starts to look like an anthill buzzing with activity in no time.











  • Ephera@lemmy.mltoMemes@lemmy.mlGetting harder as I get older
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    11 days ago

    Today, a colleague couldn’t do docker login for an internal registry. Constantly got an error which just said “unauthorized”.
    The password couldn’t be the problem, because you actually generate a token on the registry webpage, so we tried all the different ways to spell his username (uppercase, lowercase, e-mail address) and tried different URLs for specifying the registry, tried toggling the VPN, a reboot etc., even though we knew what should work, because the login worked for me.

    Eventually, we gave up and figured there must be some permission problem in the registry. Ten minutes later, he tells me that it works, without doing anything different. Now I’m wondering, if the IT saw our desperate login attempts and quickly fixed the problem. 🫠