bobbo_

Not necessarily "better", but lower level and without the use of syscalls: on bare-metal x86 protected mode, writing characters to "video memory" (from 0xB8000, normally).

http://wiki.osdev.org/Printing_To_Screen

I tried out using x86_64 Linux assembly by writing a simple TCP echo server [1] after reading about the modern HTTP server in 64bit assembly [2]. Turned out to be not too much more involved than writing the equivalent in C, though very much at the cost of readability and development time.

There appeared to be relatively few examples of modern (well, 64 bit) Linux assembly out there, though quite a few relatively out of date documents like the one posted; documentation like the 64bit Linux System Call table were exceptionally useful [3].

[1] https://gist.github.com/bobbo/e1e980262f2ddc8db3b8

[2] https://news.ycombinator.com/item?id=9948749

[3] http://blog.rchapman.org/post/36801038863/linux-system-call-...

Alternatively, could they not just use the system as a response to DMCA requests? Mute out the offending portion when a rights-holder complains and leave (probably) the vast majority of videos generating ad revenue, without large portions of the video being muted pro-actively (and therefore basically unwatchable).

The system appears to be blocking copyrighted in-game audio, see [1] and [2].

[1] http://www.twitch.tv/dansgaming/b/550331246 [2] http://www.twitch.tv/adam_ak/b/555134005

"Another obstacle is that lots of schools teach non-free software, which is basically like teaching the kids to smoke tobacco".

I'm all for free software but RMS really does come out with some ridiculous statements.

Same thing on Chrome 35.0.1916.153 on Windows 8.1. Shame, it looks really interesting but that totally put me off.