Am 04.02.2014 um 23:29 schrieb [email protected]:

> I want computation power and disk space. Apparently this is too much to ask 
> of Apple. Smallish hard disks and not really enough RAM and who the heck 
> thinks soldering that RAM to the board is a good idea? Really! And at the 
> store I could get the barely adequate RAM or the maybe-enough disk space, but 
> not both. If I want both, I have to order on-line. Wow. Never mind.
> 
> So I got an Asus with twice as much hard disk space and similar CPU speeds 
> for less than half the price. I figured out enough about WIndows 8 to install 
> Ubuntu over it and it is good.

Does that thing have an old-fashioned spinning hard drive instead of an SSD?

In 2010 I got my first SSD-based MBP after my previous 2008 MBP, and just 
recently replaced that with a current 15“ rMBP 2.6 GHz quadcore i7, 16 GB RAM, 
1 TB SSD. This SSD does about 1 GByte/s throughput in both read and write.

Not really enough RAM? Does that Asus have 32 GB or what? And more than 1 TB 
internal storage? And regarding „computation power“: you can’t even saturate 
your CPU cores for long if your storage doesn’t deliver the data fast enough. 
Having an SSD or not is the biggest difference whatsover. And I don’t think 
that many other laptops already have PCIe SSDs, and SATA3 doesn’t cut it any 
more with modern SSDs.

Or to put it bluntly:
If your main dev machine is still running on spinning disks, especially 2.5“ 
laptop ones, your developer time must be really cheap.

Maik

P.S. For everyone who upgraded their machine with an aftermarket SSD: check 
system profiler if TRIM is enabled. If not, get Trim Enabler [1] that will 
solve that for you.

[1] http://www.groths.org/software/trimenabler/

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to