Like I said, I'm speaking generally, and from my own anecdotal evidence. In my career, including consulting with a variety of companies with their own IT people, I've known maybe one or two that seem to be trying to hide things to create "job security". They were generally incompetent, and were fired before too long, in spite of their "job security". I'll note that I operate within a fairly competitive market.

That is a good question. The answer is basically "many things". My point is, they may be lazy and worried about losing their jobs, but it often manifests as a reluctance to take on new projects or make big changes, and general neglect for maintenance and upgrades. But you have 'resistance' in various forms. You might be looking at a crappy old 12 year-old server that's bound to fail soon, and you think, on the one hand, I don't want to catch hell when this thing dies. On the other hand, I don't want to argue with management, who will claim that the upgrade isn't really necessary because things are currently working, and they'll say that the price of a new server is unjustified. Plus, it'll take a lot of work for me to perform the upgrade, and if anything goes wrong I'll be blamed. Some of the blame will be justified due to the fact that I'm not actually familiar with the new hardware and software that we'll be using if I upgrade. And does the new version of our business-critical app include all the features that we need? How much training will be required for the staff to adjust to the new system?

So you put all of that together, and sometimes the IT guy picks the path that seems less scary. That's more or less what I mean by "the path of least resistance".

I see this kind of idea floated in various situations, and it always seems bizarre to me. As someone who has worked in quite a few IT roles in quite a few different companies, I don't think I've ever run into a sysadmin who was making things more difficult for the sake of job security.

I've seen sysadmins do counter-productive things out of pride and stubbornness, unwilling to entertain a new way of doing things. I've seen them continue to use ineffective solutions out of fear, believing that the alternatives are too difficult to learn, too difficult to implement and support. Speaking generally and anecdotally from my own experience, sysadmins will enthusiastically welcome anything that means less work for themselves.

And "If everyone used Linux, there would no doubt be less demand for cleaning up PCs"...? No. People make that mistake all the time. "The IT department is pushing back on our goal of moving all of our servers to the cloud. It must be because they know it will mean there won't be any more IT work to do maintaining the servers, and they'll be out of a job!" Or "The IT department doesn't want to migrate to an all-Mac environment. It must be because Macs 'just work' without any problems, and they'd then be out of a job!" Sorry, no. Unfortunately, there's nothing that will get we IT people out of our jobs.

Speaking for the sysadmins, we'd almost welcome the soul-crushing unemployment if it actually meant things would work properly. But no, really you're just changing the nature of the work we need to do. Instead of maintaining our own servers, we then have to figure out which cloud service will work for the business needs, work out an implementation, and then manage and troubleshoot the cloud service on an ongoing basis. Moving to Macs or Linux machines, it just means we now need to figure out how to replace all of the Windows-only business-critical applications that your business is running, and then come up with a scheme to protect and manage all of those Mac/Linux workstations. Believe it or not, a Windows DC with Group Policies is a pretty effective way of managing a lot of desktops/laptops.

So either way it's work, and it'll require someone with expertise. And no matter what, it's not going to quite work properly. We're usually just looking for the path of least resistance.

Going way off-topic, I don't know if I'd say that people like it, but I also don't know that I'd say that it's just because it comes on computers when you buy them. I think it's more that, over the course of the ownership of the system, you'll probably have fewer problems.

And that happens for a variety of reasons. One of the big ones is that it's more widely supported by hardware and software vendors. I think that is a major point. If you could get Microsoft Office and Adobe CS on Linux, I think you'd see a significant increase in adoption just from that. Yes, I know there are alternatives, but when people decide they want a particular application or a specific peripheral, they aren't going to like finding out that they can't use it because they have "the wrong kind of computer".

But getting slightly closer to the topic at hand, I think part of it is also just that they more or less know what to expect. Until the Windows 8 debacle, they knew which buttons to press and what would happen when they pressed them, more or less. People usually don't want to figure out how to operate their computer. They just want to know which buttons to press in order to get the result they want, and any change that moves or renames those buttons is unwelcome. If you must move or rename things, you'll get a better response from most people if the new way of doing things is so intuitive and obvious that they don't need to actually learn anything.

Well, except for the bump at "100 bpm or greater". I didn't realize so many squirrels read slashdot.

A little offtopic, but since you bring it up: All hate aside, I've come around to think that the Windows 8 GUI, ignoring the Metro/Modern stuff) is very nice. It succeeds in hiding a lot of the complexity and nonsense while still allowing power users to be efficient. It's very clean, and makes good use of the interface conventions that everyone has gotten accustomed to over the past few decades. If they'd kept the start menu and ditched all the Metro stuff, I think Windows 8 would have been a big hit.

And I think there's a possible lesson there for KDE and Gnome and any other UI designer out there: Instead of constantly trying to reinvent the wheel, sometimes it's better to just refine the UI you already have, removing inconsistencies and redesigning anything that's confusing, problematic, or ugly.

Really? Why Johnny Can't Encrypt: A Usability Evaluation of PGP 5.0. Yeah, it was a while ago and some things have improved, but most of the issues remain and I doubt another focus group study would find significantly different results.

