189
this post was submitted on 25 Aug 2023
189 points (97.0% liked)
Technology
34436 readers
223 users here now
This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.
Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.
Rules:
1: All Lemmy rules apply
2: Do not post low effort posts
3: NEVER post naziped*gore stuff
4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.
5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)
6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist
7: crypto related posts, unless essential, are disallowed
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
How many dev teams have a kernel dev on them?
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
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.
You don't have to be a kernel dev for that. Reading source code is much easier than writing it. I myself have even read the code that handles the battery management drivers, and it's mostly self documenting, even though I'm bad at C and it's pointers, and also have never yet written a kernel driver.