Well, dairy farmers still use BGH, and this was over 12 years ago and most milk drinkers are not dead...
What a horrible misrepresentation of the truth. Many large retailers refuse to sell milk from dairies where bST is used. For example, here in Oregon, Tillamook products have no bST. Neither does any milk sold at Safeway or Wal-Mart, two of the biggest grocery chains in the area, and many other grocers like Albertson's, Fred Meyer, Market of Choice, and so forth promote and market bST-free milk. I don't actually know where I would go if I wanted to obtain milk from a bST-using dairy.
This stuff's banned in the rest of the modernized world. Banned in the EU, banned in Canada... Over half of all milk sold in the USA is bST-free, too.
While you might be technically accurate on the rest of your post (which I highly doubt but don't feel like getting into), you are straight-up wrong on BGH/bST.
I don't know why you think that Valve will keep their modified drivers to themselves. Hint: You can't mix 'n' match acceleration drivers between your desktop and your applications except under extremely controlled conditions.
MesaGL is an implementation of the GL API that can use any of several backends to do its actual work, including a couple software renderers and also hardware renderers for many Intel, AMD/ATI, and nVidia chipsets. Your distribution probably splits each renderer into its own package for historical reasons.
The nuclear power plant in-show represents Weyerhaeuser ( https://en.wikipedia.org/wiki/Weyerhaeuser ), a large paper company for whom just about everybody worked in the 80s. Either you worked for them, your spouse worked for them, or your parent worked for them. This was the big industry in the Eugene/Springfield area when Groening was young. I imagine he went with a nuclear power plant instead because of the comedic opportunities.
There have been unofficial statements that certain parts of the kernel and userspace, driving certain pieces of the SoC like the 3D rasterizer, will not have any corresponding source code available and will only be made available as licensed binary blobs.
Can we get an official statement on the matter? What's your stance on open drivers, and why are you for/opposed to them?
I am not a full-timer, and I am not speaking on behalf of OSL.
The "legal reasons" alluded to are mostly problems with other signers on the contract for our upstream bandwidth provider. *coughDuckscough* At our bandwidth scale, tunneling is not feasible.
We don't run Puppet at the moment, we run CFEngine. Everybody's receiving Puppet training and there's a slow-yet-steady migration to Puppet, but these things take time. There are quite a few people depending on us to not fuck up, so we don't change our stacks without deliberation and testing.
Disclosure: I work for the Oregon State University Open Source Lab, which recently received donations from Facebook.
I've been out to this datacenter. They employed quite a number of locals to build the place, and although the skeleton crew is only 35, they plan to keep a bigger crew of hundreds out there most of the time. In the medium term, they plan to build *two* more buildings the size of their current one, extending their current need for construction for another two years or so, and requiring a reasonably-sized group of engineers to live in the Prineville area for a while. So Facebook's put money, jobs, and consumers into Prineville, and apparently, according to the locals, this was a real lifesaver for many of the construction workers who were otherwise broke and unemployed.
I'm not a fan of Facebook, but this doesn't really seem like a horrible corporate exploitation.
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.
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.
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.
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.
$ 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!
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.
Slashdot Mirror
Well, dairy farmers still use BGH, and this was over 12 years ago and most milk drinkers are not dead...
What a horrible misrepresentation of the truth. Many large retailers refuse to sell milk from dairies where bST is used. For example, here in Oregon, Tillamook products have no bST. Neither does any milk sold at Safeway or Wal-Mart, two of the biggest grocery chains in the area, and many other grocers like Albertson's, Fred Meyer, Market of Choice, and so forth promote and market bST-free milk. I don't actually know where I would go if I wanted to obtain milk from a bST-using dairy.
This stuff's banned in the rest of the modernized world. Banned in the EU, banned in Canada... Over half of all milk sold in the USA is bST-free, too.
While you might be technically accurate on the rest of your post (which I highly doubt but don't feel like getting into), you are straight-up wrong on BGH/bST.
I don't know why you think that Valve will keep their modified drivers to themselves. Hint: You can't mix 'n' match acceleration drivers between your desktop and your applications except under extremely controlled conditions.
MesaGL is an implementation of the GL API that can use any of several backends to do its actual work, including a couple software renderers and also hardware renderers for many Intel, AMD/ATI, and nVidia chipsets. Your distribution probably splits each renderer into its own package for historical reasons.
The nuclear power plant in-show represents Weyerhaeuser ( https://en.wikipedia.org/wiki/Weyerhaeuser ), a large paper company for whom just about everybody worked in the 80s. Either you worked for them, your spouse worked for them, or your parent worked for them. This was the big industry in the Eugene/Springfield area when Groening was young. I imagine he went with a nuclear power plant instead because of the comedic opportunities.
I don't like C. Have Forth. https://github.com/MostAwesomeDude/cauliflower
There have been unofficial statements that certain parts of the kernel and userspace, driving certain pieces of the SoC like the 3D rasterizer, will not have any corresponding source code available and will only be made available as licensed binary blobs.
Can we get an official statement on the matter? What's your stance on open drivers, and why are you for/opposed to them?
~ C.
https://github.com/MostAwesomeDude
https://www.ohloh.net/accounts/MostAwesomeDude
http://cgit.freedesktop.org/~csimpson/
http://git.kernel.org/?p=linux/kernel/git/csimpson/linux-2.6.git;a=summary
Your turn. Put up or shut up. >:3
We employ roughly as many programmers as sysadmins, and write plenty of code. http://code.osuosl.org/
I am not a full-timer, and I am not speaking on behalf of OSL.
The "legal reasons" alluded to are mostly problems with other signers on the contract for our upstream bandwidth provider. *coughDuckscough* At our bandwidth scale, tunneling is not feasible.
We don't run Puppet at the moment, we run CFEngine. Everybody's receiving Puppet training and there's a slow-yet-steady migration to Puppet, but these things take time. There are quite a few people depending on us to not fuck up, so we don't change our stacks without deliberation and testing.
I see what you did there. :3
Disclosure: I work for the Oregon State University Open Source Lab, which recently received donations from Facebook.
I've been out to this datacenter. They employed quite a number of locals to build the place, and although the skeleton crew is only 35, they plan to keep a bigger crew of hundreds out there most of the time. In the medium term, they plan to build *two* more buildings the size of their current one, extending their current need for construction for another two years or so, and requiring a reasonably-sized group of engineers to live in the Prineville area for a while. So Facebook's put money, jobs, and consumers into Prineville, and apparently, according to the locals, this was a real lifesaver for many of the construction workers who were otherwise broke and unemployed.
I'm not a fan of Facebook, but this doesn't really seem like a horrible corporate exploitation.
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 ... print "Lawl @ some kid thinking PHP's a real language" ...
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:
Lawl @ some kid thinking PHP's a real language
And of course, Python 3's strings *default* to Unicode...
$ python3 ... print("Wait, Unicode by default? Awesome!") ...
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:
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.