What is troubling about AR/MR which I feel a lot of people overlook is the limited FOV. From the demo videos shown by Magic Leap (and Hololens) on YouTube it feels as if the entire FOV is available, which is barely the case - the Hololens has an FOV of 120x120 and Magic Leap is said to have a lower angle than that. Verge covered Hololens and they mention [1] the FOV as a limitation.

1: https://youtu.be/4p0BDw4VHNo?t=3m

120x120°? That would be wider than VR headsets!

Unfortunately Hololens FOV is more like 30×20°. Other AR players are mostly in the same ballpark at the moment. The good thing is that this gives very high pixel density. The other thing is that you don't see the edges unless the 3D render is cut off, so it may not feel as tunnelled as in VR.

Yes, that's the ugly truth. And their PR departments do their best to hide this almost deal-breaking fact. The current experience is underwhelming (limited FOV) in comparision to the faked PR demonstration videos.

Hey, The CSS in markup is only for the TodoMVC demo. It contains styling of the placeholder psuedo selector, and inline styling of a link to override the default style of a link.

The other 3 demos do not have CSS.

This is the number 11 from the clock

    <div style="position: absolute; display: block; visibility: inherit; margin: 0px; padding: 0px; backface-visibility: hidden; box-sizing: border-box; transform-style: preserve-3d; overflow: hidden; outline: none; border: none; font-size: 28.44px; font-family: sans-serif; color: black; text-decoration: none; text-align: left; direction: ltr; line-height: 1.4em; white-space: nowrap; -webkit-font-smoothing: antialiased; cursor: default; transform: translate(50.834px, 12.5738px); -webkit-user-select: none; height: 39.816px; width: 32px;">11</div>

Nope, no css here.

Oops I thought you meant within the HTML file itself.

CSS means "Cascading Stylesheets" Using the framework the developer does not have write CSS. What you pointed out is the "style" attribute. Obviously the engine has to use the "style" attribute to communicate to the browser about the positions and remaining computed style properties.

Your post said "What if we ditched CSS?" with zero other context.

The links do use CSS, and there are non css options available in most rendering engines for such things, e.g. canvas/svg.

Personally I see no advantage to using things like lay.js in the top linked example over SVG, and further feel that a lot of the hate driven towards CSS stems from misunderstanding or misuse. Not that it is perfect, far from it, but to proxy it behind another language can only ever add limitations.

Compass/SASS solve most of my shallow verbosity based gripes tbh.

Sweet work on the UI!

And the code y'all write: The Bro Code

I didn't expect any responses and a bunch of down votes... this made it worth the 30 seconds of doing a stupid Ask HN

server in javascript, 3d engine in javascript, brain in javascript, next kidneys in javascript

Now you can add markdown resume on your markdown resume... How cool is that?

Haha I'll have to do that soon...

In the meantime, I actually am looking for a job, see https://news.ycombinator.com/item?id=7833969 for details :-)

</shamelessplug>

I stopped reading when this happened: "It effectively skips the browsers rendering engine and instead uses its own more efficient rendering engine based on WebGL"

Good thing you stopped... as that is entirely inaccurate :D

fwiw I am a famo.us employee