4 ms·
In my experience, those "some guys" do a lot of just that: talking. If they get code out to the public, it's utterly undocumented, the source code is unintellig
by jarcane 11y ago
In my experience, those "some guys" do a lot of just that: talking. If they get code out to the public, it's utterly undocumented, the source code is unintelligible, and fails to compile or install most of the time, but everything's fine according to him because "it works on my hardware."
- justinclift 11y agoThe "some guy" in this case is a well known Linux developer, working for Red Hat (last I heard). He's not a clueless, random noobie. ;)
- hinkley 11y agoMy last Linux machine was a Fujitsu lifebook, and the best ACPI firmware available for it was on Windows. The second best one was mine, cobbled together from a guy who solved less than half the problems, a guy who no longer had a Lifebook, and an idea from another guy to try to backport things from a later model. I probably blew a hundred hours of weekends and weeknights to get 50 minutes of run time out of my machine and something like five people benefited from it. When Apple came out with a 13" laptop that was less than a pound heavier (with the real battery, not that shitty fake one that was 90 minutes of run time) and happened to run a video game I was interested in, I said screw this and jumped ship. And suddenly I understood those guys who had been showing up to tech meetups for a year or two with MacBooks. I can spend all my time futzing with my machine like a classic car aficionado, or I can get out and enjoy doing things with it. Once I realized that I had never actually wanted to learn Linux, I just wanted to use it to learn other things, I couldn't go back. I still occasionally maintain Linux boxes, and sometimes bash, find or sed is the answer to a problem, but with the exception of Docker you literally have to pay me to use it.