Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×

Comment Re:Fahrenheit? WTHolyF? (Score 2, Insightful) 210

Yes, apparently it is too much to ask that people be correct these days.

The summary clearly states that 512GB of memory is 1000 times more than 512MB of memory, which is patently false. If you're making comparisons, you don't make absolute statements like this. You use qualifying words like "about 1000 times" or "approximately 1000 times" to let the reader know you do not mean to be precise.

 

Comment Fahrenheit? WTHolyF? (Score 1, Troll) 210

Why the hell are we talking about the Fahrenheit scale. And, while we're at it, memory of all kinds is always expressed in GiB, so a 512GB card is 1024 times as large as a 512MB card, not 1000 times.

It looks like a standard -25 to 85C extended commercial rating.

Comment What's the angle? (Score 1) 35

I can understand the interest in the existence of Eucalyptus itself (it's a more or less interface compatible implementation of a bunch of Amazon's heavily used 'cloud' services that you can run stuff on in house or at a non-Amazon 3rd party). Amazon's pricing is crazy aggressive; but sometimes you need to do things in house, want to do things in house, or want to go mixed-strategy(in-house/Amazon for overflow, spread across more than one 3rd party provider, etc, etc.) and in general it's not a good feeling to have a stack of important stuff dependent on a single vendor.

What I find much harder to understand is what HP gains from this, or what I, the hypothetical customer, as supposed to be willing to pay HP to put its name on here.

Is this just more HP flailing, or is there an angle I'm missing? Are there lots of potential customers who won't touch Amazon (perhaps because they have to keep stuff internal); but won't touch Eucalyptus without some giant company selling them a support agreement? If so, since Amazon is off the table, why would they care about Amazon API compatibility? Who is the target here, and why aren't they either DIYing it, paying Amazon's incredibly aggressive prices for the real thing, or using an architecturally different cloud/VM arrangement?

Comment Re:Why not all apps at once? (Score 5, Insightful) 133

Even if it were perfect, almost no ChromeOS devices have touchscreens and almost all Android devices do (especially if you count on the ones Google even slightly endorses, not the media-player-mystery-HDMI-dongle stuff). For applications that are basically hobbled by the touchscreen, a keyboard and mouse will be an improvement. For those that are enhanced by, or actively dependent on, it, that will be a bit of a mess no matter how perfect the runtime is.

Unless those proportions change fairly markedly, it probably makes sense for them to start with some popular, mouse and keyboard friendly, applications that don't lean on native ARM blobs much or at all.

Comment Re:Pricing? (Score 1) 47

Sorry, my phrasing was ambiguous: the rPi I/O is 'broken out' in the sense of 'breakout board', it's substantially accessible on reasonably friendly headers that you can connect to without tiny elven soldering fingers or oddball connectors; unlike the (otherwise cheap and quite tempting) 'buy an android mini-stick-thing/used phone with 3rd party firmware support' option, which gets you power, sometimes a screen, and a few peripherals for crazy cheap; but where you'll be lucky to find a handful of undocumented test points, much less any headers.

The chip the rPi is based on really isn't quite right for the job(but feel the price...) so eth isn't so hot; but I've never had any serious issues, assuming an acceptance of the speed limits.

Slashdot Top Deals

And it should be the law: If you use the word `paradigm' without knowing what the dictionary says it means, you go to jail. No exceptions. -- David Jones

Working...