Where's the protein we need in all that grain? And don't bother mentioning soya - that's what much of the South American rainforest is being razed to grow, and it's a very inefficient source of protein.
Depends on where in the world you are - in parts of Europe horse meat is readily available. It's a little bit like venison, and less fatty than beef steak.
It's [PA] structured the same way the audio systems on Windows and OS X are.
Like hell it is, and I say that as someone who has programmed audio and MIDI apps for OS X, Linux and NetBSD.
There should be no such distinction. Any "lower level" API should be an implementation detail of the application-level audio system, just as the PCI configuration space is an implementation detail as far as X clients are concerned. As for the traditional distinction between the audio deamon interface and the "lower level" one: it's an accident of history that we lived with that split so long. PA is a better world.
Last time I checked, PCI configuration was not time critical. As for the "accident of history", fact is you've got too much functionality in userspace.
As for POSIX real time scheduling? Just because the API exists doesn't mean it's implemented or configured on any of the major distributions, as it requires patches to the regular Linux kernel that would be detrimental to most peoples requirements. And my comment on switching users is no more anecdotal than Poettering's unsupported assertion that PA does what most users want.
I believe the solution to any *PROFESSIONAL* Linux Audio Production issue is to just go buy a Mac.
I can't mod you up, as I've already posted, so I'll just aadd this note of agreement. The issue for me isn't just audio recording, for which Ardour is acceptable, but MIDI. Rosegarden was the only option for MIDI composition on Linux last time I checked (about a year ago), and it's incredibly unstable. Even Steinberg Pro 24 on an Atari ST was more stable. I ended up buying a second hand Mac and a license for Ableton Live instead.
Fundamentally, PulseAudio is architecturally flawed, and I don't get the impression from reading the rest of the Slashdot comments that people are confusing the roles of a networked audio daemon and a lower level kernel API. The problem is that PA is userspace, trying to do things that require kernel level control of timing. This is made worse by ALSA on Linux, which has poor latency, poor design, appalling code and sketchy documentation. I don't say this based on anecdotal comments from others, but on my experience working with ALSA in order to abstract the differences between various Unix like systems. In the BSD world, PA has only been (grudgingly) accepted because so many things now depend on it - but it actually duplicates some of the functionality already offered by the native kernel API. And just because a few big names are using it doesn't magically make PA any good - I can think of a number of widely used technologies that are piss poor compared to alternatives, but have become entrenched for reasons other than technical excellence. As for switching users on a desktop machine, I don't know anyone who does this, nor can I think of any reason why doing so would absolutely require an over engineered audio daemon.
The 4Front interpretation of GPLv2 is irrelevant - the source code is triple-licensed under GPLv2, CDDL and BSD licenses. ALSA is an excellent example of Linux throwing away a solid API and implementation that could have evolved to support the few critical features it lacked (which is exactly what happened in FreeBSD for example) in favour of a half-baked alternative. The original ALSA API is poorly designed by people who clearly have very limited knowledge of OO principles, but wanted to apply them all the same. This piss poor API was never well documented, and the actual audio drivers are not of the same quality as the ones in OSSv4. The ALSA developers answer to the poor API? Slap another, equally poor, equally undocumented API on top of it. What a fucking mess.
What that list actually means is that the license permits viral infection by the GPL - in that sense they consider them Free Software licenses, as they can be subsumed by the GPL.
Remember, *parts* of each of these things are open source, not all, due to apache license.
They are completely open source and Open Source - OSI certified, and GPLv3 compatible. They're just not completely "Free Software" (which is just a particularly restrictive form of open source and therefore less free in the dictionary sense than Apache licensed code).
Yet again a benchmark against a pre-release version of FreeBSD where the testers didn't even bother reading the documentation. Anyone actually familiar with the FreeBSD development and release process would know that a release candidate has a considerable amount of debugging options turned on. This is to help diagnose any problems as the last issues are shaken out of a release, but has an adverse impact on performance.
Err, an extensive collection of breast bondage literature in the bathroom isn't normal? Perhaps that's why whenever I let my spare room the tenant normally quits after a week. Either that or it's the guy in the gimp suit I employ as a cleaner that's putting them off.
I know from my own personal experience that nobody has made a better electric guitar than those early Fenders in 50 years either.
Speaking as a bass player, I can assure you that my 1998 Musicman Stingray plays and sounds better than any vintage Fender bass I've played. The vintage Jazz basses I've played all had a thin tone and overly narrow fretboard, while the Precisions sound dull.
I'd point out the successful projects on my CV, and then point out that they were all accomplished using common sense - not some bullshit laden methodology of the week. My "methodogy" if you can call it that? KISS.
My Rickenbacker bass has two truss rods in a side by side configuration. I've always assumed they were to prevent warping as well as keeping the fretboard bowed properly.
They wouldn't want those DMCA powers in order to take down pictures of people engaged in activities like... drug taking. A friend who went to a Burning Man festival said that most people he encountered there seemed to be whacked out on Ecstacy.
This is a good point, and probably worth clarifying by linking to one of the many projects that's dual licensed under the GPL and a BSD license. An example is the wpa_supplicant project.
Slashdot Mirror
If plants were such a poor source of protein then why is it the staple of the cattle we slaughter for food?
Because they have completely different digestive systems than humans.
Where's the protein we need in all that grain? And don't bother mentioning soya - that's what much of the South American rainforest is being razed to grow, and it's a very inefficient source of protein.
Depends on where in the world you are - in parts of Europe horse meat is readily available. It's a little bit like venison, and less fatty than beef steak.
Personally, I always prefer a lap dance when the stripper is crying.
It's [PA] structured the same way the audio systems on Windows and OS X are.
Like hell it is, and I say that as someone who has programmed audio and MIDI apps for OS X, Linux and NetBSD.
There should be no such distinction. Any "lower level" API should be an implementation detail of the application-level audio system, just as the PCI configuration space is an implementation detail as far as X clients are concerned. As for the traditional distinction between the audio deamon interface and the "lower level" one: it's an accident of history that we lived with that split so long. PA is a better world.
Last time I checked, PCI configuration was not time critical. As for the "accident of history", fact is you've got too much functionality in userspace.
As for POSIX real time scheduling? Just because the API exists doesn't mean it's implemented or configured on any of the major distributions, as it requires patches to the regular Linux kernel that would be detrimental to most peoples requirements. And my comment on switching users is no more anecdotal than Poettering's unsupported assertion that PA does what most users want.
I believe the solution to any *PROFESSIONAL* Linux Audio Production issue is to just go buy a Mac.
I can't mod you up, as I've already posted, so I'll just aadd this note of agreement. The issue for me isn't just audio recording, for which Ardour is acceptable, but MIDI. Rosegarden was the only option for MIDI composition on Linux last time I checked (about a year ago), and it's incredibly unstable. Even Steinberg Pro 24 on an Atari ST was more stable. I ended up buying a second hand Mac and a license for Ableton Live instead.
Fundamentally, PulseAudio is architecturally flawed, and I don't get the impression from reading the rest of the Slashdot comments that people are confusing the roles of a networked audio daemon and a lower level kernel API. The problem is that PA is userspace, trying to do things that require kernel level control of timing. This is made worse by ALSA on Linux, which has poor latency, poor design, appalling code and sketchy documentation. I don't say this based on anecdotal comments from others, but on my experience working with ALSA in order to abstract the differences between various Unix like systems. In the BSD world, PA has only been (grudgingly) accepted because so many things now depend on it - but it actually duplicates some of the functionality already offered by the native kernel API. And just because a few big names are using it doesn't magically make PA any good - I can think of a number of widely used technologies that are piss poor compared to alternatives, but have become entrenched for reasons other than technical excellence. As for switching users on a desktop machine, I don't know anyone who does this, nor can I think of any reason why doing so would absolutely require an over engineered audio daemon.
The 4Front interpretation of GPLv2 is irrelevant - the source code is triple-licensed under GPLv2, CDDL and BSD licenses. ALSA is an excellent example of Linux throwing away a solid API and implementation that could have evolved to support the few critical features it lacked (which is exactly what happened in FreeBSD for example) in favour of a half-baked alternative. The original ALSA API is poorly designed by people who clearly have very limited knowledge of OO principles, but wanted to apply them all the same. This piss poor API was never well documented, and the actual audio drivers are not of the same quality as the ones in OSSv4. The ALSA developers answer to the poor API? Slap another, equally poor, equally undocumented API on top of it. What a fucking mess.
...it wasn't a giant ring around Uranus.
No, but it is a dirty ring produced by irregular grinding. Sounds like the result of a diet lacking in fibre.
Tell that to the OpenBSD wireless driver guys who had there code re-licensed by some Linux developer.
What that list actually means is that the license permits viral infection by the GPL - in that sense they consider them Free Software licenses, as they can be subsumed by the GPL.
Remember, *parts* of each of these things are open source, not all, due to apache license.
They are completely open source and Open Source - OSI certified, and GPLv3 compatible. They're just not completely "Free Software" (which is just a particularly restrictive form of open source and therefore less free in the dictionary sense than Apache licensed code).
Yet again a benchmark against a pre-release version of FreeBSD where the testers didn't even bother reading the documentation. Anyone actually familiar with the FreeBSD development and release process would know that a release candidate has a considerable amount of debugging options turned on. This is to help diagnose any problems as the last issues are shaken out of a release, but has an adverse impact on performance.
Err, an extensive collection of breast bondage literature in the bathroom isn't normal? Perhaps that's why whenever I let my spare room the tenant normally quits after a week. Either that or it's the guy in the gimp suit I employ as a cleaner that's putting them off.
I know from my own personal experience that nobody has made a better electric guitar than those early Fenders in 50 years either.
Speaking as a bass player, I can assure you that my 1998 Musicman Stingray plays and sounds better than any vintage Fender bass I've played. The vintage Jazz basses I've played all had a thin tone and overly narrow fretboard, while the Precisions sound dull.
Google it - there's a lot of math blogs out there.
What exactly is funny about that comic?
Not a lot. And in the strips where the author tries to come across as a maths expert he normally fucks up and ends up looking like a knobhead.
That title should read "Dad Builds 700 Pound Cannon for Himself, Under The Cover of His Son's Birthday".
I'd point out the successful projects on my CV, and then point out that they were all accomplished using common sense - not some bullshit laden methodology of the week. My "methodogy" if you can call it that? KISS.
a guitar's fretboard is made of rosewood
Not always. The one on my Stingray is made of maple, and it's not a custom job or special option.
Truss rods do not stop necks from warping
My Rickenbacker bass has two truss rods in a side by side configuration. I've always assumed they were to prevent warping as well as keeping the fretboard bowed properly.
When I think of a slash I immediately amble of to the toilet. I certainly don't think of guitars.
Knowing about it's one thing, widely disseminated images proving it is another thing entirely. At least that seems to be the BMO's attitude.
They wouldn't want those DMCA powers in order to take down pictures of people engaged in activities like ... drug taking. A friend who went to a Burning Man festival said that most people he encountered there seemed to be whacked out on Ecstacy.
This is a good point, and probably worth clarifying by linking to one of the many projects that's dual licensed under the GPL and a BSD license. An example is the wpa_supplicant project.