The good news is the modern desire to 'web all the things' with stuff like ROR, PHP, Tomcat, etc; you can generally find in the code where something is an issue without having to necessarily trace system calls. You don't have quite that luxury on compiled applications. Though occasionally you could run into issues with the interpreted languages that just don't compile properly and cause problems--then you're back to the same problem...

For what it's worth, even if you do have access to dive into the code/kernel memory to find what the problem is, you must first know how to read what you're looking at. A lot of good this stuff does for you if you have no idea how it works in the first place. That's not a uniquely Windows problem, though; because very little in the Linux Admin world over the years strictly enforces that you should know this stuff. The technical information on it out there is about as good as the Technet articles on Windows that tell you how to appropriately identify system bottlenecks (Disk Queue Length, etc.).

I believe dtrace was added not too long ago and seems to be the goto solution for most Linux admins I know, but I've not personally used it to seek out issues.

This person knows what's up.

The issue with #6 is that users almost invariably never accept an answer here. And a lot of the time it may be something you can't adequately explain, which is something they don't like even more. Especially if you know the problem wasn't the result of something you did.

I'm willing to bet that Western Europe and Canada numbers are actually pretty accurate. Same with the US numbers. The only places that might underreport are likely to be Russia and 3rd world countries.

The bigger question you need to ask is why is the US so far behind its first world brethren?

The reality is that US History courses don't do enough to explain what it was like to live in the 1800s and the kinds of shit people had to put up with.

http://www.continuetolearn.uiowa.edu/laborctr/child_labor/about/us_history.html

It's easy to look at that on paper and say "well that wasn't very long!", but there was a period of 68 years between the first state law limiting child working days to 10 hours and the push for national reform. Most of the people on slashdot have not been around for 68 years...At 68 years, some of your friends have already died after working in factories for most of their lives, and you are on the edge of your death bed.

Oh, it was also Unions that made this happen.

There's far more involved with labor situations in the early industrial era.

None of the things the person mentioned above are "rights". You don't have a "right" to use the taxi, train, or other public transportation systems. You do have a "right" to not vaccinate your kids, but schools have no "right" to accept your kids.

if you want to home school your kids and drive them everywhere and take care of them--then do that. But the rest of society should not suffer because of your decisions.

All this study says to me is that White Males and Asian Males typically have more free time capable to dedicate to this sort of endeavor.

I disagree with you on the "most people who work in the sector have no clue" statement. People have long known about IT security issues. It's not like things like "sub7", "winnuke", "nimda", "code red", etc. weren't issues.

We've long known about NTLMv1 issues and it was strongly recommended as a hardening practice as early as 2001/2002 when Microsoft implemented it.

The issue has never been "nobody having a clue", but more like, "Management not giving a shit". Yes, the state of information security is atrocious. But that doesn't stem from the IT guy so much as it comes from having to approach management, "Hey; we need to upgrade to this system to improve our security and reduce our risk."

Blame IT for not being able to put it well, or blame them for not being able to play the social game well enough to get the boss to want to listen to them over their friends. But in some cases, you really don't have much leg to stand on. Even if you were logically correct, even if you were on the boss' good side; the reality is the guy who says "NO DON'T UPGRADE JUST STICK WITH WHAT YOU GOT AND THROW THIS LITTLE BOX IN FRONT OF EVERYTHING!" is going to win--all of the time, for the simple fact that he appeals to the boss' wallet.

Telling business leaders they need to not only spend money in IT, but spend it repeatedly and regularly, is something that is almost never going to go over well. And it's something that's needed to keep up. The "bar" itself is constantly moving.

It seems he's coming more out of the woodwork now rather than sitting behind the scenes and letting the documents do the talking.

That's 4 hours to shower, 4 hours to shop, 4 hours to eat (breakfast and dinner), 4 hours to clean...

The sad part is there are people out there that think this very thing. That you're "playing with god's will" if you use antibiotics in such manners. Don't even get me started on the food supply.

http://opensuse.14.x6.nabble.com/SSD-detection-when-creating-first-time-fstab-td3313048.html

If you read the source for the information on the 'performance hit' issue, It looks like Windows 7 is not performing the TRIM command in the same manner for which there was a performance hit with the 'mount -discard' option when using ext4.

"Also, it was assumed 9 months ago that Windows 7 did it that way. But
since then one of the kernel devs got a sata protocol analyser and
monitored how Windows 7 is doing it. Not like "mount -discard" at
all, so that whole paradigm seems like a rat hole to me. "

"Note FITRIM is still not as good as what Windows 7 is doing. The
claim is aggregating multiple trim ranges into one ATA command is hard
for the kernel to do, so it is still on the wish list, not the done
list."

Whatever is implied by these 2 tidbits means that Windows is handling the situation much better than the Linux kernel.

How is there a performance hit? I get over 500MB/second reads and writes on my Samsung 830 SSDs--each. I've pushed over 1GB/sec when I had them in a RAID0.

There is a much higher performance hit by not "trimming" your drive. And if this isn't enabled by default, it means a vast majority of Linux users out there with SSDs are experiencing significant performance degradation that they don't even know about.