nivloc

In-App Purchase

It's really easy! Seismic surveys are key to the oil & gas industry, and can be used for other resources as well. We use thumper trucks instead of waiting for earthquakes.

Benchmark applications are not GPUs.

Besides that, GFXBench 2.7 doesn't support ES 3.0 and that's what most of the comparisons with other current-gen GPUs have used.

That's what CCP did with the EVE-VR demo, and it makes sense in the context of a flight sim. It'll be interesting to see what developers come up with for FPSes.

http://community.eveonline.com/news/dev-blogs/eve-vr-an-expe...

They do: https://support.stripe.com/questions/can-i-authorize-a-charg...

Correct. Haswell is LGA 1150, SB/IB were LGA 1155.

There is another deposit in Nevada called Kings Valley that is in feasibility. It's about 300,000 tonnes LCE, and fairly likely to go into production.

If the Wyoming deposit it real (their numbers wouldn't float for a listed company and they're short on details), it's probably 10+ years away from production. Neat discovery, but very speculative.

http://www.westernlithium.com/project/ is the Kings Valley project.

No, it's really the economics of it. Lithium and other evaporite minerals are usually concentrated in ponds so the evaporation rate can play a part, but usually it's a matter of efficiently using the capital over the lifetime of the operation.

It's easy to drill more wells or build more ponds.

I work in the industry and, as luck would have it, am on a project near the facility in Nevada.

Local currencies are a mess of jurisdiction, but generally legitimate currency, or for the purposes of this document, 'real'.

Linden Dollars (along with WoW gold, EVE ISK), are owned by the respective developers. That database entry denoting your Titan isn't yours per se, you're just allowed to have it rendered as long as you abide by the terms of service.

They probably haven't filed anything, if they get a couple bites then they will.

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.

Previous discussion: http://news.ycombinator.com/item?id=4895372

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.

`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.

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.

Yeah, the good ol' inflector. There's actually more to it, it can use locales now and it's been cleaned up: http://davidcelis.com/blog/2012/07/31/edge-rails-a-multiling...

It's going to be a great release.

With apologies to Her Majesty, Canada has more progressive banking regulation.

It's a different way to price products - they charge per user. So, if your little startup starts growing, they bring in a bit of cash and have opportunities to up-sell with the other products in their line.

They fuzz the numbers displayed - everything internally uses the real upvote/downvote count. It's so bots can't figure out if they've been flagged or not.

Amazon and Steam work the same for me in Canada/Latin America - have to use a local card. That said, I've still been able to make some purchases without switching. I've long given trying to understand the nuances of it.

How does apple force you to go through the public store for everything, exactly?

Apple's maps are really good. Google's maps are much better, generally, though.

There are places where Apple has an advantage over Google, but Google has been pouring resources into Maps for a long time.

Garmin, TomTom, Navteq, etc. won't be nearly as good as Apple or Google because they aggregate sources.

They aren't unusable, and are better than if you rely on a dedicated GPS. But they can still be improved. Apple doesn't seem to be weighting proximity for search as effectively as Google (unsurprisingly).

Honestly, Apple is the new #2, but they've got a mountain ahead.

I'd say it was, or at least as ready as it could have been. Problem is that everyone is behind Google on Maps. They're on Mars, everyone else is playing with baking soda and vinegar at Cape Canaveral.

Apple would have to acquiesce to Google on a lot of fronts to get better maps features (that are a major improvement in many places), and get stuck working on something that could never compare in perpetuity. Launch or die, right?

That's pretty much what the entire article is about, no?

Maps are hard.

The original Google Maps was pretty bad. Mapquest beat it much of the time. There was one road in my hometown, and none in many countries.

Google devoted enormous resources to acquiring data (petabytes worth), processing it, correcting it, to give us the product we have today.

Even though Apple acquired some neat companies that made data look good, they obviously underestimated how much data was required to make it useful. No amount of QC could have prepared them, frankly.

The upside is that Google has been fairly closed with their map products. They're miles ahead of Apple, who will need every partner they can find to close the gap. Hopefully it will give the data providers a bit of leverage to get refinements back out so it can be used in endeavours other than showing where the nearest pizza joint is.