I spent four damn years trying to have a dialog with Mojang and Bukkit about how to write good code and have a community that wants good code. The MC community literally does not want anybody participating if they have any sense of QA or planning for the future.

Remember, these are people that wrote their own cryptographic transport *three times* and called it good after nobody could post an exploit for it within a week. MC is not even willing to use standard things like TLS.

You picked a poor example, as PyPy is also state-of-the-art, PhD-powered, and loaded with just as much performance-enhancing optimizing code as V8. Additionally, JavaScript can easily be rejected on the demerits of being a poor language.

Haha, you actually think that just going into the Control Panel is sufficient to get the resolution set on a Windows installation? Oh no. No no no, no, that's not all, my friend.

So, let's take as an example my TV. I have a computer attached via HDMI to the TV. It picks a 4:3 resolution and the entire picture is shrunken; it doesn't fill the entire screen. Annoying.

You go into Control Panel. Or perhaps you're a "power user" and you decide to directly right-click the Desktop and get at the Resolution settings. Either one. You scroll through the list of modes. There are three dozen. You try them all individually. None of them correctly fill the entire screen without letterboxing, and all of them look somewhat shrunken still.

You pull out the TV's manual, sighing. Flipping through the pages, you finally find the one that lists the rather arcane timing numbers for the TV. Sure enough, the widescreen mode that this particular TV would like is not listed. You go back to your Control Panel, and decide that it's time to go into the driver-specific settings, promising yourself a cold one later.

Scrolling through the entire driver's settings panels, you eventually find information on over/underscan. For some unknown reason, the system has decided that your TV needs its scan adjusted by 8%. Setting it back to 0% unshrinks the display. Excellent. However, the mode is still wrong.

You continue to hunt through the driver's configuration, finding two spots where resolution can be chosen from a dropdown but no way to enter in manual timings. Rolling your eyes, you go through each of the three dozen possible configurations again, manually noting how close each one comes to filling the display and how badly the fonts are misrendered. Finally you come to one that nearly works, and resign yourself to having a slight letterbox on the top and bottom of your screen.

Meanwhile, that Linux laptop you have correctly finds the resolution on the first try, without any configuration needed. Your Linux workstation has the same problems as the Windows machine, but with a couple minutes of xrandr and Google, you've found a way to turn those arcane timing numbers in the TV's manual into a mode, and saved a shell script to do it for you should the need arise.

tl;dr: How do you change your screen resolution for Linux with Xorg? You don't need to, usually! If you do, xrandr. That's all.

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.

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?

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.