We are getting more off topic here, but @jwilliams you seem to be very anti SSD. Once I used my first one I could never go back. I have a Mini-ITX machine with an Intel i3-2120 and an OCZ 256GB SSD running Arch with Gnome 3.10 and a 3.12 kernel. The longest part of the boot process is me typing in my password and shutdown takes about 5 seconds. Big programs like LibreOffice Writer open almost instantly. And the box rarely uses more than 26w and it is very quiet (the only moving part is the CPU fan). I have never had any issue with the SSDs. My first system was an SSD boot drive (/), with swap and /home on a second HDD - fast enough for most people, but since then I just have an SSD and lay off data storage to my NAS.
Failures do occur (so far not to me), but then I have had a few HDDs fail as well. I do back up important data to a NAS, but then I did that in the olden days of HDDs as well. A friend of mine recently had an early OCZ SSD die after just less than three years, and he did not even consider going back to an HDD. He got a new drive and restored his disk clone and went on his merry way.
Just my opinion as a very happy SSD user.
My workplace-provided laptop has a SanDisk Sandforce SSD that just plain LOCKS UP upon large TRIM operations. I've just given up on having TRIM enabled on the thing.
I hope Canonical will document this some way, so anyone with drives that behave this badly will know to blame the drive, not Ubuntu.
Does e.g. Fedora or Arch have TRIM enabled by default?
Exactly what are they discussing? It seems like a no-brainer that they ought add a daily cron job by default for supported drives.