In Windows, when I perform a delete operation, the TRIM command is automatically sent along with the DELETE operation command. No scheduled tasks needed.

This isn't quite as accurate. Most SSDs these days are built with space already overprovisioned. For example, a 128GB SSD might actually have 160GB of NAND flash inside of the device, with the remaining flash unreachable by the operating system and is used by the device.

Essentially, the age old adage of "over provisioning" is not actually that necessary on modern systems.

There is nothing you do special in Windows to enable TRIM support. It is included support directly in the OS and the drivers, automatically. The only time you have to do anything special in Windows for TRIM support is when you're actively using Intel SSDs in a RAID configuration using the Intel Rapid Storage Driver--and even that is merely a driver update, and boom, RAID0 TRIM support passed from OS to driver to device.

That's it. Under all other circumstances TRIM is automatically enabled and there are no extra utilities needed under any circumstances.

The post here is entirely too alarmist. Essentially, the guy stole his employer's software because he had a philosophical difference with how the company should be handling the source code and went to offer it himself.

In short, this isn't a "violation of the 4th amendment" so much as it is an excuse to try and get access to the guy's hard drive and recover stolen assets.

And yes, I do believe he stole the code.

Absolutely. It seems all the posts blasting the 'President' for this stuff people intending to blast the President himself rather than the process. Yes, The US Congress (legislative branches) have authorized all of these programs, repeatedly. And people will continue to vote for them, and even I will; because the alternatives are FAR worse.

I am willing to exchange a little bit of my personal privacy for the rights for gays to marry. That's just how it goes. It's a trade off I accept.

Exactly this. The kind of person you're looking for is probably going to be outside the bounds socially. And if you're not willing to exchange how you THINK a person should dress or behave in exchange for their knowledge; then you're going to have some real issues.

I'll reply to this, not as an AC, and not as an MS Shill. In fact, I've had this Slashdot account for years.

I recently switched to a Windows Phone (Lumia 920) from the iPhone 5 through that promotion that Nokia is running for trade ins. Yes, I voluntarily funneled out $450 for a Lumia 920 (of which I'll get $360 back when I send 'em my iPhone 5)

Anyways...

Overall, I've been happy with the phone. It works reasonably well. And while the lack of apps can be a problem, it hasn't detracted from the functionality of the phone itself. The best I can say is 'different'.

I also like the live tiles over notification center...

For what it's worth, Surface Pro (A Microsoft-built device) allows you to disable Secure Boot support if you so choose.

UEFI -> Secure Boot -> Measured Boot (requires TPM)

This isn't any different than the way Steam works right now...

I guess you use a different version of Windows 8 than I do, I've found the experience to be quite useful.

Indeed they would.

The only people stabbing anyone in the back are the corporate overlords you so revere. What do you propose the solution to the aforementioned problem is, if not to organize?

I'm a bigger fan of violence myself, but I'm not stupid enough to think I'd be leading some sort of revolt in the process, so I don't carry it out. But I wouldn't be surprised if it came to that.

Have you ever worked in IT? Because I can assure you it's a lot more challenging than that.

You see, at 1 update/day for 50 days, you risk potentially breaking any application that the business uses. Every update is not just "rolling out Java", it's the following:

1. Hunt around for download links for a full, offline version of the installer.
2. Find out which management system you're going to use to do remote installs to every system.
3. Write up a change control document and follow an approval process to get changes out.
4. Test said update to a test environment as best as you can.
5. Get approval for update.
6. Roll out update to users.
7. If update breaks something, roll all users back.
8. Try to explain to management why IT just caused significant downtime.

How do you propose we handle this?

If it's a web application it's reasonable to assume that browser caching would cache certain data on the hard drive. Even "clearing cache" would only delete the headers and not securely delete all of the data. With IE, you can enforce a GPO that tells the browser not to cache data retrieved over HTTPS ; but this is assuming that HTTPS is used for internally connected systems (often times they're not), and it assumes the user is using Windows in an Active Directory environment.

The other thing is policy. I work in an organization developing policy surrounding HIPAA data and I can tell you that it's significantly easier to have a global overall encompassing policy than it is to separate out what data should and SHOULDN'T be copied off of the server. If a user has read writes they have the rights to copy data to their HDD. So we treat all systems, even ones not directly involved in dealing with HIPAA data as the same. It makes it much easier to say with certainty that appropriate security measures have been applied.

For what it's worth that's actually not a whole lot of money depending on the development practices of the organization.

* Cost of resources used (PCs, software, servers, etc.)
* Development, QA, Lifecycle
* Project Managers, Managers, Business Analysts, Developer