http://www.youtube.com/watch?v=WgbK0ztUkDM&feature=player_detailpage#t=3195s is the video. In short, I asked the NaCl guy whether they knew what they were doing by letting NaCl clients access GPUs directly. His response was that they were doing everything WebGL does to protect the system from malicious code. That's unfortunately not sufficient.

I asked the Chrome team (see http://www.youtube.com/watch?v=cQZu6azNlA0&feature=player_detailpage#t=514s ) and yes, it runs Gentoo Linux just like the Cr48. The marketing team at Google apparently has a Linux allergy.

Chrome OS is Gentoo Linux. One of the things that Google's marketing team isn't wanting to admit.

Did you know that Haskell, Ruby, and Python exist? They have many of C#'s features, while not being C#. Consider it sometime.

IOCP or WMFO are both options on Windows which are worth investigating. Thankfully, a bit ago (sometime last decade) somebody wrote a Java library called NIO (http://en.wikipedia.org/wiki/New_I/O) which provides platform-independent networking services, and somebody else included it into the Java standard library. Then, some people wrote a thing called MINA (http://mina.apache.org/) which provides even better networking services on top of NIO, and somebody else got the Apache guys to maintain it.

So yeah, there's no excuse for thead-per-connection these days. Using NIO or MINA in Java is the right way to build asynchronous servers.

Also, is that whole thread-per-connection thing gonna be fixed before then? (Signs point to no, of course.)

Specifically, my X.org student last year did some great work in the r300g Gallium driver for Mesa, and is still a developer in the project to this day. There's a single success story. I'm sure the other several thousand success stories will be along shortly.

I wonder if this iteration will be less prone to overheating. I have an original GuruPlug which still gets too hot to use for long periods of time.

OR? Oregon's not exactly a bomb-proof place, unfortunately. Portland, OR is one of the three good West Coast spots to drop a nuke. Intel's here, Linux is here (technically, Linux is in Corvallis, but still), and we're in range of ICBMs from the other side of the Rim.

To be fair, they could probably code a better Minecraft than the official client and server that Mojang have been putting out. :3

Python 2 has Unicode string literals...

$ python
Python 2.6.6 (r266:84292, Sep 15 2010, 16:22:56)
[GCC 4.4.5] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> if len(u"£") == 1: ... print "Lawl @ some kid thinking PHP's a real language" ...
Lawl @ some kid thinking PHP's a real language

And of course, Python 3's strings *default* to Unicode...

$ python3
Python 3.1.2 (release31-maint, Sep 17 2010, 20:27:33)
[GCC 4.4.5] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> if len("£") == 1: ... print("Wait, Unicode by default? Awesome!") ...
Wait, Unicode by default? Awesome!

So I think you need to go stuff it.

The inconsistent type system, lack of Unicode support, lack of namespaces, quirky parser, and other stupidities (== vs. ===) weren't enough, so. Is this bug inane enough to actually get people to realize that PHP bites?

Ever read Raymond Chen's book? It's pretty terrific. There's an entire section dedicated to showing how Win32's stable API and ABI in kernel and user space has been a horrific nightmare and is a large waste of developer manpower.

Also, the *only* people affected by the lack of stable ABI are people that ship out-of-tree kernel drivers, all of whom have no excuse for not immediately pursuing upstream merges of one sort or another.

Also, some exported kernel APIs, like the syscall list and ioctl list, are sacred and are never altered. To take a topical example, all KMS graphics drivers respect and give sensible return values for legacy userspace X components calling pre-KMS settings.

And finally, to answer your strawman, *yes*, you can get a driver accepted if it has no users besides yourself. IBM's notorious for this; one of their upstream drivers has something like 2 users in the entire world. The drivers that tend to be controversial are things like reiserfs4 (layering issues, maintainer conflicts), aufs (layering issues, code quality issues), OSS4 (licensing issues, maintainers want to keep it out-of-tree!), etc. where there are clear and obvious reasons why the upstream merge hasn't happened.

Hell, for DRM, this was a problem too, since the DRM/libdrm tree was buildable for BSD as well. We made the decision a bit ago to merge into the Linux tree and make the out-of-tree repo for libdrm only, and all of a sudden, life gets *easier* because we no longer have to switch back and forth between Linux and BSD compat.

This would trash the Chinese economy as well, crashing the Asian and American markets simultaneously.

At the same time, /v/ is no longer about video games, /mu/ is useless for talking about real music, etc. The best board is easily /po/.

It's certainly a better place than DA for artists, but that's not saying much.