I'm the CEO of Tailrank. This is my old (personal) blog. See my new blog over at Feedblog.org. Tailrank is proudly hosted by ServerBeach.

My Photo


June 2008

Sun Mon Tue Wed Thu Fri Sat
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30          

« Bubble tea... | Main | Exercise and Aging.. the good fight. »

"The future direction of xscreensaver has become... highly ambiguous"

Looks like JWZ has migrated to OSX:

Remember last week, when I tried to buy exactly the same audio card that 99.99% of the world owns and convince Linux to be able to play two sounds at once? Yeah, turns out, that was the last straw. I bought an iMac, and now I play my music with iTunes.

Linux is just honestly a pathetic desktop OS.

Every developer that has ignored end user demands are responsible for this pathetic situation.

Every XFree86 developer and KDE developer that hasn't compromised to fix the dual clipboard issue.

Every kernel developer who has contributed to ALSA, Open Source, etc debate and the continued fragmentation of sound support.

Every developer who started their own window manager. Every developer who wrote their own sound server.

You're all to blame. The usability of Linux is pathetic. I'm an expert and when I can't get work done because its just too difficult to figure out how to setup my wireless card - I'll just punt.

Up until now Linux has had a monopoly within the frustrated Windows user market because there was no other choice. We put up with the horrible usability of Linux because the only alternative was Windows. Now we have OS X.

The next generation of hackers are growing to expect OS X functionality. They have their UNIX and all is well in the world.

Expect to loose market share unless this is fixed. Personally I doubt it will happen. Twenty years of unix history seems to back me up here.

I would love to be proven wrong though.


TrackBack URL for this entry:

Listed below are links to weblogs that reference "The future direction of xscreensaver has become... highly ambiguous":


The comments to this entry are closed.