I strive to work towards a better (IMHO obviously) world in which well designed tools empower knowledgeable users to accomplish the tasks at hand.
#Postview software software#
Then it did exactly what it told the user it would do.Īs a software developer, I don't want to work in a world where the end user is 100% unaccountable for their actions.
#Postview software Patch#
While the apt tool could've just opted to not do this stupid thing (note: System 76 has already patched their version to ensure this and is attempting to get the patch upstreamed with Debian), it instead opted to provide the user with a transparent accounting of everything that would happen if he chose to proceed. but he made it a thousand times worse by treating the system like a black box which produces output and warnings that can be safely ignored. It turns out however that a large percentage of the Linux community disagrees with this assessment, especially the Tech Linux YouTube contingent who have thus far universally expressed sympathy for what happened to Linus. But I do blame them when they open a shell, run a command with root privileges and utterly ignore the warnings its plastering across the screen about very bad consequences and tell it to proceed anyway. While it was fixable, I don't blame any new Linux user for cutting lose of the distro and trying something else at this point. Oh sure he didn't read any of the warnings in the terminal where apt informed him that proceeding might result in catastrophe, but that doesn't absolve him of responsibility for authorizing it.
However Linus decided to give the system permission to do whatever it decided it needed to do to fix the issue, consequences be damned.
#Postview software install#
See up until this point, he just couldn't install Steam. Bravo to Linus for even being willing to open the shell as his recent Linux related diatribes on the WAN show seemed to indicate that he was generally opposed to this idea.īut its what happens next that really forces me to put a lions share of the blame for this on Linus. Hell I install almost everything via the shell anyway so this is hardly a problem. Linus on the other hand, decided to drop down to the shell and install Steam that way. So I decided to just open a browser tab and play DCSS (and yes by play I mean lose) while I waited for Steam to get fixed. This is not a condemnation because I'm a long time Linux user with lots of experience adapting to bugs that pop up. Well Linus reacted to this differently than I did. How you react and adapt to the bug means everything.
Somebody had already reported the bug so I helped to triage it on Github. To be clear, when I upgraded to 21.10 beta on the day of release, I experienced this bug myself. The long and short of it is that he tried to install Steam, but Pop! was currently suffering from a bug in which certain dependencies for that package were missing so it refused to install Steam. The reason why is because Linus ran into serious problems with Pop! during his portion of the video. He was a valuable resource for Pop! So what happened? The Twitter hate train happened after the release of the video. The purpose of this post is to discuss some of these consequences.įor starters, one of the most prominent developers for Pop! OS, Jeremy Soller, has decided to step back from it and work on other projects at System 76. Of course while it all seemed like good fun to most people, a lot of negative and some positive consequences came out of that video. So here we are, living in a world where Linus Tech Tips has released its first Linux challenge video.
0 kommentar(er)
