Live data from Hacker News

HoloJS – A framework for creating UWP applications using JavaScript and WebGL

github.com

21–25 of 25 posts

Re: HoloJS – A framework for creating UWP applications using JavaScript and WebGL

#21
post #20

Earlier quoted context omitted.

To be honest, I don't want a webapp. Webapps may have a good thirty second use case, but adter that, i want something thatnis with all my other programs that I can pin to a menu/quick launch bar, that runs in a different process space so that a bug in a different program doesn't take down your program, etc. I want the same UI/UX as a native app, and that's something tat webapps still fail terribly at.

I definitely agree (and prefer writing/using native apps), but i would say that uwp apps get all of the UX benefits of a native app (the js apps for UWP get access to all the same libraries as the .net/native apps; I don't know about default styling but I'm sure someone has a template). Also, UWP apps are full apps like any other windows app.

Totally. I'm writing an app myself using UWP, albeit in C#. I was addressing the wanting it to be a webapp part, not the UWP or written in javascript parts, which is a totally different issue.

Re: HoloJS – A framework for creating UWP applications using JavaScript and WebGL

#22
post #2

This seems like a lot of work. Couldn't Microsoft just support the WebVR API interface in Edge or some other type of AR extension into Edge? That is all I would want. Then I can just use ThreeJS or Babylon.js with it from a normal website, and then there is no need to ship custom desktop applications with embedded. I guess I do not want to ship applications if I don't have to.

To be honest, I don't want a webapp. Webapps may have a good thirty second use case, but adter that, i want something thatnis with all my other programs that I can pin to a menu/quick launch bar, that runs in a different process space so that a bug in a different program doesn't take down your program, etc. I want the same UI/UX as a native app, and that's something tat webapps still fail terribly at.

Those sound like an odd bunch of criteria. I'd go for a list more like:

1. Performance (either speed of opening if it's the kind of app you open and close a lot) or just responsiveness in use 2. Quality of user experience 3. Stability 4. Cost. 5. Features 6. Interoperability

At the moment across a range of app types it's roughly 50/50 between web apps and native apps and I occasionally switch alleigence.

Re: HoloJS – A framework for creating UWP applications using JavaScript and WebGL

#23

Interesting. With a little hackery, it should be fairly easy to get this working with PlayCanvas. I'm not sure why it needs to use a new element type though (canvas3D).

Canvas does not support all the 3D elements needed for spatial recognition and accessibility via 3D audio. I'm hoping to read through and see canvas3d support that feature.

What does Canvas have to do with audio? Web Audio has the necessary components to do spatialized audio. And spatial recognition is an input. Canvas is for output.

Re: HoloJS – A framework for creating UWP applications using JavaScript and WebGL

#24
post #13

Very similar to my work here: https://github.com/lwansbrough/HolographicJS that got no love on HN. :( But I'm really happy Microsoft has chosen to create something similar - I had hoped they would. Their implementation seems quite solid, I wonder if it supports libraries like Three.js yet. If anyone is wondering why you might use this, the reason is pretty simple. Before this, there was only two ways to build HoloLen…

> Very similar to my work here: https://github.com/lwansbrough/HolographicJS that got no love on HN. :(

Yeah, it's only open source if MS/Google/Facebook/Mozilla is doing it.

Re: HoloJS – A framework for creating UWP applications using JavaScript and WebGL

#25
post #22

Earlier quoted context omitted.

To be honest, I don't want a webapp. Webapps may have a good thirty second use case, but adter that, i want something thatnis with all my other programs that I can pin to a menu/quick launch bar, that runs in a different process space so that a bug in a different program doesn't take down your program, etc. I want the same UI/UX as a native app, and that's something tat webapps still fail terribly at.

Those sound like an odd bunch of criteria. I'd go for a list more like: 1. Performance (either speed of opening if it's the kind of app you open and close a lot) or just responsiveness in use 2. Quality of user experience 3. Stability 4. Cost. 5. Features 6. Interoperability At the moment across a range of app types it's roughly 50/50 between web apps and native apps and I occasionally switch alleigence.

Oh silly me for forgetting the markup rules once again. What were those arguments against WYSIWYG again?
Post reply on HN