I have just made history

I just created the world's first FART program using Windows 8's Metro UI.

How hard was it? I have heard that Windows' audio stack is an utter mess.

>>2
The Linux audio stack is magnitudes worse, with layers upon layers of encrusted shit. At least on Windows, the APIs are more or less consistent, and everything just works, including stereo mix recording, per-application audio settings and with proper hardware support for things like 3D audio effects, wavetable midi and the likes.

>>3
MS is not that far ahead:
http://www.guardian.co.uk/technology/2008/jan/31/microsoft.technology

>>3
Ahahaha, oh wow. I bet you believe that Linux audio image posted on that Adobe employee's blog too, right? Linux is far better than Windows in terms of audio.

Just install OSS or ALSA, and you're done; that's all you need. Of course, you can pile on crap like PulseAudio, but that isn't necessary at all. In addition, all those libraries that the Adobe guy mentioned (OpenAL, gstreamer, etc. etc. ad nauseam) are also commonly used on Windows, and thus if these libraries make Linux full of 'encrusted shit', then Windows is too.

I feel another holy war is about to start up again with this '8' shit. I tried to run it on qemu got an IRQ error. I'm over it.

Windows 8 Rapes your freedom, multianusally and uses all 8 cores to the maximum TDP.

ALSA is terrible. The kernel team need to get over their butthurt and switch to OSS.

>>4
MS is not that far ahead:
2008/jan/31
Perfect fagstorm!

>>8
No ancient 90s shit please. Get Lennart Poettering to write an audio stack from scratch.

>>8
I wholeheartedly concur.
>>10
That 'ancient 90s shit' is a rock-solid audio system that supports all the shit that ALSA doesn't and thus spawned PulseAudio because. Also, Lennart Poettering is a dick.

>>2

It was actually matter of 3 lines of code. Sound was working out-of-the-box here, the framework had the tools. It was just a rushing work to pick with the basics of building shit in the new UI.

I used C#, IHBTBM

>>2,3
Windows: open a directsound device and start writing samples to it
Linux: open the sound device file and start writing samples to it

>>13
Lisp: open my anus and start inserting cum in it

At least ALSA uses Lisp for scripting. And shitty PulseAudio segfaults like crazy. C/C++ quality!

>>11
That 'ancient 90s shit' is a rock-solid audio system that supports all the shit that ALSA doesn't
Because the core of ALSA is still C/C++. The only way to cure it is to write whole OS on Lisp.

I have had an idea to use a light version of an lisp interpreter (or compiler) to describe the expressions between the abstract and direct (hardware) controls. It seems that the main problem is how the lisp should be integrated into alsa-lib. The API for applications should be definitely in plain C. As Takashi noted, it might be that C -> lisp -> C path might be inefficient. In case, when we will have someday a lisp compiler which translate the lisp code to C, then the efficiency will be much better.
That is: C/C++ is guilty in all ALSA's misfotune.

Lisp: Incredibly Superfluous Parentheses

>>16
>>17
OSS is written in C, and yet it has none of the issues ALSA has.

>>4
That's to do with Windows Vista. Vista had all sorts of problems. They've been fixed with Windows 7.