The problem here is all the OS features are discarded. Can't insert password from password manager because to do so the page would need to access to passwords. Can't use the user dictionary because to do so would be a privacy issue. Doesn't support CJK and other languages that require an input method editor. etc....
It also means a platform's features are not duplicated so your app's behavior sticks out as having a different experience from everything else the user does making it frustrating.
That said, if you want see an app in WebGL/WASM where the browser is rendering everything there's https://earth.google.com as a high end example. It has most of the issues just mentioned as well as the fact that nothing is selectable by default. Want to copy a name so you can paste it into your search engine of choice. NO! Want to right click on a foreign name to find out how to pronounce it? NO! etc....
This is a good experiment. What does it take to have a wasm powered corss platform architecture for apps. So far tauri had done something, but requires a humongous backend (system webview).
If we can reach this goal in under 1mb or 2, this is a massive improvement to the SoTA. Experiments such as these are what get is there. kudos.
Why did you write a layout and rendering engine to run on a browser, which is a layout and rendering engine already? As socalgal2 points out, you’re losing many important features.
It seems insanely...bad to me. I loaded the HN demo. I can literally see the rows of items loading as if I'm on dial-up.
I can't select any of the text on the homepage demo. In the comments page, text selection doesn't behave like I would expect, in too many ways to describe here.
I right click and can't do anything, unless I right click on an item. And then my only options are "Open", "Open in New Tab", and "Copy Link".
The scrolling on the page doesn't have the normal rebound that you get when you try to scroll past the extents of the page on a trackpad.
Pinch to zoom doesn't work.
Cool that it's handwritten and that you can hot reload and write it on a phone, but as an end user I would _hate_ if I was asked to use an application built on this.
The name seems very un-searchable and already overused (I found several other web Uniforms while testing searching for yours, which I didn't find). The demo seemed low framerate or something on Chrome Android, and apparently my main, Firefox Android, doesn't support WebGPU by default.
The problem here is all the OS features are discarded. Can't insert password from password manager because to do so the page would need to access to passwords. Can't use the user dictionary because to do so would be a privacy issue. Doesn't support CJK and other languages that require an input method editor. etc....
It also means a platform's features are not duplicated so your app's behavior sticks out as having a different experience from everything else the user does making it frustrating.
That said, if you want see an app in WebGL/WASM where the browser is rendering everything there's https://earth.google.com as a high end example. It has most of the issues just mentioned as well as the fact that nothing is selectable by default. Want to copy a name so you can paste it into your search engine of choice. NO! Want to right click on a foreign name to find out how to pronounce it? NO! etc....
This is a good experiment. What does it take to have a wasm powered corss platform architecture for apps. So far tauri had done something, but requires a humongous backend (system webview).
If we can reach this goal in under 1mb or 2, this is a massive improvement to the SoTA. Experiments such as these are what get is there. kudos.
Cool hack. But taking a step back:
Why did you write a layout and rendering engine to run on a browser, which is a layout and rendering engine already? As socalgal2 points out, you’re losing many important features.
I have been dreaming about this for ages, ditching the DOM and building everything in WASM for example. This is insanely great.
It seems insanely...bad to me. I loaded the HN demo. I can literally see the rows of items loading as if I'm on dial-up.
I can't select any of the text on the homepage demo. In the comments page, text selection doesn't behave like I would expect, in too many ways to describe here.
I right click and can't do anything, unless I right click on an item. And then my only options are "Open", "Open in New Tab", and "Copy Link".
The scrolling on the page doesn't have the normal rebound that you get when you try to scroll past the extents of the page on a trackpad.
Pinch to zoom doesn't work.
Cool that it's handwritten and that you can hot reload and write it on a phone, but as an end user I would _hate_ if I was asked to use an application built on this.
The name seems very un-searchable and already overused (I found several other web Uniforms while testing searching for yours, which I didn't find). The demo seemed low framerate or something on Chrome Android, and apparently my main, Firefox Android, doesn't support WebGPU by default.
That's exactly what companies want: truly closed-source website.
Surely you could ask Claude to decomp the WASM blob it sends you (lol).