Hacker News new | ask | show | jobs
by boost_ 3902 days ago
no they haven't, its still narrow as hell.

nice one hackernews, downvoting the most important question in this thread...

i guess this is full of MS fanboys that don't mind being scammed out of 3k dollars..

4 comments

I'm not sure the narrow field of vision is that important for a dev. kit. The goal is to let people work out how best to produce apps for this kind of interface.

If they can't sort it for consumer release, that's a much bigger issue of course. My guess (and it's just that) would be that they'll be trying to improve field of vision for the consumer release, as from the reviews I read it was the one major negative people cited.

The reason the narrow FOV is important is because right now, the FOV is so small that you can't see a person's hands and face simultaneously at a comfortable conversation distance. There's a huge number of applications where you won't know the suitability, or even be able to visualize/test if it'll work well w/o knowing a target FOV for a consumer revision.
well i would be more inclined to agree if they didn't announce their product with full view (at least 120ยบ) capability.

i mean, we all saw the videos from the announcement, and the "live" demos. and that was just pure lies no matter how you want to paint them.

also even if they didn't lie, don't we need the dev kit to have the same full capabilities as the final product? would you acquire an early dev kit for some new console, only to find out that it has less ram, gpu and/or cpu than the final product? how can we actually test it fully?

> would you acquire an early dev kit for some new console, only to find out that it has less ram, gpu and/or cpu than the final product? how can we actually test it fully?

I guess for MS is important to have a good portfolio of apps before the product is launched to the public. This class of unpolished dev kits are not unheard in MS world, Do you remember when the dev kits for the XBox were Apple Power Macs?

they were, but the hardware was the same was it not?
Not really, just the processor was the same, but it was the best they could do in a short time.
oh sure, in an ideal world the dev kit would have all the capabilities of the live consumer device.

But when you're developing a new category of device, that's not always possible.

For a very related example, look at the Oculus Rift approach to VR. they've been iterating on developer kits slowly improving the hardware while letting people feel out how to use that class of device.

Ultimately it'll be down to individual dev. houses whether it makes sense for them to invest at this stage, or wait till it's closer to consumer launch

> only to find out that it has less ram, gpu and/or cpu than the final product?

That doesn't sound like a problem. Now if it turns out it is less powerful than the final product, that would be a serious issue.

'narrow as hell' is your assessment based on what?

Is there some industry standard minimum field of view for AR glasses that this fails to meet? Have the people who tested HoloLens out who complained about the field of view being narrower than they would like said that it made the technology useless, or just that it limited it? Seems like you think it's a showstopper, I'd be interested to know why.

It is an annoying trend and I have seen it in similar discussions about Google and/or Apple. It almost feels like tribes within HN.

As for the topic, they didn't specified the field of view, How could you tell they didn't fix it?

"nice one hackernews, downvoting the most important question in this thread... " We're less than an hour in and the OP question is the top comment... I'm not sure what's so wrong to you about the HN community here?
when i replied more than 30min ago there was already 11 replies and the one i replied to was on the bottom in grey color..

and now they down vote me.. lol whatever guys go crazy!