Jamie Zawinski Switches to Mac OS X
iskander writes "After a disappointing experience with sound, Jamie Zawinski has finally given up on desktop Linux and switched to Mac OS X. The future of apps like xscreensaver and Gronk is now ``highly ambiguous''. He has already ditched a free/open platform before, but he seems a lot angrier this time. Indeed, twisted by the Dark Side of the Source, young Zawinski has become."
and why should i care what OS he is running ?
maybe i should submit a story about what OS my neighbour runs, or perhaps his brother and wife
Dear Slashdot: please don't post about this. Screw you guys.
D'oh!
Join the Free Software Foundation
Okay, he has a preference. Why is this important?
Desktop developers can finally integrate xscreensaver into the Freedesktop framework without pissing him off?
Trust the Computer. The Computer is your friend.
I hate to be a jerk, I loved all his negitive comments about Netscape/ Mozilla, and whatever else he works on, but it got old like 6 years ago.
The force that blew the Big Bang continues to accelerate.
So someone is switching to OS-X? So what?? And this made the frontpage news? May I ask why? Is it happening so rarely that when one person makes the switch to OS-X it is a front page news?
This seems to me more like a desperate cry for attention in which Zawinski says he is switching platform in the hope that the Linux mob will cry "Don't leave us Jamie!" and he can then return in a blaze of glory. I really appreciate everything that he has done for OSS, and I hope others do too, but I can't condone something like this. Mod me troll you like, but he seems frighteningly cynical.
apterous.org
You got your LiveJournal linked on the front page of Slashdot. Now get your butt upstairs, Mom needs help with the dishes!
.. it DIDN'T go "beep beep beep".
SCO employee? Check out the bounty
I also gave up and went for a Mac for exactly the same reason. It's unacceptable that in 2005 a Linux distribution (FC3, in my case) doesn't recognize a three-button+wheel USB mouse out-of-box or that setting up a TV card requires you to edit some config-files by hand.
The owls are not what they seem
Farewell, O ye of little faith.
Many Bothans died to bring you this sig.
I think it is pretty telling that someone who has a lot of technical expertise has the same problems that a lot of us have had with desktop Linux. The problem is real, folks.
If Linux on the desktop is to survive, I really think there needs to be a major coordinated effort to get lots of things in line. Maybe some type of consortium that would facilitate dialog between different groups and/or state a common direction. It is really hard to build a solid desktop OS when you've got thousands of developers operating independently or in small groups. You might get a few good solid apps, but the OS itself is going to be a patchworked hodge-podge.
1. Short timeout for writing passwords, what may make it difficult for some people to unlock the screen at all.
2. Stupid, delaying messages after entering the wrong password, as if the security delay by the authorization system was not enough.
3. Ugly, ugly, *ugly* logo.
4. Small, non-antialiased fonts in the password dialog, as if the screen space was so scarce when all other windows are hidden anyway.
Dear CNN: please don't report this. Screw you guys.
Patrick Doyle
I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
Also, he doesn't really care what the Linux crowd thinks, which is why he posted the remark about Slashdot.
Sigged!
No, he has NOT been twisted by the dark side, he has just been pissed off for the last time by Linux software which does not do the job.
We have a printer system that was developed for line printers and never matured.
We have a sound system that works most (but not all) of the time if you are lucky.
We have power management issues on laptops which Microsoft fixed in 1995.
And finally
I have a laptop running Red Hat 9 because Fedora 1, Fedora 2, Fedora 3 and SuSE 9.x all have so many major problems with their basic installation that the machine is unusable. My next laptop will be an Apple machine.
Instead of adding more features I for one would be grateful if the Linux software developers fixed existing software. Bug hunting is not sexy but it might avoid more incidents like this.
Ed Almos
Budapest, Hungary
The more corrupt the state, the more numerous the laws. - Tacitus, 56-120 A.D.
Some of the same reasons that I'm switching away from Linux to OSX. Don't have the time to fight those battles anymore. *Don't* want to fight those battles anymore
The posts so for have missed the main point. That is, sound in Linux sucks. It just needs to be fixed.
- arts must die, and it will w/ KDE4
- esd must die
- every program should start using gstreamer
- ALSA must learn to do proper software mixing out of the box.
Imagine my "pleasure" when I inadvertly caused a "beep" to emerge from my terminal window, and as a result had to wait a while (20 seconds? can't remember) before I could start playing a video with sound. Or how I had to do "killall -9 artsd" to start playing video in totem after listening to music on Amarok (which is superior to rhythmbox in most ways).
Save your wrists today - switch to Dvorak
I've had it with these complicated operating systems. I've never gotten my printer to work correctly on Linux, my Mac is just a total pain in the ass and slug, and I spend hours upon hours trying to do the easiest things on Windows.
The hell with all of you. I just installed DOS on my box and all is well.
Slashdot, please don't post this. You guys are jerks and I'm going to tell my mommy about you.
Yeah, I'm as old as my UID would suggest.
Sound under linux requires a card that supports
hardware mixing of multiple audio streams
(SoundBlaster Live or newer is the only one that comes to mind and that I have (1 live, 1 audigy)).
Anything else is mostly unusable because of the lack of kernel (== always works) mixer.
User space mixers are a joke (or at least were last I tried them) because of incompatibility.
I don't know where you got that notion, but it is wrong. Right now, for example, my OS X system is playing music in iTunes, environmental sounds from World of Warcraft, and my terminal can beep, as can my email program when I receive a mail.
These things are very obvious problems, at least to the users. But the developers have convinced themselves that these aren't problems so they just move on to adding new features and forget about these small issues. But its the details that are important to the users. I don't care if gnome supports SVG graphics or whatever, but I do want to be able to get my photos off my digital camera easily. I want to scan in something and print a copy. Why is that so hard?
This is the major flaw with open source software. Most of the developers are volunteering their time so they care about what interests them. Thats fine, no one should tell them what they should be spending their own time doing. But until Open Source "grows up" and starts listening to its users it will never be popular and shouldn't expect to be.
Yeah, this is a great comment. On the one hand, you have Linux advocates and distribution channels shouting that Linux is ready for the desktop and they have installers that do everything for you and it supports X, Y, and Z hardware right out of the box.
However, when someone has a problem, it seems like the solution is always the same: if you spent as much time coding a solution as you did bitching about it, it'd be fixed right now. To me as an end-user, that seems like a cop-out. To me as a programmer, that seems like the coders don't want to be bothered with trivial bugs, but want to code new and exciting, but mostly broken, tidbits of software. Neither are good for the community.
Guess what, the average person is still going to have to call tech support to install their video games. That's just the way it is. There is no way that everyone in the world is going to become an ace at computers. That's why mature video game companies invest in a) better installers and b) tech support. If Linux really cares about the global domination aspect, maybe their community can change its PoV a little about these less technical users that are coming in and HELPFULLY pointing out serious impediments to that goal.
With Linus using a Powermac for his development, you can't help but wonder if he secretly uses OS X now and then ... you know to run Photoshop and stuff. Now that jwz and all the cool kids are making the switch, it could only be a matter of time...
If Linux is going to succeed on in gaining Desktop Market share. You should really listen to the rants of people who tried the platform and then ditched it. So except for calling the ditcher Dumb or a quitter. Look at the complaints. He wanted to get the sound card to work, or 2 sound cards to work and went threw the processes of RTFM and Asking for Help with no avail. So guess what they switched. And on the Mac it just worked. I think a lot of Linux Zealots and/or developers should use Macs for a while to get use to "Just works" and what it really means. I mean if this was 1990 sound cards were considered a speciality item on a PC like adding TV Tuner Card today. But every modern computer has a sound card. And for God sake Linux should support sound. Sound it no longer just for cutisy dings and for games. It is used for practical application such as VoIP and Watching DVD, Sound is now an integral component to the system and Linux should support it and support it well.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
Hunting down articles doesn't require to you learn any programming language. Anyone can hunt down articles, very few people can program. So the two groups aren't coincident.
What "worry"? Linux is very easy to install and run
Now, if your "average user" does not use those features, then Linux is easier than Windows and on par with a Mac.
The "problem" is that most of the HOME user market DOES want those features. But the CORPORATE/GOVERNMENT desktop will NOT focus on those features.
So it all depends upon how you segment the market on whether this is an "issue" or a "critical problem".
Eh, whatever. It's a tool. You use whatever works best in each situation. The key point with Linux is that it CAN be modified to suit your requirements.
The home desktop market will be the LAST market segment that will fall to Linux.
First will be the servers - we're already seeing this happen.
Second will be the corporate/government desktops - this is just beginning.
Last will be the home market - there are just too many limited-run, proprietary hardware pieces out there that work "good enough" right now. In time I believe they will migrate to Linux. But focusing on the LAST segment and claiming that there's a problem when the OTHER segments are starting to migrate is just silly.
How this qualifies as an important piece of news, I don't know. I'm assuming it's a "comedy" piece because he said "Dear Slashdot: please don't post about this. Screw you guys." on one of the linked pages.
However, I myself have had problems with sound in linux, yes, but considering that (as someone who had only ever played about with TCP/IP in Linux and had never touched X or the Linux desktop until a few months ago) I have now switched from Windows to a Linux desktop and got sound working in all apps installed within a few days of switching. That was about four months ago and I still don't use Windows.
I had worked out everything he had worked out in less than two days of having a linux desktop. There are things that should be simpler (cups, sound, etc.) but none of them hindered me for very long and, once properly set up, work much better than my previous OS's incarnations. Yes, it's a pain having to "set things up", but it's hardly worth such a strop.
We all know arts, esd, etc. are a pain in the ass and, yes, we are all waiting for ALSA to "just work". Now that it's in the kernel, we finally have a standardised, working, maintained sound system that supports mixing on EVERY LINUX MACHINE. This should be the turning point.
If a program that plays sound doesn't have an ALSA-compatible option by now, it's not being maintained properly. If it does, it will just work with ALSA and any plugins you might use, e.g. dmix.
As soon as 2.6 distros become the standard, we can work on getting EVERY app to use the same damn sound systems.
I saw his entry on wikipedia and if he's such a great programmer who has made contributions to such important projects as, gosh, XScreensaver, it makes me wonder why the hell he:
a) didn't know this already (not a single XScreensaver that uses sound?).
b) can't work it out for himself.
c) throws a major strop because it's not point-and-click.
It occurs that he's just missed the point. You don't have a Linux desktop to say "I've got a Linux desktop". You don't have one to beat every other desktop into the ground with your technical superiority (real or percieved). You don't have one to complain that it's not like Windows. You don't have one to play iTunes (as he seems to value this as an important feature).
My desktop is Linux because it works, it's fast enough, it does what I want, it doesn't restrict me in any way, it's free, it's Free, it doesn't blue-screen, crash, corrupt and die every few months/years, I can leave it running overnight and not worry about if it'll crash before it finishes it's downloads, I can access it remotely (a good thing when you're working behind restrictive child-safe proxies all the time), and I can do things without wizards, dogs and paperclips jumping up to "help me find a file".
I can't help feeling that any decent programmer would have been able to overcome the same little roadhumps on the way without so much as a sigh. They might even have bothered to fix the troublesome programs themselves.
That's such a typical Linux users response. You say it's better and then when it's shown that it isn't you say "Oh well it's free so it's allowed to not work!" You're like the people who have endless betas so that they can't be given out to for having buggy code.
This guy are sick.
Just about 8 out of 10 user support questions we get on rosegarden are actually sound setup problems. This isn't just a hardware support issue, the "final packaging" step on things like Alsa and JACK just isn't there. Yes, distribs should probably do it, but currently none does. No normal user can configure sound on linux as it is, beyond the basic 'play a .wav file'.
Get SuSE.
Get an SB Live! Value or an SB Audigy! Value.
Get an Nvidia Geforce(1/2/3/4) MX or not video card.
Use an ACX110/111 802.11g wireless card.
Done.
Hardware audio mixing, all the drivers will auto-install. An almost Mac OS X-like experience, and certainly much easier than Windows.
WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
you run fucking *GENTOO*?!?!?!? you bitch about tweaking and you run *GENTOO*?!?!? and a Pentium MMX no less... here's a clue, for your next computer, buy some moderately modern hardware with a halfway decent linux distro.
So instead of purchasing a $10 audio card (which will work on Linux) he gets an iMac.
There is a huge double-standard going on when it's about Linux and MacOSX:
Both Linux and MacOSX will run fine on supported hardware but Linux supports a lot more hardware. How exactly does that make MacOSX better?
Apparently, both the newest Mandrake (Mandriva?), Fedora Core 4, and SuSE 9.3 feature dmix out of the box for soundcards that do not support hardware mixing.
So this is now a non-problem.
Survey says? Stop running Redhat 5. Old linux=PITA. Get a new user-friendly distro.
Oh, you don't want a dumbed-down OS? Than why are you switching to OS X?
Note: I have a powerbook G4, running Tiger, and two mac minis running Tiger. I also have several linux desktops and 2 linux servers. I've got plenty of experience with both platforms.
But SuSE is almost as easy as OS X, and I can run most of my Windows games on SuSE.
WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
I think what he meant by saying that was, "Oh fuck, you're right...you didn't say that. But I can't admit that I was wrong, and was blinded by my Linux fanboy tendencies, so I'll extrapolate as much I can out of your ACTUAL words, and pretend that I was right all along"
You bet your sweet bippy that was a troll. Do your worst, I've got karma to spare.
*NOW* is the time for Linux to get its collective head out of the sand and really reach out to the common users. You know how on a weekly basis we laugh at Microsoft for announcing yet another feature that will NOT be in Longhorn? Let me just put this one in bold:
Longhorn is going to suck. It's going to be the worst Windows since ME.
Microsoft has no plan for it. They know they have really taken Windows about as far as it can go, and any real changes are going to require years of work. But because of market pressures, they can't really take the time that would need - and yet, due to mismanagement, they're going to spend years wastefully. This is the PERFECT opportunity for Linux to finally rise to the forefront -- but only if the geeks get off their high horses and admit that a good OS has to be usable by common man. AND, right along side that, if they can come to understand criticism is NOT necessarily an attack. Reading responses on this thread, all I can think of is O'Reilly screaming 'Shup up! SHUT UP!' at anyone speaking facts he doesn't want to face.
I gave up on Linux for the same reasons as Zawinski. I want an OS that *works*. I don't want to tweak my sound drivers. I don't want to have my nVidia drivers FRICKING VANISH after a week of working right (after a week of work to get them running). I don't want to have to remember that completely ridiculous program names like "the GIMP" are actually usuable graphics applications and not, as the name would suggest to a normal human being, porn videos.
(yes, I know what the name stands for. That does not change the fact that Granny Average User would never in a million years click on something called a "gimp" looking for a way to take the redeye out of her pictures.)
The Linux community needs to get out of the 90s. There are modern solutions to every major problem with the OS, and within a year, two at max, they could make it REALLY user-friendly. The problem is that user-friendliness isn't sexy to Linux geeks. No one wants to spend time writing a new sound library that actually works when they can just look down their noses at anyone who doesn't know how to properly configure ALSA. And the only thing less sexy than THAT is not writing any actual code at all, but just going through the OS and making sure the user dialogues make some sort of sense to those who don't have PhDs and, as someone else mentioned, will actually fit on a screen resolution of less than 1024x768.
But you know what? Someone has to do it. Because if no one does, Linux will NEVER get past being a hobbyist OS, and whatever horrible things the next Windows introduces to the computing world, we'll be stuck with dealing with them. ('Cause god knows, I just *love* having mailboxes on Linux and Mac machines shut down because Windows-borne virii have filled them with spam. That helps my sense of superiority to no end.)
So this is truly put up and shut up time. There has never been a better opportunity for Linux to really make some inroads in the home market - but only if the contributors are willing to make some compromises and give the other 90% of users some reason to switch. So all I ask is, if you contribute to OSS, and you EVER spend any time online complaining about how Linux could be great if only it could get into the mainstream - use that time to tweak Linux's usability instead. Fixing bad error messages doesn't even require much programming skill at all. Make Linux usable for common people, and it can succeed. Period.
Bush: He's Liberal in all the wrong ways.
- I never have to upgrade from one version to another. I'm always up to date! This is completely different from every other operating system out there. Whether it's Windows upgrading from XP to Longhorn, MacOS upgrading from 10.3 to 10.4, or Fedora upgrading from FC3 to FC4, most every OS out there requires a major upgrade every now and then. Gentoo does not.
- You have complete control over your programs. Don't like how a specific program works? Well, you can easily change the source and compile required libraries. Dependencies and required versions of libraries can be a nightmare in some distributions.
- Generally, everything just works. In my experience, I agree that it has absolutely been a chore to get some things working in Linux. Most of the time I don't mind it, but with Gentoo Linux I have definitely had to meddle with the system LESS than ever before. I have less programs crashing, even when I'm running all of the latest stuff.
I don't think I would have ever switched away from Linux, but Gentoo has certainly given Linux a new light that many Linux users just have not seen yet.... and it never will be.
One small correction:
GNOME *does* have the navagational paradigm, which is readily available within Nautilus menus. Navagational Nautilus is simply not the default mode.
While the spatial Nautilus decision was certainly controversial, it hardly seems worth the continuing flamewars over it.
~~~~~~~~~
dissertus scribendo latine videri volo.
"Jamie's mom is way cool!"
You mean, like, "has got it going on"?
It's 10 PM. Do you know if you're un-American?
I can relate to Zawinski's frustration and many others do as well. I notice that it seems to effect those with more experience than those newer to computing.
When one first acquires a new tool, whether it is hardware, software or a woodworking plane, the very act of learning how use the tool itself works is highly engaging. Just futzing about figuring out how the new tool works is an end in itself.
However, after one has spent 20+ years learning the ends and out of each season's new tools the joy fades. One becomes progressively less interested in the tools itself and more interested in product you want to use the tool to make. The time spent futzing with the tool is not engaging but frustrating and wasteful. You want to get the primary work done not spend all your time adjusting your tools.
How many times over the years has Zawinski wrestled with a problem similar to his Linux sound issue? The thrill of solving such a problem is long gone, baby.
The Linux community is dominated by people who enjoy the process of learning and using the tool itself. They are the kind of people who take the toaster apart to see how it works. The vast majority of desktop users, however, just want to make toast.
People like Zawinski, who have taken apart their fair share of toasters, also now just want to make toast. At present, Linux doesn't let him do that.
... do you remember where you were when you first heard the news?
They'll nod solemnly, and in reverent tones, tell with precise detail where they were when they learned that Jamie Zawinski had switched to OS X.
However, I do belive you may have the same problems with MacOS X -- you can't play two sounds at once.
Where in the world did you get that idea? Have you even used a mac since OSX came out? Since OS 8 came out? You do realize the Macs are the darlings of the media production industry, right? I mean honestly....
Honestly...
Network Audio System (NAS) was around for a while before these other audio projects sprung up. Just as every Linux distribution uses the fully standard X windows as a networked video server, every Linux distribution should have used, from the outset, the existing fully networked audio server, NAS.
How all these Linux distros and desktops got themselves into so many fragmented half baked audio schemes is beyond me.
Earth to Jamie - Linux is NOT FINISHED
Neither is OS X or Windows. MacOS 9 is, and nobody's using it. OSsen are moving targets.
That said, "IT'S NOT FINSIHED!!!!" is no excuse, and the FOSS community's inability to take completely valid criticism and do something about it is one of the reasons it isn't "finished".
Apple is certainly /a/ Dark Side. I recently bought a Mac Mini to reaquaint myself with what Apple has to offer. I knew at the time that at the end of the day Apple's number one commitment is to it's shareholders, but blimey the OS X/iLife experience is just so commercial.
.Mac. Your USB webcam doesn't work? Why not buy an iSight?
It's as if you can't open a menu without a "BUY ITUNES MUSIC" or "BUY GARAGEBAND ACCESSORIES" options being thrust in your face. You can't move for invitations to pay stump up more cash for
After years as primarily a Linux user, it's quite a shock to the system moving into an environment where I'm constantly being reminded of my status as a consumer.
And is throwing his toys out of the pram because he's just not getting everything his way. Don't worry nothing is ever perfect for these guys, OS X won't be able to satisfy his demand that the world be made perfect for him either.
Guess what all you Prima Donnas, (and yes there are a *lot* of Prima Donnas out there). You will never ever get everything you want, something will always be wrong because the problem is not with the world at large, it's with your personality.
HTH
Deleted
There are tons of solutions to the problem, but they all miss the boat because they're done at the wrong level, and hence they're not transparent. The last thing we need are more sound demons. (I use NAS and it works fine, but it's the wrong solution too.)
All sound drivers without exception should work like they do currently on FIRST OPEN, but on second and subsequent opens they should automatically hook in a mixer and mix all inputs together.
The code to do it already exists, but it's just not being structured sensibly as above. It's no surprise that newbies find the one-at-a-time behaviour unhelpful, because it is. This is a multi-user O/S fer crissakes, single-open in sound drivers is just dumb!
"The question of whether machines can think is no more interesting than [] whether submarines can swim" - Dijkstra
You, ah, might want to retake some critical reading courses or something. His post as a whole didn't say anything like you argue against. Even the quote you pulled to back up your argument doesn't.
He does correctly point out that the elitist bullshit is exactly that, but he doesn't say that there is only ONE TRUE OS.
Maybe his comments just hit too close to home?
He's right.
We should be able to plug a mouse into a port on a Linux machine and expect it to work. We shouldn't need to troll the net looking for guidance on how to configure the damn thing. If it needs a driver and it needs to be configured, we deserve a GUI that handles the congifuring. A mouse is a tool that's used to manipulate a GUI; it's lame and lazy to build a driver and then slump off the configuration into an X ASCII config file.
Ditto sound. Linux doesn't do it right. And, what's with that stupid business of distributions shipping muted ALSA drivers? That makes no sense at all. Can anyone even imgaine Microsoft or Apple doing something so gratuitously user hostile as shipping boxes with the sound turned off by default?
-- Slashdot: When Public Access TV Says "No"
You couldn't be more wrong about OS X.
As a Mac user, the idea of a computer being unable to play an essentially unlimited number of simultaneous sounds is just foreign to me. I don't even think about it. I expect that I can leave iTunes playing music while playing a game that makes all sorts of noises and still hear alerts from iChat when I get an IM. There's nothing to configure, it just plain works.
The only time I've been amazed by sound on OS X was when I first played with Soundtrack. This program lets you create professional-quality music by mixing up to 99 tracks of layered audio. Not only does it mix them in realtime, but it can apply advanced audio effects in realtime as well.
Not once in the process do you have to care about audio hardware setup. Whatever you have plugged in -- analog speakers, USB speakers, S/PDIF -- the appropriate audio comes out of it.
Meanwhile, you need to spend an afternoon to get open-source UNIX to reliably make a sine-wave beep.
Perhaps you might want to review Apple's overview of OS X 10.4's Core Audio functionality?
Seems to be that JWZ's gripe is that Linux requires an one to have at least some skill as a *System Administrator* to well, *administer* a machine. Mice features aren't plug and play (I am assuming he refers to the fact that a scroll mouse still needs to be configured before the scroll wheel must be used -- USB mice *are* essentially plug and play with most all recent versions of Xorg), is that really a bad thing on a *UNIX* machine? Of course you are supposed to configure your system software (and X11 certain counts as such), not the system for you -- on a professionally oriented OS like Linux or BSD?
:-)
It is precisely this desire to accomodate a user who is wants to a) admin a full featured UNIX machine b) not have any system administration skill that is has ruined most *all* Linux distributions (note: all Gentoo fanboys replying to this will be deported to Siberia) -- and which is why I use FreeBSD wherever I can (the only reason I wouldn't use FreeBSD is a specific application or hardware support -- such as on amd64 machines, at least for now).
There's also nothing wrong with OS X and before that Irix -- which JWZ *does* seem to be fond off -- for gearing themselves to developers/designers rather than system administrators, that should be encourage -- and users who wish to use a Linux machine *without* being willing to read documentation should be more than encouraged to switch. OS X is an excellent system for that user -- they still have the power of a UNIX shell, etc...
Yet, people will remember how insecure IRIX is out of the box (and to all the IRIX bashers -- it *can* be made secure) -- and especially how expensive and hard to obtain the OS is! -- those are all prices you pay for being able to plug and play *AND* have a "cool" UNIX shell.
So essentially, to JWZ and the rest of the crowd -- the same people for whom garbage like GNOME/KDE/linuxconf was created -- don't let the door kick you on the way out.
[On a side note, what esd (enlightenment sound daemon -- which is still used by GNOME junk afaik) has been doing what jwz was trying to do since *at least* 1999; It amazes me how such talented developers can't do even the simplest administration tasks, I've worked with people holding M.S. and Ph.D degrees in computer science (or math or EE, but you get the idea), who couldn't use vi and used *TELNET OVER WIFI*; I also know *many* graduates of the famed Berkeley EECS program, some of them now in graduate schools, who can't manage to write a makefile or extract a tar file]
This is only a semi-"arrogant UNIXoid rant" -- I don't see anything wrong with OS X (or IRIX), it's just that users *shouldn't* demand mainstream Linux distributions (and BSD flavors) act like it.I also find it entirely acceptable for people to be developers and *not* be system administrators -- indeed, this is how I get jobs
Two years? How about tomorrow, when FC4 is released with dmix correctly setup out-of-the-box?
And sound mixing has worked for me since 2003. I setup Alsa and sound mixing Just Worked(tm), no messing with dmix or whatever.
I don't know that moving the people on the 253 browser projects over to ALSA and telling them to "make sound work" would solve the sound problem
It might, but that's not what I was pointing out. I was pointing out that part of the reason that Linux on the desktop is still sucking in many different ways is that people don't consider it interesting to go off and fix the suckiness, they instead go and start another browser project, or MySQL web interface, or whatever. This is both the strength of open source software, and it's weakness. It's like living in a town where everyone's jobs focused on what they wanted to do instead of what needs doing. Who'd pick up the garbage? Who'd dig the ditches and lay pipe in the rain? Who'd really be a plumber (literally working in other people's excrement) if there wasn't that large hourly rate? Same thing with open source. This is where M$ and others whom you pay money to do have an advantage becuase they can point to the crapwork that needs doing and tell someone working there to fix it or find another job. So it gets fixed.
Thinking of the authors of software as interchangeable is unrealistic
I never said that, or for that matter suggested that they switch projects. I just pointed it out as a glaring weakness in the OSS model. You said it yourself: People work on the projects that interest them.
Even despite those limitations, I would have switched to Linux on My main machine -no, make that ANY machine long ago if just two things were functional; a firewall that works like ATGuard or Outpost (NO Connection Unless Specifically Allowed Previously Or Just This Once)... and a decent CAD program. It just kills Me when I hear the stadard cry of "Linux has ports of all the Major Apps!" How about AutoCAD? Or ANYTHING even remotely close. I mean, bloody hell, My preferred low-end/low-resource app is a Visual Basic construct. How difficult could it be to port an older version to Linux?
And please, no comments from the 'What A L00ser, Just Type In (insert insanely long string of utter gobbledygook here) To Config The Firewall'. I was a DOS proponent for many years before I was forced to switch to 'Doze (Linux not being that common in the Corporate environment then). NOBODY wants to type in long combinations of letters, numbers, and switches to do something.
People switched to 'Doze from DOs (or Unix) because it was much easier. I have heard for years how Linux was Ready To Replace Windows. Wake up, people. If you can not even get 'Nix to perform the most basic of functions that 'Doze does automatically (Sound Configuration for one), then Linux/BSD will continue to be relagated to exist as a mere fraction of the marketplace.
When you've been using UNIX for 20 years, start a family, and actually find other hobbies than sitting in front of the ol' cancer machine, you'll get sick of stuff like:
- learn yet another new config format
- having to constantly recompile a kernel or a kmod
- compile anything
Just to get a camera hooked to your PC or try out some new piece of software.
It just gets really fucking old, eventually.
This is why I see OS X as a bigger threat to Linux than Windows. A lot of Windows users actually LIKE Windows; the way its laid out, the interface design, etc. They usually don't like OS X's interface.
Its a good thing he didn't try to copy and paste any meaningful information between apps (or even on the same app) on Linux - then he'd be really pissed.
Multimedia installation: Install these applications in this order, using an automated installer such as yum, apt-get (preferably with synaptic GUI), or the urpmi mandrake installer: mplayer + components.
USE AN AUTOMATED INSTALLER, DON'T INSTALL FROM RPMS UNLESS YOU ENJOY DEPENDENCY HELL.
- mplayer
- mplayer-plugin
- skins
- w32codecs
- xine
- xine-lib-devel
- realplayer
- flash
Start playing things back and enjoy. For Fedora Core 2, follow the procedure in my article Painless Multimedia For Linux, but use the yum.conf file posted in Build a Linux Appliance, Part 2--The Extras, not the one that's posted as part of the multimedia article. (the multimedia article should be updated to refer people to the "appliance article" URL, I need to contact the editor about this)Tech Public Policy stuff
You can find all my Linux how-to pieces here. They're more or less FC2 specific, but the procedures I should describe should work on just about anything, with minor distro-specific mods (like apt-get instead of yum, for instance)
Tech Public Policy stuff
I was talking about people ragging on Jamie Zawinski for his decision to switch to the mac.
Does this decision all of a sudden make his past contributions less valuable? Ingrates, the lot of you.
Jesus was a compassionate social conservative who called individuals to sin no more.
Nice "pretty" screensavers are nice and all, but it serves little to no purpose, unless you normally sit at your computer and stare at a blank monitor. I think 99% of the time, the screensaver activates because the user walked away from their computer temporarly, or is occupied with something else. So why is important what screensaver you use, since you won't be there to look at it anyway?
Now if people made screensavers that displays useful information, not just graphics, thats a different story. Say on a webserver box, you have a screensaver that shows the server load and various other statistics, that would be cool.
At first there was silence.
Then a company called 4Front came along. They wanted to create a common sound API standard for all those UNIX systems that lacked sound support, like Linux, BSD, etc. Hence OSS (Open Sound System) was born. A simple API to cover a simple need: get sound. Cool.
But then they decided to charge people for their drivers. Now who hell would pay for a fucking sound driver? Hence the OSS/Free project was born. Its mission: create free OSS-compatible drivers.
But most OSS/Free drivers sucked. Buggy, lacked basic features, etc. And they still suck as of now. But since sound manufacturers often don't reveal specs, you can't really blame the OSS/Free guys for this.
Also, OSS was nice and all, but lacked advanced audio features needed for pro work, and >2 speaker support requires having multiple sound device nodes, which is an ugly hack. Also, some people didn't like its ioctl() interface, saying a library would be superior. Hence the ALSA project was born. Its mission: create a modern sound API for Linux (yes, only Linux), along with free drivers that don't suck.
But ALSA has many problems. First, its library-based API broke binary and source compatibility many times. Second, it has a powerful infrastructure, capable of doing pro work stuff such as routing sound from a card to another, or use plugins, however ALSA can only be configured to do those things through confusing plaintext config files that are barely documented, and hard to understand. Thirdly, it's a bitch to have working. ALSA is very modularized, which is normally a good thing, however it tends to make it break up more than the plain one module way of OSS.
Oh, and let's not forget that since OSS is an established standard, ALSA needs backwards OSS compatibility. Hence the ALSA people made OSS emulation standard in ALSA. Which brings up the same chicken and egg problem we have seen with OS/2 and its Win 3.1 support: since ALSA has OSS API support, why should we care about the native ALSA API? So, even today, many apps have not taken the plunge to ALSA because OSS "just works". Well, most of the times at least. OSS emulation is not perfect (gasp!).
Oh, another thing: since the ALSA libs are LGPL and have broken backwards compat quite often, closed-source projects tend to forget about bothering to support ALSA, prefering the simple ioctl() API of OSS.
And of course most ALSA drivers are very buggy, for the same reason as the free OSS ones. Which brought up some interesting situations: sometimes when an application supports both the OSS and ALSA APIs, some ALSA drivers actually work better with the OSS API!! Another blow to the native ALSA API.
But one of the biggest problems of ALSA is that its devs refuse to believe that having more than one app playing sound at the same is a major problem, which continues to piss off lots of people to this day. Indeed, very few sound cards can actually play more than one stream directly in hardware, so the mixing must be done in software, preferably at the driver level so that the operation is transparent and (this is very important) latency-less. Windows has done this for a long time now. The ALSA people came up with "dmix", a userspace plugin that does the transparent mixing we needed so much. However, being a userspace plugin, it needs to be configured, so again the ugly ALSA config files are to be used. After being configured, dmix works quite nice, HOWEVER for some reason some apps just crap out when using dmix. Apparently dmix is not transparent enough. It's clear now that software mixing must be done at a lower level, however no work is done on that front. Arguments against it say "this shouldn't be in kernelspace, bla bla". which is funny, because the commercial OSS drivers do support hardware mixing inside their kernel drivers. And it always work fine.
For a long time people have tried to solve the more-than-one-app problem through things called sound servers. The idea is simple enough: have one program open the sound
Everyone is saying "he must not be that smart/great" if he can't get a sound card working in Linux.. My take on it is "maybe he is to busy working on useful things to waste his time getting a sound card working in linux". As someone who gets shit done at home and work, I find that you have to focus on the problem and work on it rather than being distracted by everything around you. Spending 6 hours getting proper audio support in linux is 6 hours lost that could have been spent working on your project. Today it's 6 hours on the soundcard tomorrow its three weeks figuring out why the throughput in your application is 1/10th of what it should be (my current problem) because some idiot linux kernel 'hacker' broke part of the disk subsystem in the last 10 revisions of the kernel.
A few years ago I decided to switch my desktop back to windows 2k and exceed, and I'm significantly more productive than I ever was running linux, and wasting 3 hours trying to figure out how to remap my goto-line key in the most recent version of emacs, after the developers decided to use the key for something else.
This stuff should be part of everybody's default distro installation, and that would solve the problem. However, nobody's stepping forward to buy the licenses.
Another way to do this is put together an automatic download/install package that could be run via point-and-click, say a script telling an automated installer, and that's probably the best answer for the free distros.
The difficult part is finding out what has to be installed, and that literally took me weeks of research. (about 3,IIRC) I did this for publication so the rest of us wouldn't have to.
The tedious part is simply installing a bunch of packages. But... by and large, it's on the order of:
yum install mplayer - y at the prompt
(lather, rinse, repeat until you get to a package that actually has to be manually installed
Probably an hour or two if you've got broadband, and one or two of the packages takes a long time at somewhere around 90% CPU load to fix the dependencies, so go out for coffee when that happens.
Tech Public Policy stuff