The problem is that designing a UI that makes it easy for people who don't know anything about cryptography or security to achieve useful cryptographic security is really, really hard. Almost as hard as educating everyone about cryptography and security enough that they can achieve useful cryptographic security with PGP.

Java did that years ago. Notice how it destroyed Microsoft?

This is the sort of criticism that software developers really need to get, and it seems good that maybe KDE is listening. I wouldn't be surprised, though, if a lot of people respond to this by saying the criticisms are stupid, that "if you know what you're doing" then you'll understand what's really going on, etc.

The engineers working on Windows 8 knew the Metro UI was crap for the PC. The usability studies all showed that the Metro UI was crap for the PC. It was senior management that forced the issue over the protests of those involved.

The reason I have hope for MS yet is the result from all that. The entire management chain responsible for that, right through the CEO, all of them gone. Gates, Ballmer, Larson-Green, and middle managers below her well fired or moved away from PC computing. Someone, somewhere, decided enough was enough.

Will the new guy be better? Who knows. But we've had decision after decision that left consumers saying "WTF?" being rolled back, starting with firing that X-Box VP whp insulted the customer base and reversing his decisions on used games and always-on DRM and hopefully through the restoration of the start menu. Of course, if Windows 9 ends up sucking, MS is as dead as a very dead thing.

Had TC been an open standard, it could have been a great thing. Think: locking down one VM such that no virus can taint it, which you can then use to scan the rest of the system with assurance that the results are valid.

But instead it was a joke. I was doing standards work while the TC "standard" was being hammered out, and while they were in the same Hotel as real ISO standards work, you had to be there from a member company and sign an NDA to even listen to the discussions. We didn't take them seriously (the normal ISO/INCITS rules are that anyone who shows up can participate, you only need to be from a paying company to vote, and that minutes are always public).

Forest coverage of America has grown quite a bit over the past 50 years because so much farmland - most of it, in fact - has been abandoned as unneeded to feed us, or to saturate the export market. By far the majority of arable land is no longer cultivated, out of lack of need, unless you count tree farms.

I have found that asking the following about a potential workplace is a remarkably good predictor of the entire work culture and acceptability for devs:
* What version control tool is used
* What bug tracking system is used
* What technological measures are in place to prevent anyone breaking the build, with no need to back out changes
* What automated testing infrastructure is in place, and are new check-ins automatically sanity-checked immediately

You can really learn a lot from the tools used. Are the tools in place those that devs would choose, or some horrible crap sold to management by a good sales guy? Did projects to make dev life better by automating the programmer workflow get funded, or get blocked? How short-sighted is management when it comes to productivity?

Software dev as an industry is out of the downturn. Demand is way ahead of supply right now, mostly because devs still think there's no point in looking. Well, times have changed, and a dev has a lot of "pricing power" right now. E.g., my team has quite a few open positions, no one with experience seems to be looking, and we're definitely not going to lose anyone qualified we actually manage to find due to being cheap!

Sign of an engineering field that hasn't matured yet. Most big companies do have engineering promotion paths all the way up to VP-equivalent now, so that's something, but you still don't see as many devs in paygrades equivalent to senior management as you see senior dev managers. They're not really taking that career path as seriously as high-tech "real engineering" jobs yet. But, yeah, at least find a place that has a non-management paygrade above the one you're applying for!

We can trivially feed 11 billion today. The farmland once used in America alone could do it (though that would be a bad approach for many reasons).

Your ideas about nutrition are way off. Calories are key to survival, and meat is not where you get calories, carbs are. Meat is a tasty luxury that requires more farmland per meal than eating vegetarian.

Fresh-water availability, as I already said, is only an issue in large cities that insist on drawing down their aquifers (well, and a few low-population areas with regular drought). Cities tap their aquifers only because it's cheap compared to proper sewage reprocessing. No magic technology required, just infrastructure spending. There are very few big cities that actually lack the surface water (e.g., Dubai), but they have desalination already. Wikipedia has some notes on the plants currently under construction and operating around the world. Again, it's not high-tech, as long as you're on the coast.

Native-born net population change is either negative or barely positive in every industrialized nation. Many places with high barriers to immigration are in population collapse right now (e.g., Japan). America is only growing due to immigration. It's a common pattern, well, researched and well understood. People have enough kids such that enough survive to help them in old age. Pre-industrialization, that's 10 or more. Post-industrialization that's 2-3, or fewer once a good retirement safety net is in place. There's a one-generation blip seen in most places during industrialization when people are still having 10 kids, but all of them survive to adulthood, so population explodes.

The news that population was expected to peak at 11 billion is at least 10 years old - not sure why it's a /. story, but we do like old news here.

Sure, sure, preventing discrimination is good, but that's a somewhat limited excursion into regulating who can do business that ensures more people can participate in the economy. But what we usually see is government doing the opposite granting monopoly, and otherwise excluding people form the market, instead of busting trusts and otherwise enabling participation.

We see this in spades in the entertainment industry in the US, with cable monopolies being granted like localities were competing in "monopoly granting" as an Olympic sport or something.

But anyway, none of that has anything to do with giving the government access to what books you read, or what movies you watch, or the like. Governments just need to stay the Hell away from that data, even if it would be convenient for the government, well, too bad!