I have been wearing a Fitbit for over a year, my wife for 6 months. I can't imagine life without it now. The Big advantage is it keeps me honest. I aim to always do 10,000 steps a day, 100,000 steps a week, and I can see if I am short at any time. It is easy to convince yourself you have done more walking than you really have.
http://getforge.com/ - a superfast static web hosting service. Some clever tech, a bunch of users, very little support and brings in money. It's a nice project, but its success is more important than our owning it. Someone else will be able to do more with it than us :)
The video latency is low enough that you don't notice. We tried with moving our hand in front of it, it feels weird too see yourself real-time!
The rotations of the cameras are a bit too slow though, but mainly because of our setup, so this can be a lot better. Our custom protocol couldn't really handle dropped packets, so if we filled the sender's or receiver's buffers, the servos would start to spasm. To counter that we just didn't send head position as often as we could.
Of course, by fixing that you still get the round-trip time of turning your head -> moving the cameras -> getting updated image back. But we think it's feasible.
Any reason you didn't just transmit 3 normal RC PWM channels? You could do all the custom circuitry on the ground. Plug the Oculus into a microprocessor, then output to the trainer port of an RC transmitter or perhaps use one of the standard RC transmitter modules like JR or Futaba.
It's not exactly a "university research" project. We're just students. It's a course where there is much focus on combining the expertise of different studies and focus on teamwork. So it's more about the process and widening your engineering focus.
And the video is made for showoff, the project in itself is about the applications of a system like this in a specific industry.
You're right, sorry - it was the supercilious tone I objected to. In fact $() returns the first element and clicks it. Because it's in a setInterval, it continues to click the first <a> it finds every 100ms. Did you try it?
I'm with sleepyhead - what exactly is wrong with Safari? I'm a web developer and I use Safari almost exclusively. Hardware-accelerated (on OSX, anyway), good performance, accurate rendering, no privacy intrusions.
It sounds like you are coming from a web development direction, and are frustrated that Safari doesn't support the web APIs that you care about. As a software engineer, I can sympathize with that.
But as a user, I prefer Safari, because I find that it prioritizes user experience over fidelity to the web page. Examples:
1. Safari was one of the first browsers to ship with a popup blocker
2. Safari defaults to blocking third party cookies
3. Safari Reader cuts out distracting ads and other crap, improving nearly every article. I click it whenever I can.
4. Safari Power Saver defeats annoying animations while saving battery life
I love that Apple is able to deliver features like these, because their fortunes are not tied to advertising.
It's true that some websites don't work well in Safari, especially HTML5 games. For pages where I want to see that stuff in action, I'll switch to Chrome. But frankly, most web pages are made more usable by disabling newer features. Chrome then becomes a poor man's opt-in.
Scroll latency has nothing to do with performance. You can achieve low scroll latency by doing scrolling and composition on a worker thread - which, IIRC, is more or less what OS X and iOS do, and is something Safari can take advantage of freely because it's not portable.
If memory serves, recent builds of Firefox (on the non-release channels) are actually starting to roll out OMTC (off main thread compositing) which delivers the same sort of 'performance' you like about Safari, while keeping the perks of Firefox having a faster parser, faster JS runtime, and modern feature set.
You are generally correct that latency is important, though. I don't know if the Chrome dev team prioritizes it much, but Mozilla recently started putting more effort into measuring and reducing latency in various parts of the browser (inattention had let latencies get pretty bad in some places.)
Safari's fortunes aren't tied to advertising because Apple already extracted a payment for every user that runs Safari. They're free to do those things like disable cookies and bundle an ad blocker because they don't have to consider the desires of content creators or generate a revenue stream via their browser. It's the same set of tactics Microsoft was free to use with IE. It's impossible for Firefox or Chrome to offer similar features without directly undermining their revenue sources.
Scroll latency has a lot to do with "perceived performance" and that's the only measure a user cares for - Chrome might be 1000x faster for SunSpider / whatnot benchmark but if it stutters and stalls when scrolling a page, users will consider it slower.
Yes, they'd notice that. But how often does that scenario (running Unreal Engine 4 under asm.js) happen, would you say, on a day to day basis? Compared with trying to scroll a loading webpage, I mean. We're probably talking orders of magnitude difference, I suspect.
I use Safari as my main browser for the reasons you mention, but it is slower. It just feels like a cumbersome dinosaur compared to FF or Chrome. And the navigating back flow is less than desirable. I find myself navigating too often to a blank page, or it just seems like Safari doesn't know what to do.
Basically, it does everything great except for the actual browsing part.
The issue is the example being set. Trappy is definitely one of the best, but his videos don't demonstrate his hours of experience, or safety considerations, to a novice pilot. The affordability of the machine plus some examples of fancy flying are sure to put dangerous machines in the hands of idiots, and that's best avoided. Remember - these things fly out of the box with no training.
Trappy also has access to many more multicopter spares than the rest of us. This may have something to do with his reckless flying!
> Render it server side, cache it, and fire it to my browser as fast as possible.
Precompiling static HTML is a strict sub-problem of the problem most people in this comment thread are referring to, which is development incentives and SEO characteristics for web pages that have non-trivial amounts of dynamic content.