alt Hacker NewsI like this statement:
> The web browser is very, very, very powerful software for applications, and the cost of accessing that power is going down seemingly every day.
It's wild how much easier it is to build things that harness web technology these days. I'm building features on top of three.js and offline storage and SSE and WebAudio and WebAssembly multiple times per week these days. I used to tinker with some of those maybe once or twice a year.
Replies
That's my experience too, except that I'm not using three.js, just WebGL. At this very moment I'm trying to elicit an in-browser machine-vision app that records go games on a go board if you mount your cellphone on a tripod over the board, with the idea of integrating it with an Emscriptened KataGo to give kibitzers real-time feedback. This would have been insanely ambitious for me three months ago, and now I'm hoping I have it in good enough shape to test at the go club tonight.
Why three.js? Your LLM will do fine without it and be able to optimize further for your particular use case without being stopped by three.js architecture that may or may not fit your project.
Ask your LLM, "Can we remove three.js so that we can re-architect the graphics system to be more optimized for our specific use case?" and see what it comes back with.
It's wild how much more difficult it is to actually use things that harness web technology these days.
I built a voice-command driven kitchen assistant demo with webkit speech to text and WebAudio, and that was 10 years ago!
would be fun to revisit and see what v2 would look like today, I have a feeling I wouldn't be manually recording voice lines this time around ha
https://github.com/pathouse/kitchen_assistant