Slashdot Mirror
Linux Sucks (Video)
How do we know Linux sucks? Because Bryan Lunduke says so. How did he become a Linux authority? By using Linux, of course. He has also written a kids Linux book, Linux for Hank, and a grown-up Linux book, Linux is Badass. But wait! That's not all! Bryan is also one of the people behind the infamous Bad Voltage podcast.
And now, for something slightly different: In moments of weakness, Bryan admits that maybe Linux suckage isn't total, and Linux may have a good point or two and maybe some of the suckage could be removed. Zounds! Is that possible? Watch our video chat with Bryan (and/or read the transcript) and see. Or watch the entire 44 minute speech he gave at the 2014 LinuxFest Northwest, which was the 5th (or maybe 6th) "Linux Sucks" speech he's given at LFNW. That makes this a tradition, not just a speech. So if you find yourself in or near Bellingham, Washington, in 2039 you might want to pop in and see if Bryan is still updating his "Linux Sucks" speech. He'll be the geezer hobbling to the front of the room with help from his AutoCane, a device sure to be developed between now and then -- which will no doubt run Linux. (Alternate video link)
And now, for something slightly different: In moments of weakness, Bryan admits that maybe Linux suckage isn't total, and Linux may have a good point or two and maybe some of the suckage could be removed. Zounds! Is that possible? Watch our video chat with Bryan (and/or read the transcript) and see. Or watch the entire 44 minute speech he gave at the 2014 LinuxFest Northwest, which was the 5th (or maybe 6th) "Linux Sucks" speech he's given at LFNW. That makes this a tradition, not just a speech. So if you find yourself in or near Bellingham, Washington, in 2039 you might want to pop in and see if Bryan is still updating his "Linux Sucks" speech. He'll be the geezer hobbling to the front of the room with help from his AutoCane, a device sure to be developed between now and then -- which will no doubt run Linux. (Alternate video link)
And why should I give a shit what his opinion is?
OpenSSL doesn't listen to bug reports. They don't even accept offered patches to known bugs. It's this spirit of non-cooperation that caused the forking into LibreSSL. See the 30 day prospectus (/. coverage) from the LibreSSL project lead, which details all of the problems. Brian even says forking is ultimately a benefit, and that he "loves that they're doing it."
It seems to be that his definition of "sucks" is "has room for improvement" ... Everything has room for improvement, so apparently everything sucks.
Use my userscript to add story images to Slashdot. There's no going back.
...at least with Linux, we have the power to do something about it without the constant hassle of a commercial system with all its secrecy, NDAs, policy approvals and we don't have to hide the fact we screwed up in order not go get sued by every paying customer, we just FIX it...and then another bug appears, but hey...have you ever found any human to be perfect? When you bought your first house, was it perfect? I bet not.
At least with OPEN SOURCE everyone is free to chip in, that is the magic of Linux. Suspect a bug? A backdoor somewhere? If you have the knowledge, you're free to look. I've been compiling my own Kernel since the early Slackware days, and albeit I'd never recommend this system to Aunt Daphne and rather have her purchase an Apple iMac instead...Linux is all about freedom. And if you missed this point, maybe Linux isn't for you.
What this world is coming to - is for you and me to decide.
The rot goes deeper than the interface. It goes down to DBus and Systemctl..... NetworkManager????? good fucking grief. I've seen an article suggesting it's a RedHat NSA conscription to control the kernel and make sure that all the major distros and almost any way you run Linux you're going to have their hooks in your system (yes in selinux, and even if you disable it, it's still there; do you *know* there are no back doors?)
Hey I'm not paranoid, ... . they're not out to get me ... but only because I don't think I've got anything worth getting. If I did, I'm sure they would.
A fork of OpenSSL which is stripping out support for VMS, Win16, and other ancient platforms by the *OpenBSD* group is making a bug more likely? It's supposed to make another Heartbleed twice as likely? This guy is completely full of shit. He has no idea what coding is, he just wants to hear himself talk. Give me 8:32 back!
I'm a die hard Linux user, but seriously, it sucks.
X breaks my shit every time I upgrade. I just spent 90 minutes tonight getting my Synaptics touchpad working again. I spent hours 2 years ago making it work. All the focus on compositing is leaving good 2D stuff in the lurch I feel. I do a lot of work remotely, and it is the devil trying to find a display manager that will work over VNC and let you choose your window manager without crashing. And then what do you use, Gnome, Unity, KDE? It's getting to where nothing works without a compositor and 3D.
Sound is a disaster. How many Linux sound systems are there? OSS, ALSA, Jack, ESound, PulseAudio, some I don't even remember. Alsa has been a disaster since it came out, from the perspective of documentation. I don't know how anyone ever wrote the first ALSA applications. They're supposed to be compatible, but they're not. If you play ALSA applications on my PulseAudio system, you get static and distortion. I went through all the fixes, and none of them work on my system. Fortunately the author of my application added PulseAudio as a natively supported output method (in addition to the OSS and ALSA that they already supported). I need to send them a thank you.
Notifications? Behavior I depended on two versions ago has been removed from the current version.
My system tray in XFCE4 is quirky. Some application icons won't appear unless I run the application as root (Hamster and redshift). Maybe that's a quirk of upgrading, but Google tells me I'm not the only one with these problems. And XFCE4 sucks less than other window managers, so it's a behavior I just live with.
That's just what I can think of off the top of my head.
And it sucks.
Started Linux with RedHat in the mid 90's I gave up in disgust when I couldn't create the "partitions" or split up the hard drive as required. I've been doing the same for a while with Mint over many installations, this one time I let Mint select it's placement, as it's never put itself where I've suggest it to.
When Grub was my bootloader the problems really started, of all the things that doesn't have a GUI it's grub; I've complained recently that everything was GUI. Linux is a learning process to many (myself included) nothing to put on-line blind (while a firewall is available it's off and has zero settings, not even examples.
I knew Mint would claim the boot but also expected EasyBCD (NeoSmart Technologies) to fix it, as it's been very good at that.
I've always had a dual boot system, having Linux Mint available would work just fine. Yet working with Grub is no easy task. Some don't even mess with Grub they just select the drive from the BIOS when their computer starts. http://community.linuxmint.com... this one creates two grubs - I don't see it
http://www.howtoforge.com/dual... Just saying many avoid Grub, in one way or the other.
I had to be at the computer when it started to select windows, or have to reboot; playing around with Mint and having to use it are two different things; EasyBCD was of no help...
So I reinstalled Win7; I had been planning to reinstall Win7 as it was showing signs that it was time. It's no big deal (normally) C:\ drive is my Win7 Drives D,E,F,G,H,I,J,K,L (total of three drives) are support, another OS, or storage. I just format C drive, reinstall windows, the drivers and my favorite programs; 2 hours time I can be up and running with my base system.
Now here's where I came across Microsoft messing with those who use Linux; once a MBR has been touched by Linux, Windows won't have anything to do with it, and it's a damn pain.
This time the Win7 install claimed "Setup was unable to create a new system partition or locate an existing system partition" (a new one for me) I was able to continue on, it gave me a 100K boot partition, and Win7 partition, this screwed up my drive arrangement (my drives are named Drive_D, and so on). I formatted the drive again using Hirens boot disk 14 and Win7 install format both. This time I couldn't install Win7 at all, there's even a "FAST PUBLISH" "as-is in response to emerging issues". Support.microsoft.com/kb/2272294 claiming the partition the BOOTMGR is located must be in 4K clusters (NTFS is 4K clusters).
Searching for the problem, the accepted fix is to disconnect all drives except the one to hold Win7. I did that, no big deal as it's how I installed Mint without Grub loading Win7; and it worked, but there were problems. Win7 wasn't acting right, things weren't working as they should if at all.
So I started over, all this time the MBR seemed to be the problem but with Win7 formatting it before the install it should of been taken care of that, as well as my using Dart (Diagnostics and Recovery Toolset) http://www.microsoft.com/en-us... to repair the boot structure; specifically the "Bootrec" command. I had every reason to assumed it had been taken care of.
It was only when I specifically wrote the Win7 header to the MBR did everything start working. This was three days into the fiasco.
Until I learn Grub I'm not going there again, and Grub isn't all the friendly.