No, but don't try to veil this as some sort of win for the ideals of FOSS when it's not. It's a political play and nothing more.
Most probably wouldn't care less about "ideals" winning - in practice, Open Source has already won.
What remains is Linux to start raking in desktop wins. And activity like this definitely helps more than some abstract victories about ideals.
I was thinking of sitting there beside the computer, quietly cherishing the Freedom it contains.
Whoa! I can't express how excited I am about this, it's going to change the way I "experience" my computer. It will happen on a much more intimate level from now on, knowing that there are no proprietary firmware blobs inside.
Whoosh
Ah hell. I made the mistake of taking that poster seriously. Reading it again it's obvious satire. Whoosh for me.
I caught the satire right when he said he uses iPad to impress *girls*. A Freudian slip.
Why use IronRuby when you have IronPython? Because it is Ruby. Duh!
Ok, better phrase it like - why *support* IronRuby when IronPython is pretty much the same thing, just more mature and popular.
Also one good question is - why bother with IronRuby when they already have IronPython?
Rails isn't *that* important or special anymore.
Windows Users don't have multiple workspaces, or window transparency (at least I haven't encountered it in Windows 7), or a package manager.
Which of these is relevant to audio?
I've been using KDE since 4.2 with PA, often using the ability to output to another PA instance on the network, reliably, on Gentoo and Ubuntu, mainly using Amarok. You are trolling hard and fast.
Nice that it worked for you.
With freshly installed Ubuntu, I could hear sound from Gnome, but not KDE. Well, KDE 4.4 works ok.
Clearly it was not the fault of KDE - perhaps I should have called a computer repairman?
I can't tell whether you're implying that KDE developers getting to use a unified audio API across different operating systems complicates the user experience in some way, or that you are somebody who pointedly doesn't care how things work internally, in which case I'm not sure why you bothered replying.
Phonon in KDE *is* a user-visible entity. You have to priorize different backends, etc. You can also enjoy nice error messages about Phonon backends not working when running KDE programs inside Gnome.
Compile-time? Why? Phonon is designed so that *all* backends that work with your OS can be provided and users can change backends in run-time without any applications having to handle anything, or even needing to be aware that anything has changed. Why should it be "unreasonable" for a user to select backends?
How often do windows/mac users change their audio backend?
Sorry about redundant posts. Slashdot web backend seemed to be failing badly.
To be fair, I did have to do this once. Kubuntu shipped with one that was broken by default, at least on my system.
Me too, that's why I'm complaining. On Gnome & Ubuntu, you don't need to think of backends - it's pulseaudio or bust.
To be fair, I did have to do this once. Kubuntu shipped with one that was broken by default, at least on my system.
Me too. That's why I'm complaining! In Gnome world I haven't needed to think about backends for a long, long time.
"Protozoa are small, and bacteria are small, but viruses are smaller than the both put together."
