The big problem there is graphics drivers for old cards, for which the vendors have discontinued their binary blobs and the opensource drivers never had good thermals and bus timing configurations for lack of documentation. In general, though, old machines can carry most of the newest distros while breaking a moderate sweat.

Maybe slashdot posters are all the prejudiced stereotypes you have in your mind, or maybe they just are frustrated with constantly reading about studies being invalidated by other later studies, with further salt rubbed in the wounds by pooor science journalism on top of that (like headlining an article about sugared soda as if it applied to all soda when diet soda accounts for over 25% of soda sales.) and perhaps they remember this article avocating larger sample sizes and more sound statitsical treatment in such studies.

I thought people who sat around opining about the code they expect other people to actually write were somehow paradoxically payed much better than that.

Because gen mobile needs to be able to type it on their crummy laggy error-prone on-screen touch keypads, preferably without ever shifting keypad state.

And when they do release an update, it will break something more important, and there will be no way to use the user interface to downgrade.

Similar experience. There were updates for my SmartTV but only for bullsit. Similar to how Sony only ever updates to PS Store and never fixes anything important that is broken.

Actually it isn't "just creating heat" it's creating a temperature gradient suitable for efficient conversion of heat flux to work, since the efficiency of that conversion is limited by the second law of thermodynamics.

Without weighing in on TFA or any of the other subject matter, or even the economics of nickel isotopes since I have no clue, materials that have little current use can and do cost more than they would were there reason to produce them, so to make that statement one must assess the projected cost of large scale production.

Yep as the TFA states:

However, with modern software's 7 layer abstraction burrito and race conditions up the wazzu, that's only half the battle.

What I meant is that some people do it in Europe. Here in the U.S. I've seen someone other than me do it about a grand total of once.

We do better than that in MA. Our left lane law was actually apparently written before multilane highways and never adapted. It's technically even illegal to take a left exit here (never enforced) and to use the middle lane unless passing.

There's a common code that many states to defer that gets it about right, unlike the "passing only" states: you have to be going the average speed of traffic to use the left lane, should pull over if safe to let people pass, and generally shouldn't use the left lane unless there's too much congestion for everyone to drive in the right lane. with exceptions for left exits and preemptive passing positions when going by entrance ramps.

In Europe they put on their blinker towards the median side rather than obnoxiously flashing their high beams to remind people in front to vacate the fast lane. Very civilized. This also lets the driver behind you know you'd pass the guy if you could.

This is pretty much the way I see it, working in the field. On the "pro-net-neutrality" side there are those with reasonable views on balancing common carriage with legitimate needs for priority, some with a basic level of network literacy with a wide range of conflicting specific suggestions who don't usually understand the consequences of what they are asking for, and a whole lot of people who don't even understand what it is they are asking for and prefer to converse in vague terms and catch phrases. I doubt there are even 3 million Americans who know what "statistical multiplexing" means so how are they supposed to weigh in on the issue.

Being a progressive my peers are generally surprised when I answer :"it depends" when asked whether I support "net neutrality" rather than "yes."

...or run the alternative userspace driver, which linux supports doing as well.

What really should be the question is why can't even Microsoft, which despite their software reputation generally is well reguarded for input accessories, not present a consistent interface across different generations of controllers. It's not like there isn't an enumeration standard they could follow.

Well, if the Microsoft would fix the damn surface so MFP doesn't break it and operators have to disable MFP, and the hotel sets things up right, nothing, just a bit of congestion.

What happens when conventioneers start using MFP? That's the real fun, there.

I work in a university IT department and we never go near those vendor features because of legal concerns. I don't know how the vendors get away with offering them.