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)
Whoever wrote this summary should be kicked in the balls, hard, at least three times.
Every distro except the one I use does suck.
And every other window manager, and every other package manager, and every other...
I don't like this growing trend where people insist on creating everything as video, even things where the video doesn't actually serve any purpose other than showing a talking head. Information is so much easier to consume when you can consume it at your own pace, depending on your own speed of reading with no distracting heads and not being limited by the speed at which the video happens to progress. Text also happens to let you quickly jump over things you already are familiar with or jump back and forth between interesting passages.
I want less videos. I want more text.
Because canes are for lames.
Support my political activism on Patreon.
So long as other operating systems suck worse. Kind of like "democracy is not really a good form of government, but all the others suck worse".
I have no idea who inisited on it and when it became cool to have to watch a slow ass instructional video when a small write up and 10 photos will do the job 10x faster and I can scroll up and down the page or print it when I need a reference. Its so painfull just see how many vdeo tutorials where are for say Drupal.
by TheSpoom (715771) Uncaring Linux user here. I have nothing to add to this but please continue. *munches popcorn*
TFS is complete bullshit. There won't be Linux in 2039 because everyone knows time resets to Jan 1, 1970 in 2038.
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.
It got a little noisy, someone said "Sssshhh" and everyone shouted out their passwords.
Click on "Hide/Show Transcript" under the video...
This is not the sig you're looking for.
What that be the "Hide/Show Transcript" link directly below the video?
systemd is Roko's Basilisk.
...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.
this was very funny diatribe (and I have mod points). I have mod points ! no, really, I do !
Linux has many positives, there is no doubt. However, there are many problems with the system. The lack of applications leads to situations where a user is told is a great OS, but there is nothing on the OS that does what they want to do. Its great to have a kernel that works well but whats the point if you cant do what you need on it because of the lack of applications. Wine has been around for 20 years yet still has yet to develop an emulation layer that can run 99% of Windows applications reliably. It constantly breaks support for older applications carelessly. The changelogs seem to be filled with obscure performance hacks that lead to a .01% improvement in performance but it appears little is happening in major progress on supporting all of the Windows API.
The bigger problem is lack of hardware support, to the point that the application issue may just be a result of the problem with it being so difficult to get new, novel, or unusual hardware to work on Linux. The fact is, hardware makers will always provide better working drivers in a timely manner than backwards engineering. Its a pipe dream to think that many hardware makers will open source the drivers. By the time open source drivers come around, the hardware is often so old its not even being sold any more or is out of date. Some hardware has no drivers available.
This problem stems from the attitude of the Linux kernel developers. Many of the Linux community have an absolute aversion to actually working with hardware manufacturers to get hardware support implemented, especially with Dell. With Microsoft repetedly throwing Dell and other manufacturers under the bus, there was an opportunity to reach out to Dell to look at Linux as an alternative. This option has been thrown away by Linux. Linux could have gotten much wider adoption by accepting the users using small amount of binary code, which wouldnt even be required to be used as open source drivers would still be developed. Part of the problem as well is the badly documented or not documented at all kernel driver interfaces. It is actually almost impossible to find any comprehensive reference on kernel internals and the driver interfaces. Driver interfaces which seem to change with each kernel version as well, blowing up hardware support for users in the process. Backward compatability is critical throughout the system. Users need to be able to be assured they can use applications and driver accross kernel versions. I have suggested before a driver compatability layer for binary drivers so they will work between kernel versions.
Another problem is the bone headedness of Canonical and Gnome who have copied every disasterous mistake and disaster of Windows 8 in creating user interfaces that are incomprehensible. The fact is, for users, an interface that is well known and practical rather than some hair brained scheme concocted by some crackhead who thinks they know better than everyone else and wants to ram their self righteous idea of user interface design on users, as with Ubuntu Unity and Gnome 3. Just stick with the tried and true taskbar start menu paradigm, please. These people are actually worse than the kernel developers because they think that they are genuises with user interface design but are self absorbed, obsessed and arrogant with trying their insane user interface experiments without any sense of practicality or really caring about users at all. The user interfaces they create are vastly worse than what the kernel developers would come up with.
I've watched two of these stupid talking head videos. Why is it that I've wanted to punch both of the subjects in the face?
One thing I think he misses pointing out is the good ol' saying: The right tool for the job.
Which is probably a huge reason there's so much forking and so many different distros for Linux and all the open source software that follows it, and for that matter the reason there's more than one OS.
We want to use the right tool for the job.
I do like the general premise 'Linux Sucks', because I think it's good that Linux as a collective, a community, can look at their creation and say, "Well, it still sucks." And carries on to keep making it better every day.
For anyone who wants to explore this specific topic further, this is a really good video talking about the problems with X from former X developer and current Wayland developer David Stone.
http://www.youtube.com/watch?v=RIctzAQOe44
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!
Any halfwit can post their monologue to youtube. Spare me the lecture, and save me some time - post a damned transcript. If you are too cool to post your actual slides, just post the transcript of what you said.
Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
back in the days of Win 98 it was loads more stable, faster, and it used all my hardware.
With XP, Microsoft got it mostly right and with 7 SP 1 they fixed it. Yeah, Vista and 8 suck, but you don't have to run those. So until Win 7 drops support I can't think of anything practical I _get_ with Linux besides a kick ass shell. I do like Bash though. But I'll run some Linux in a VM for that.
Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
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.