@IvoFlipse I really like the idea of a browser extension post.
@IvoFlipse It might be neat if we had a few different writers contribute to the post (or make it a series of post). Each writer could say what browser extensions they use.
@IvoFlipse Kind of like LifeHacker's "What We Use"
Views: 1027 (slightly lower than our top of 1124 but a very solid number for our third full week)
Top Viewed Post: "Why I switched from Firefox 4 back to Google Chrome" and "Microsoft Licensing - Tranferring Windows to Another Computer"
Top Refferrers: SuperUser(of course), Twitter was then next.
Other Exciting Highlights: @LucasMcCoy's post brought attention from the creator of MetroTweet. We also had a post each day for the week for the second week in a row!
Here are somethings that I would like to see this week:
1. A post everyday again. 2. I'm going to be doing the first WTF post this week, but please be thinking ahead for more ideas in this departement. 3. Productive Thurday hasn't started yet, anybody wanna take it on? 4. I would like to see a post about the maintance or actual use of SU (i.e. asking proper questions, how to edit, answering the best way
Windows 7 is heavily optimised to make full use of both the advantages and disadvantages of SSDs. There's a blog post from the Windows 7 engineering team about it: Support and Q&A for Solid-State Drives
Windows 7 will continue to use the swap file on the SSD, but this is fine as the usage p...
I suspect the main reason he was killing the HDDs was constant head movement generating heat, I suspect his application was more likely to be read heavy than write heavy and so an SSD probably would have been best for him anyway...
I think the world is missing an article on just how quickly you can kill an SSD. Most of it so far is just theoretical "if it is X% full, you could kill the remaining Y% in Z amount of time, assuming the wear leveller is doing it's job"
I could write a program in Python, I would call it SSDAssassin
You could test to see if the drive deallocates clusters that are no longer usable by constantly querying reported drive size...
I'm sure I've read about shrinking SSD in t'internet
I would love to benchmark one of these, but I'm too scared to ask the price: scan.co.uk/products/…
Apparently some guys at work managed to kill a 64GB SSD by constantly reinstalling Windows XP on it...
Hmm, aside from the drive and NTFS reporting that TRIM is available, is there any real honest-to-god way of telling that it is being used?
SSDs have been out for a few years, and have seen all kinds of usage patterns. Windows and Linux support the TRIM command, with Mac OS still trailing behind here. Update (30 Mar 2011): There is some hidden support in OS X 10.6.7 ("Snow Leopard"), with strong evidence that suggests it will be ou...
@IvoFlipse I blame you for getting me thinking about what else you can test on SSDs. Everyone has done read/write performance and all I can think of is destructive testing...
But it'd be like buying the Mona Lisa and then pouring paint thinner over it... :(
I wish my program-fu was strong, it'd be cool to write a side by side comparison type program for SSD and HDD. Constantly throw (say) 30MB/s at bot SSD and HDD, in varying proportions of read and write, in which proportions does one survive longer than the other...
I would suspect that either way the SSD would win, mechanical & heat death would kill any HDD long before you hit any kind of SSD problem...
I have an old P4 system (actualy like ten of them) and I'm going to strip the heatsync and take an old alluminum pan and try to head the egg in the pan...
very useful for when the next zombie inavsion comes
or when Gorgon freeman screws up our lives...
or just the plain apocalypse...
user30
9:32 PM
aluminium pan? sod that, throw it on the heatspreader. ;)
This blog post is not published yet. You can vote for this ad now, but until I remove this extra text, it will not get shown on the site (because it breaks the standard ad format). This post will be available on Tuesday, April 12th.
the ad is here! @IvoFlipse, @studiohack, @KronoS, @LucasMcCoy, @Mokubai, @ThomasMcDonald, @anyone else around