←back to thread

133 points avan1 | 2 comments | | HN request time: 0.256s | source
Show context
osigurdson ◴[] No.45078470[source]
Sometimes I think we should go back to basics: pixels, data, latency / bandwidth. The web is an optimization problem in the sense that we want to render correct pixels at perceptual speed given latency and bandwidth constraints.

It should be more like: what pixels is the user about to see? What data is need to set the the pixels? What data is likely needed next and optimistically pre-fetch - something like that.

replies(3): >>45078683 #>>45078991 #>>45080169 #
timschmidt ◴[] No.45078991[source]
In https://github.com/timschmidt/alumina-ui I've been building for WASM using the egui toolkit which just accepts an HTML canvas the size of the browser and starts shouting WebGL at it.

I get to forget about HTML and Javascript, CSS, most of the complication of the browser and web, and just write an application in my favorite language which will run fast and deliver GL accelerated graphics to it's users.

I am really happy with WASM / WebGL for being abstractions which allows for this.

replies(2): >>45079828 #>>45079872 #
1. osigurdson ◴[] No.45079872[source]
This! Love it!
replies(1): >>45079948 #
2. timschmidt ◴[] No.45079948[source]
Thank you. There is still a lot of work left to get it controlling it's first machine. I am currently figuring out how best to build for all the mcu and board combinations I expect to support, and then wiring up motion control to the UI. Just got the node-graph interface for csgrs working and there's still a lot left to flesh it out fully. Advancing slowly :D

Please consider joining the Discord: https://discord.com/invite/cCHRjpkPhQ

I'm the only one in there at the moment. Bring friends! lol