126 karma · joined September 20, 2008
SF.
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.
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.
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.
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.
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.
Douglas Lanman, the researcher behind this technology work at Nvidia was hired a few months ago by Oculus VR.
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.
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.
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.
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?
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.
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...
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.
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
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 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.
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.)