I think that is somewhat correct. Last year I worked on over 20 Aiot Dev kits and what I found was there was a lack of Gnu Linux knowledge... To the point I needed to edit config files and build modules. Modules existed but they didn't even build them or load to the kernel. I mean let's be honest here, there are a lot of these windows developers trying to work on Linux and they don't even know how to roll out a package. I also have been using gnu Linux for over 20 years and I think maybe my insight about being new to Linux is not as applicable... But I can say that I recently converted a process workflow to remove proprietary software and this long-drawn Windows GUI workflow was replaced with a 20 line bash script... and this definitely improved my productivity!
Certainly - however, at this stage of Linux development, users expect the drivers to their hardware to be present and configured "out of the box". Very few new users will have the type of skills necessary to discover the correct driver/module, configure it or compile it for their kernel, especially if it requires tweaking the device tree.
As to the productivity gains, that is the reason I switched all those years ago. I prefer a system that I need to configure once, that works efficiently and without breakdowns, to one that automatically detects and configures new hardware, but breaks down over time and becomes unusable.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think that is somewhat correct. Last year I worked on over 20 Aiot Dev kits and what I found was there was a lack of Gnu Linux knowledge... To the point I needed to edit config files and build modules. Modules existed but they didn't even build them or load to the kernel. I mean let's be honest here, there are a lot of these windows developers trying to work on Linux and they don't even know how to roll out a package. I also have been using gnu Linux for over 20 years and I think maybe my insight about being new to Linux is not as applicable... But I can say that I recently converted a process workflow to remove proprietary software and this long-drawn Windows GUI workflow was replaced with a 20 line bash script... and this definitely improved my productivity!
Certainly - however, at this stage of Linux development, users expect the drivers to their hardware to be present and configured "out of the box". Very few new users will have the type of skills necessary to discover the correct driver/module, configure it or compile it for their kernel, especially if it requires tweaking the device tree.
As to the productivity gains, that is the reason I switched all those years ago. I prefer a system that I need to configure once, that works efficiently and without breakdowns, to one that automatically detects and configures new hardware, but breaks down over time and becomes unusable.