Hacker News new | past | comments | ask | show | jobs | submit | more nivloc's comments login

It's the same reason natural cryolite isn't used - it's not economically viable. Lots of countries grow all the agricultural products. Aluminum isn't hard, just potentially more expensive.

> While I'm nit-picking...

Me too, Pinjarra is where the refinery for the largest producing bauxite mine is. And the refinery operates today because of cheap coal in Australia.

As is the case with many industrial minerals, it's often far cheaper to ship raw ore or concentrates to smelters built where electricity is cheap. Aluminum is no exception, and electricity cost is the reason there is a refinery in Iceland, despite being far from any bauxite mines.

The story really isn't that no country can't make a can of Coke, but why they don't. It's a fascinating story, unfortunately mostly told through feasibility spreadsheets.

I'm in the industry and it's not hard to think of all the steps ranging hundreds of millions of years to put an apple on my desk (there's volcanoes and inland seas! Dinosaurs if you stretch your mind!). This is a good summary. If he got any deeper, it'd be a book.


Lots of countries grow all the agricultural products

Who grows cinnamon, vanilla, coca, and kola? How many countries grow all four, because I doubt it's "lots". Do they also have some form of sugar and aluminium industries? (or steel/tin industries for different kinds of cans, or glass industry for bottles (with something for caps)?)

Besides, saying "oh, but countries could, they just don't" is having your cake and eating it too - the fact that countries don't because it's massively uneconomical means that yes, it does take multiple countries to produce a can.

It's a bit like saying "it takes a superpower to land men on the moon". Oh, sure, you could say "no it doesn't - throw enough private enterprise together and get someone there", but the point remains, no-one will - it still takes a superpower to land men on the moon.



This sounds like a PR stunt.

Un-prefixed declarations are everywhere. They're part of every framework, and what every developer tries first. Then comes -webkit, -o, -moz. IE hacks are far more widespread. filter?

I've been looking for sites without un-prefixed declarations for an hour and come up short. If there is any merit to this, I'd love to hear it.


I was able to gather the following links which may be interesting:

* IRC log of W3's meeting, where Mozilla, Opera, and Microsoft bring up the possibility of being forced to support -webkit prefixes: http://lists.w3.org/Archives/Public/www-style/2012Feb/0313.h...

* Article on Opera and -webkit prefix adoption: http://www.netmagazine.com/news/opera-confirms-webkit-prefix...

* Mozilla's analysis of -webkit usage on the web: https://bugzilla.mozilla.org/show_bug.cgi?id=708406 There's a lot of data there. Raw data is here: https://bug708406.bugzilla.mozilla.org/attachment.cgi?id=601... . Some processed data in a spreadsheet: https://bugzilla.mozilla.org/attachment.cgi?id=599084 . You may want to view others as well.

I haven't personally looked for sites that do this, but I use Firefox and have a Windows Phone, and in both cases I have found that I've ran into sites that were either Chrome only or simply looked terrible in my browser, not because of technical limitations, but because the developers had really only tested on Chrome. In some cases, I've ended up spoofing Chrome's UA in Firefox and found that sites still worked.


`border-radius` has been usable for about a year on everything except IE. `-webkit-border-radius` has little reason to exist, and is only around for token backwards compatibility.


People put it in there to keep the vampires at bay.


Cached from when it last crawled the page.


Benchmarks don't mean much until it's released, if ever. But I was playing around with it, and it's hard not to get excited about performance!

      |  mem | time |
  p1  | -24% |  -3% |
  p2  |  -8% | -12% |
  p3  | -31% | -12% |
  avg | -21% |  -9% |
(over 1.9.3)

Those are a couple workers I fired up for an hour. p2 relies on a C library, which might account for the smaller drop in memory usage. CPU needs investigation.

The numbers are kinda useless, but look good anyway.


> The origins of the fighter are equally murky, although superficial similarities to the U.S. F-22 and F-35 have fueled speculation in the West that Beijing based the J-31′s design on blueprints reportedly stolen from the servers of at least six American aerospace subcontractors in 2009.


Serviceability has nothing to do with reliability, for one.

They're designed to not be serviced by anyone - not customers, not retail staff. So, they have better quality parts that reduce return rates, and get replaced by new or refurbished units if they are lemons. Nothing wrong with the advances of mass production.


I'm surprised at the swooning over the form factor, not just from Gruber but the rest of the press, including big-fingered die-hards like Darymple.

We've been deploying tablets in the field since the Panasonic days. iPad replaced them, but not before we tried every alternative as they've arrived. When IPad hit we went 100% web-based.

(bit of background: after getting on the tablet train, we buy anything requested, support it 100%, and let users decide what works. ≈93% iPad, 7% trying out Nexus 7 today, 5 requests for Nexus 10 FWIW)

Playbook, Xoom, TouchPad, Nexus 7 and more were duds. Big complaint was "too small", browser performance (and bugs) came next. Build quality was so bad pretty much all were far more expensive than IPads anyway. I've got 3 dead Nexus 7s on my desk and it seems like they just came out.

If they've built a "perfect size" tablet with a good browser and pro-sumer build quality, well, 20% lower acquisition cost would make me happy. But happy folks in the field is better, and that's where we stand to see a shift.

Edit: Surprised everyone is so ready to ditch the 10" for 8"


Multiple remotes are easy. Three lines in the config to push to Github and Bitbucket. Which is great if you rely on either service. It's everything else - hooks, wiki, issues, etc. - that get overlooked.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: