mkeblx

https://github.com/WebKit/WebKit/commit/7ad679f071434da45d45...

Chrome is 100us: https://chromium-review.googlesource.com/c/chromium/src/+/85...

Michael Abrash has a good overview of some AR challenges here, also discusses why that doesn't work: http://blogs.valvesoftware.com/abrash/why-you-wont-see-hard-...

Easier said then done, just an LCD won't work for darkening. http://blogs.valvesoftware.com/abrash/why-you-wont-see-hard-...

Yes, they could have done the same thing with an Android WebView. But the Chrome team is actively working on implementing WebVR (which also want to support many AR use cases) so they already have a native (= higher performance, lower latency, etc) implementation to modify with some smaller changes to use the ARCore API.

There's actually a couple of Chromium-based browsers on there, Samsung Internet for GearVR which has been out and quite popular for 360 video watching (Youtube.. etc.), and Oculus just came out with theirs.

Yes ideally they'd be able to be composited together at the depth buffer level. But even separate I can see a ton of devs making some very cool more UI-centric applications just with CSS mode. Can't wait to see the webdev community understand what can be done with VR and the webstack in 2016.

Really looking forward to the the stereo rendering of non-WebGL content, HTML+CSS, which the Mozilla team is working on. More challenging path to figuring out but will open a lot of possibilities.

On the Gear VR (dev kit, 2014) there was a 2.5k screen at a smooth 60fps. The consumer Gear VR coming out this fall will likely have a 2.5k screen but we'll likely see 4k screens on mobile headsets in 2016. 120fps will be a nice improvement but not required, with the Rift CV1 at 90fps and sufficient for presence. So we're talking a 2-4x difference.

The graphics card issue is not that relevant, Gear VR with a mobile GPU is showing that it's not really about some arbitrary graphical fidelity bar. Yes, some of the highest fidelity cool stuff will be on PC but multiple cards won't be required. Both the Vive and CV1 will run great on one high end card, and by the time they upgrade to ~4k/120Hz... they'll still require just 1 card.

I don't disagree completely but underlying the growing excitement was for the past 18 months (since Abrash, etc. started talking about VR and presence as something incredible, game-changing and deliverable in around 2 years) was in large part based on the pace things were advancing and what was in store for a consumer release.

Plus many of his specific points are just so temporary in nature, like resolution complaints, heaviness/comfort, tethered, form factor, etc. These will be solved in just the next few years.

Michael Abrash of Valve now at Oculus giving a basic description: https://youtu.be/G-2dQoeqVVo?t=3m14s

It's parts of your lower brain aligning to convince you you're in a virtual world, and while it is a spectrum you really need a high end headset to experience it. Abrash himself mainly dismissed VR's potential prior to experiencing it.

Jeff is speaking from a position of not having tried the good stuff that delivers a sense of 'presence' in the virtual world. That is the game changer, the thing that is making people believe something special is on the way. When he says "I have experienced modern VR. A lot. I've tried both the Oculus DK1, the Oculus DK2." he's just flatly wrong, he hasn't. Those headsets at not modern VR and using them as the reference for where VR is at is pretty crazy.

But you'll get a chance to try to presence-inducing stuff in the next ~6 months with the consumer release of the Vive and Oculus CV1.

It's less about the mobile as in using-while-walking-around than the ability to have with you wherever you're at and not tied down to the context of sitting in front of a PC. VR is for everywhere: the couch, the kitchen table, in class, at work, social gathering where you can easily share it, etc. The tether of the current dev kits actually takes away from presence.

While there are hassles of VR with Android that were only solved by making deep changes to Android, the hassles of PC are greater. And this is a phone accessory that is specifically not designed for changing hardware and software: it only works with the Note 4 running a custom optimized version of Android. But they do agree with you that a dedicated unit is what they want to do as well which is why this is not their own consumer unit.

It can and will in relatively short order: https://www.youtube.com/watch?v=deI1IzbveEQ

Douglas Lanman, the researcher behind this technology work at Nvidia was hired a few months ago by Oculus VR.

That's why you have to go with a microSD card adapter that doesn't protrude at all. http://theniftyminidrive.com/

Yes, while the current dev kit would have a hard time being a consumer success for easy to point out reasons, knowing that the consumer version will be qualitatively 10x-100x better (~4x resolution, content availability & quality, better form factor, positional tracking, low persistence, and the real key: 'presence'-inducing) lets you understand how many of the potential things that would stop VR from going big very soon will basically be non-factors.

I'm hopeful 1440p will be fairly text friendly and prove good-enough for programming, etc. but even if not quite there, that merely means that threshold will be broken a year or two down the line.

This kind of hits the nail on the head. An idea is in many ways the context by which you judge a startup team in terms of a core commitment to a common goal, as shown by working on it together for a period of time (more than a week, etc.). It defines what 'team' means. Without that, what do you have? Credentials.

Of course by disaster I meant just relative to other classes, with a much higher amount of team splits/zombies in such a short period, which seemed predictable. Most startups don't work out, that's expected, but the stage was weighed for things not to work out in re: the startup itself and the friendships involved. Who knows, perhaps you and your friends, with a shared, good idea would have done great in w13, having the right context to build upon where you were at. I know of other teams who were extremely frustrated that something they've dreamed about, Demo Day, turn into something to dread and the quite painfully choosing to give up on the whole endeavor whatever the high personal costs (not necessarily wrongly).

One of the best things about pg's essay was the core message to entrepreneurs that a good startup idea requires not a pressure cooker atmosphere to come up with an 'idea' but the natural space in which you notice a problem that can be solved. It's the starting point, not something that can be tacked on later like the noidea concept would suggest.

Perhaps the whole idea of the noidea app set the stage for the disaster that was S12. Even though only one noidea app was accepted strictly speaking perhaps both a signal sent that the 'idea bar' was lowered and and a lowering of standards. This seems to me to hold a lot of explanatory power, much more so than the idea that multiplying 66 by 1.27 would be the key thing in turning something that works into something unmanageable.

I read the post S12 (post noidea) essay (http://www.paulgraham.com/startupideas.html) as a (if unacknowledged) reaction of someone trying to understand and elucidate why ideas are actually very important (going against the common refrain that 'execution' is all that matters) after having recently seen poor ideas get by a selective process.

Interesting that however fast the startup world runs there are often ideas that are sat upon for years that still remain viable, without direct competitors coming on the market (and the idea still being one that is good). I bet it's a fairly common story of "I've been thinking about this for years and STILL no one has done it. Let's do this."

From the post: "the guy said that he liked to play hoops. That single sentence lost him the job" - Max Levchin

I know culture fit is critical but where is the line between between not a fit and just having a hobby not shared by the rest of the team?

Simple. Do some monte carlo comparisons between a large number of generated functions, based on various heuristics like number of instructions. So quickly get rid of explicit mapping of tests, especially if used larger. Add some genetic algorithms and a little more AI stuff ;)

One interesting thing though with auto-generated code based on specific test code is that when the test fails at some point the process just has to be repeated, potentially being done automatically.

My first instinct was to look under the hood for some sprites I could use for a map based game. No luck, all the cool building/characters seem embedded in the the actual tiles.

Is there any way Google would try to make an actual game out of this? I know there are other successful online 8-bit-ish RPGs that use the Google Maps as a base...

Talking about FreshBooks: "As an aside, they mention that "we didn’t have our first paying customers until month 2." How do you think they felt before then? Or even in the six months after?"

I don't get it. I mean getting a customer in the first month would be ideal but having revenue in month 2 doesn't sound all that torturous to me. That one of the fastest examples of revenue traction I've ever heard.

If he was trying to make the valid point that many startups that on the surface appeared to have overnight success were in fact trucking away for years filled with uncertainty of getting traction it was unmade by the examples presented.

Madison, WI - (REMOTE possible) Circuit - http://circuitapp.co

Circuit is a collaborative webapp for designing and building electronic projects aimed at the exploding Maker/hobbyist market. We're going to disrupt hardware with a tool that makes things 10x easier & faster. Launching Q1 2012.

We need a passionate all-around programmer, experienced with creating advanced frontend interfaces as well as backend systems. Mainly would be doing a large amount of challenging HTML5, Javascript, and using PHP (Cake) & MySQL on the backend. Big bonus points if you have graphics programming experience and hardware background: microcontrollers, designing PCBs, tearing things apart, and familiarity with the Maker movement.

Interested, questions? jobs@circuitapp.co

Is there any vcs that would be better than any other when it comes to a serious EMI issue? And, who wraps an ethernet cable around a switch mode power supply brick?

Madison, WI - (REMOTE possible) Circuit - http://circuitapp.co

Github for hardware. Circuit is a social tool for designing and building electronic projects aimed at the exploding Maker/hobbyist market. We're going to disrupt hardware with a tool that makes things 10x easier & faster. Launching Q1 2012.

We are looking for a passionate all-around programmer, experienced with creating advanced frontend interfaces as well as backend systems. Mainly would be doing a large amount of challenging HTML5, Javascript, and using PHP (Cake) & MySQL on the backend. Big bonus points if you have graphics programming experience and hardware background: microcontrollers, designing PCBs, tearing things apart, and familiarity with the Maker movement.

Interested, questions? jobs@circuitapp.co

It's a basic economic principle that if supply decreases with the demand staying the same the price will go up, and a sudden, unexpected decrease in supply will lead to activity of buyers to look elsewhere to meet that supply. Basically, what's happening is exactly what would be expected, but the reporting has a breathless tone.

It will be interesting though to see what effect a >50% supply decrease has on prices and the market once things com e to equilibrium when the timeline of the supply coming back is known.

A non-square grid would itself not be an issue but if you want to do multiple LED strings as would be needed for a 10x50 grid the code might need to be modified to have multiple data outputs for each string. You should be able serially connect the strings but at some number you will have issues with the data/power wires, and may not get your desired refresh rate.

Why 36 hours? For the 24-hour hackathons I usually stay up the whole time but 36 plus the surrounding time might be pushing it. I'll try it though :)

I see that the tickets are limited in numbers based on what they bring to the table: dev, design, biz. What was the thinking behind doing it this way? The page mentions that it was to make sure to get enough devs, I don't recall that being a problem at the hackathons I've been to.

(On details page say typo: says that have over $2,00 worth of prizes.)

I've seen variants of this article a number of times. Is it really many decades from here already getting below 20nm feature sizes with Si?