• elouboub@kbin.social
    link
    fedilink
    arrow-up
    25
    arrow-down
    3
    ·
    1 year ago

    Indeed, nothing is perfect, but closed source stuff doesn’t provide a lot of recourse. If you have a linux expert in your team, they can investigate and if need be even dig into the code of linux itself to find the core issue. Microsoft doesn’t provide anything even remotely similar.

      • elouboub@kbin.social
        link
        fedilink
        arrow-up
        16
        ·
        1 year ago

        Don’t need one. If you can read C/C++ you can read the kernel code. And in most cases, you won’t have to, as the problem is probably in a component in the distro. Those are written in python, ruby, or bash, which are all much more readable than C/C++.

        No such luck on windows

      • sugar_in_your_tea
        link
        fedilink
        arrow-up
        6
        ·
        1 year ago

        I worked at a small company without a kernel dev and we periodically looked into the code to solve problems. I don’t know how much we upstreamed, but we relied on Linux so it was either the or try to get someone on the mailing list to care.

        It’s really not that hard to look through the kernel source, it’s pretty well written and documented. It’s a lot harder to be a kernel developer writing new code, but finding bugs and contributing fixes isn’t that bad.