http://www.tomshardware.com/news/Crucial-m4-Firmware-BSOD,14...
Not cool.
http://www.tomshardware.com/news/Crucial-m4-Firmware-BSOD,14...
Not cool.
I see no reason to change that. I'd rather spend fifty or a hundred bucks more and get a drive that I'm pretty sure won't fall flat on its face.
tl;dr - Crucial is one of a handful of brands I do trust, and I've owned a number of the M4 series.
Your M4s I wouldn't touch. There's nothing wrong with the hardware at all but the firmware sucks.
As far as you can go with SSDs is buy the ones with the least shit firmware, which is Samsung 840 Pro.
If your kit is mission critical, SAS is still the right choice.
Crucial/Micron RAM has no firmware!
As an ex EE this sort if crap is why I trust the hardware guys more than the software ones in life. We still haven't figured out software engineering yet.
Also keep in mind that for firmware often times an EE will be the one doing the programming and much of the time they picked programming as another tool on the way rather than as another separate field of work.
Software engineering and EE are different in a lot of ways though. It's a lot harder to modify a EE design after it's shipped. You're also often designing around a particular manufacturing process. I think that makes you focus on getting things working correctly before it gets out the door.
Software engineering has a long way to go, but I can also see the EE world does too. A lot of the EE design tools suck, lack standards, and often don't (or aren't) integrate well with revision control. The design process therefore, tends to be a bit messy during development.
The fundamentals of EE work do seem to been clearer than software engineering though. I think this is partly due to EE having developed a mature set of design patterns, but also because it relies on a standard set of components which are really based on physical properties and as such strict and concrete in their definition as opposed to most concepts in software engineering.