No not really. The SF controller is known to have a lot of issues.
http://www.xtremesystems.org/forums/showpost.php?p=4581793&postcount=11
http://www.bit-tech.net/hardware/storage/2010/06/25/sandforce-ssd-test/9
As soon as you do actual file copy tests or use real data the performance degrades. In addition, once the drive has been in use for a while, performance also degrades. This is a known issue with the way that the SF controllers support TRIM and GC.
One of the more humorous things with SF controller is that simply reading the same file over and over results in degraded performance!
I see three 'issues', first is massive file copies resulting in slower performance: Your first link says that if I absolutely hammer the drive (what would be considered 'seven days worth of writes over the span of a few hours' that the firmware will purposefully degrade write performance as a protective measure. That write performance will eventually be allowed to come back. Since I have no reason to do this, and neither does any other "standard" user, then I find it a non-issue. But let's think bigger: this is exactly
contrary to what you tried to tell us earlier about these drives being "benchmark only" that fail when they 'leave the parking lot.' Really, if this drive was going to be a stellar benchmark horse, this intentional degradation should make it look FAR worse than it really is. And I don't see that happening... So you need to decide which of your issues are really true: is this a benchmark winner and yet a loser in real life? Or is it a benchmark loser (because of this flaw) but still a winner in real life? It's looking a bit like neither to me...
The second issue: Uncompressable file performance. As the above, I fail to see how this would apply to me. ZIP files and MP3's and my DVD rips are bandwidth-unintensive or archive data, and thus are NOT stored on my SSD drive. Stuff that IS stored on my SSD drive would be things like Windows DLL's and binaries and other such applications -- things that, I have found, are very easily compressed. Further, they share a lot of 'common' data elements, and so write amplification can be considerably reduced at a block level (ie, subcomponents of individual files, similar to Microsoft's ImageX compression methods.)
Finally, TRIM performance degredation. Sure, it was an issue on older firmware, just as it was for the original OCZ Vertex drives with 1.3 firmware. When they upgraded to 1.5 firmware, all that issue went away (which was also covered in your link.) Same thing happened for OCZ Vertex 2 drives
So, I still see Intel's offerings as sub-standard to the SF-1200 and SF-1500 offerings. That's my opinion, and I really don't see anything you've presented that has much chance of changing my mind. Got anything else?