I'm still (very regularly) using my 2013 Nexus 7 and my kid loves her 2011 IPad and they both work perfectly. Tablets age rather well; performance and display res have been more than good for several years, and they don't get dropped down the toilet/left in a bar as much as phones.
It would be much more useful to see data from Apple/Google on daily device usage...

and it wants its news back. Seriously I've used quad monitors (two portrait plus two landscape, all 1600x1200) since.. oh god I can't even remember but it's forever ago, way more than half a decade. It's awesome tho; text editing & ssh FTW on portrait, "everything else" (mostly web) on landscape.

My Comcast cable connection is fucking fast and regularly gets faster. I noticed 100Mbps downstream a couple of days ago - good thing I purchased a router with gig-e - when I'd tested it a few months earlier I was clamped at 60Mbps which was still in the "doesn't-suck" category. With that kind of performance (and excellent reliability) I just can't hate them.

Kickstarter shitcanned it in the last days!
As The google doc puts it (http://bit.do/ifs)

SCIENCE: 1 SCAMMERS: 0
Thankyou Slashdot, your informed skepticism (and humor) was a great help.

Did he say if he'd seen a working device, or confirm anything other than that it was him that appears on the KS page? Verifiable details from the creators are exceedingly thin on the ground. If you'd like to screencap your email and post a link to the image, that would be great. Thanks.

Wotao popped up (long ago) on the KS comments thread and basically said "I'm an investor but I can't really talk about anything". He also replied to direct emails to his uni email, confirming his involvement. One person who contacted him, reported him (not seen the email) as admitting he's not yet seen a working device.

I think he probably got pulled in as an investor (and to add credibility) and probably now rues the day he said yes. We'll see. Either way, at this point Google searches won't forget his involvement.

The thing also needs (most of its) power to run a Bluetooth receiver (+accelerometer), which typically uses 10-15ma @ 2V (=20-30mw) when in _receive_ mode. The duty cycle is short but waking up every 5 seconds to see if the tag is being pinged isn't typically something you'd power with leprechauns (unless they were made of lithium).

err... whose claims are unverifiable?

Wetag's? Sure, they're pretty sketchy. Practically no hard info except two wack pseudo-science documents and some nice photoshop work. No pics, no demo, no nothing (so far).

Mine? Errr... well, there's a ton of links to source material throughout, there's links to other people who think the same way (and did the math also), there's facts, figures, references, etc.
If you didn't click any of the links, do any Google searches, look at the iFind site or pay attention in math or physics class in highschool, then.. yes I suppose you find them unverifiable. Tell you what, I promise, cross my heart, it's all true. Does that work?

What you say is not plausible; how do you think any radio-activated device receives the "I lost you" signal? In practice it's far from "dormant 24/7"; it's completely deaf to any signal until it turns on its high gain radio which takes typically 10-15ma. The tag must be constantly waking up and consuming power (even if, as with BTLE, it's possible to set the gaps to e.g. 5-10seconds and the "on" time is very short).

Without trying to be unduly rude, you're 25% informed yet 75% confident in your knowledge, which I suspect comprises large portion of backers of this project.

Either do a little research (e.g. look up the math and/or read the datasheets for BTLE chips - all provided in the RTFA's google doc) or... go order a pack of 10 iFinds. . :-)

I did, see Google doc. So did others (better than me). Results posted in doc.

You say: "no idea, did not check it".

Your ideas are intriguing to me and I wish to subscribe to your newsletter.

It's not (just) for speed, if at all, it's BECAUSE YOU HAVE PORTABILITY WITH iOS (and other platforms)
If you use Java you're hosed. If you use regular C you can compile on both platforms, with a shim to interface to either iOS or Android as required.
The GLES code can easily be compatible. The UI stuff not so much but (high end) games generally implement their own UI in GL for specifically this reason.

It's not pretty but it's what most pro game developers have been doing since at least 2010, and it's a _hell_ of a lot better than having to totally rewrite your Java app in ObjectiveC or vice versa.

The extra performance is sometimes useful in some places but it's almost always about compatibility with iOS or (more rarely) with existing C libraries e.g. video encoding or whatever.

...in which case a Google Bus is going to appear out of nowhere and park between you and the moon, completely blocking your view.

You people are weird, I've been on 4x 1920x1200 monitors for years now (2x portrait, 2x landscape; It's fucking marvellous). I have a fifth but no desk space (or interest in turning head to view) so it's a spare.
This cost... I dunno, peanuts, even a few years back.
Super strongly recommend at _least_ a pair of portrait monitors plus at least one landscape. It's practically impossible to go back.

...you say that like that's a bad thing? This is Vegas!
Just make sure you have some potential customers with you and it's your card behind the bar (or in the stripper's hand, etc)