Live data from Hacker News

Coding Horror: The State of Solid State Hard Drives

codinghorror.com

61–70 of 123 posts

Re: Coding Horror: The State of Solid State Hard Drives

#63

Earlier quoted context omitted.

The term "price gouge" is counterproductively pejorative. Being able to get it for some price is an improvement over not being able to get it at all, which, as you point out, is the alternative.

Ok, so what idiom should I use instead? I can't think of anything. Is this the market-economics version of political correctness?

The phrase you're looking for is "market clearing price" or just "market price".

See also Obama's elementary explanation of why lowering gas taxes doesn't lower gas prices when gas is in limited supply: the market clearing price is still the price at which the amount of gas that people want at that price equals the supply of gas. Setting the price lower than this will result in shortages. It doesn't matter whether gas taxes go down.

"Price-gouging" really is a terrible phrase for what you do in a supply-bound market. The people who raised prices have drives if you want one, and if nobody wants one, they lose their bet - have unsold inventory. The people who set lower prices sold out their inventory, but now they don't have drives if you want one, which isn't exactly a favor to you either. There are four methods of allocating resources and the method that our hunter-gatherer brains don't understand is market prices, so people think it is "unfair".

Re: Coding Horror: The State of Solid State Hard Drives

#64
post #34

Earlier quoted context omitted.

Just say the price went up due to unexpectedly high demand. It's hardly "gouging" you if the only way people can keep it in stock is to raise the price.

Just say the price went up due to unexpectedly high demand. I did say that. The issue is that I need 2 names: a name for the stores charging $450 (and are out of stock) and another name for the stores charging $600+. I chose "gouging" and "non-gouging". Concise, and everyone who read it understood what I meant to say. I'm not seeing any real alternatives being offered, except to replace clear, concise, universally un…

> I chose "gouging" and "non-gouging".

Why the nice name for a supplier who doesn't, you know, supply?

Discount camera stores are infamous for advertising things at great prices to get you in the store but being out of stock. It's a crappy way to do biz and should have a crappy name; "non-gouging" doesn't qualify.

Re: Coding Horror: The State of Solid State Hard Drives

#65

Earlier quoted context omitted.

what idiom should I use Others are replying, but I don't know that there's any idiom needed. Raising the price to whatever people willingly pay is just being a merchant. Is this the market-economics version of political correctness? I don't think it is. Political correctness applies when people feel they can't plainly say something that's true. In this case, using "price gouging" adds nothing to the statement that pr…

using "price gouging" adds nothing to the statement that prices are high except a sense of outrage Of course it does. It says: 1. the subject is a retail product with a standard price , as opposed to a market product where the price is determined by bids and asks. 2. the price is temporarily higher than the standard price due to some sort of unforeseen disruption . 3. the price will return to the standard price when…

Not to get into a prescriptivism debate but "Price gouging" has a specific meaning, not just "charging a lot of money":

> Price gouging is a term for a seller pricing much higher than is considered reasonable or fair.

or

> pricing above the market price when no alternative retailer is available

Re: Coding Horror: The State of Solid State Hard Drives

#66

If you'd like to see exactly how a macbook pro with an Intel X25-M feels like, I made a video to give you an idea: http://vimeo.com/7057850

I've never seen Aperture open so fast ... that was hot.

Yeah, that's a huge deal.

I'm moving to a workflow where I import to the SSD, do my work, then immediately move the raws to an external drive to save space.

Re: Coding Horror: The State of Solid State Hard Drives

#69
post #3

Linus' recommendation to buy the Intel X25-M still stands, because they have the fastest small-block random I/O performance. Why would you buy an SSD only to do large sequential transfers with it? Just use a 1.5TB HDD to store your media files.

Why would you buy an SSD only to do large sequential transfers with it?

Visual FX, video transcoding etc. Rendering times can often be disk-bound, and eat up a lot of time. It becomes aggravating once you start editing HD video, even on a quad-core. For that, the Crucial drive mentioned by Jeff is a win because of the price - the lower random-access performance compared to the Intel drive is not that big of an issue for this application, and even with that limitation it'll smoke my existing system drive too.

Re: Coding Horror: The State of Solid State Hard Drives

#70

Earlier quoted context omitted.

I've never seen Aperture open so fast ... that was hot.

Yeah, that's a huge deal. I'm moving to a workflow where I import to the SSD, do my work, then immediately move the raws to an external drive to save space.

This way TRIM would be useful because you're deleting data a lot? Do you cope with that by running linux/win7 aside or do you use Disk Utility to 'free empty space' once in a while?
Post reply on HN