This is the money quote: > The second dimension to the problem is that no two Linux distributions agreed on which core components the system should use. Linux on the desktop suffered from a lack of coherent, strategic vision, consistency and philosophy . Every engineer I know likes to do things a particular way. They also have a distorted view on the level of customization that people want and need. I like OSX. Out o…
What killed the Linux desktop
291–300 of 385 posts
Re: What killed the Linux desktop
#292The first attempts were Mandrake and Conectiva. Canonical has been doing a good job lately, the problem is that the platform is now beyond hope on the desktop, it simply doesn't gather traction from 3rd party developers - the most important thing for a desktop OS. You're pretty much limited to the FOSS utilities that exist on the repositories.
Re: What killed the Linux desktop
#293Earlier quoted context omitted.
What are you using for sound? I use Pulseaudio on my desktop (custom built with a M-Audio Delta 2496 Pro soundcard) and on my laptop (crappy Lenovo G575) and I don't have any problems at all. All I do is have this line in my .xinitrc: [[ -x /usr/bin/start-pulseaudio-x11 ]] && start-pulseaudio-x11 & And it works perfectly! If I want to change my volume or manage which device it outputs on, I just run pavucontrol
What distro are you using that you are having to start pulseaudio manually? I swear I thought it was default everywhere.
Re: What killed the Linux desktop
#294Earlier quoted context omitted.
To stress out again; OS/X has the poorest hardware support for 3rd parties; even compared to Linux. Just "think different" and buy some hardware and you ll see what I mean..
Oh well now that you said it the argument is settled. You can't just say OS X has the poorest hardware support ever and not back it up with anything except "go buy some hardware and see what works and what doesn't". Is there maybe a table online that lists these incompatibilities you can link to? Please don't say "do some research" because the onus is on you to prove yourrself right, not on me to prove you right. You…
Don't read too far into things, and "...loyalty to facts" eye roll.
Anyway, It's pretty common knowledge to Linux users that hardware/driver support on Linux can be a challenge. Sometimes things work right out of the box, other times you have to do a lot of work and a lot of Googling.
That being said, I don't agree with the parent. For basic hardware needs, Windows and OSX have a fairly high success rate of plug-and-play functionality. For me on Linux, it's about 50/50.
Re: What killed the Linux desktop
#295Earlier quoted context omitted.
Among non-ultra-geeky Linux users I know (mostly part-time users), "Linux" does seem to be reasonably standardized as far as desktop components go, because by "Linux" they mean "Ubuntu". It's possible the Ubuntu desktop dominance came a bit too late, though, and still isn't entirely complete. My own experiences aren't great with Windows, though they're smoother on OSX than Linux. The problem I have with Windows is th…
Windows is horrible to use, everything is poorly designed. Linux (Ubuntu in my case) and OSX just work sanely mostly, but OSX is a horrible dev environment, so I moved back to Linux.
But if you are Apple pet developer then you'd just use XCode/XCode projects/etc for all your needs. And would be very happy with that.
Re: What killed the Linux desktop
#296This is the money quote: > The second dimension to the problem is that no two Linux distributions agreed on which core components the system should use. Linux on the desktop suffered from a lack of coherent, strategic vision, consistency and philosophy . Every engineer I know likes to do things a particular way. They also have a distorted view on the level of customization that people want and need. I like OSX. Out o…
If that was the only problem though we would have expected FreeBSD to overtake the desktop. the larger issue, unfortunately is just that people are afraid to switch from Windows to anything other than Mac. Android is helping there, but it will take time. Never underestimate the fear of the consumer that they will break stuff on a computer they are unfamiliar with. The fact that Windows is actually getting better may…
Re: What killed the Linux desktop
#297What killed it is that it didn't have a huge and multi-billion dollar company betting on it (on the desktop) like Microsoft and Apple had, even Apple with its billions is still around 5% market share worldwide so having 1% is still a great accomplishment when you think that it had no support from huge corporations. Now take the mobile world for example, Linux on mobile had been around for a decade but it never really…
Redhat and Canonical are big companies that did bet the house on Linux. A few years back I was confident Canonical was what desktop Linux needed to get its shit together. And today I'm typing this on a Zareason laptop that's supposed to provide 1st class support for Ubuntu (even has an Ubuntu key), and the mic doesn't work, Fn keys don't work, youtube videos appear in monochrome blue, and it likes to boot itself up r…
Re: What killed the Linux desktop
#298Earlier quoted context omitted.
Coming from the perspective of a developer: I used linux as my only OS sans VMs from roughly 2008 till 2011. I finally gave up because it handled monitor switching, multiple monitors so poorly (using Nvidia GPU). I begrudgingly switched to windows because I owned the hardware already, and it was the only option. Windows sucks, the lack of a usable shell kills it, full stop, nothing else windows does matters. And no,…
As for the "lack of a usable shell" part, have you looked at Powershell? It comes bundled with Windows, and has a lot of the features that are missing from the command prompt. It does have some rough edges that may cause you to dismiss it as unusable, but it offers tab completion, colored text output, and a real scripting environment (not DOS batch scripting). Every serious Windows developer I've talked to nowadays u…
No, and I have zero reason to do so. I don't deploy on windows, I have no reason to ever deploy on windows, so why would I bother learning another syntax just to develop on windows? It really doesn't make any sense. Powershell only makes sense for IT admins whom have to manage windows networks, it makes no sense at all for developers deploying on *nix.
Re: What killed the Linux desktop
#299Earlier quoted context omitted.
To stress out again; OS/X has the poorest hardware support for 3rd parties; even compared to Linux. Just "think different" and buy some hardware and you ll see what I mean..
The real difference is that on OSX is if something doesn't work it doesn't work. Under Linux it may work, or work badly, or you can probably hack it to make it work well. I used to think I liked the latter but there's something appealing about the binary clarity of OSX.
Anyway, this has been almost 100% true up from 10.3 through 10.6.x. Recent developments both on Apple's as well as on MS's side have closed the gap between the two systems quite a bit. I still prefer OSX but it's gotten close. The real reason I continue to buy macs nowadays is the hardware quality.