I have over a years worth of content where I build a video in Zig, Odin and now C, compiled to WASM, running on the browser with no hardware acceleration, no canvas, no webgpu, no webgl, just to show it's possible. https://www.youtube.com/@SpiroFloropoulos
I can help with team management (hiring or building a team) of programmers.
I have over a years worth of content where I build a video in Zig, Odin and now C, compiled to WASM, running on the browser with no hardware acceleration, no canvas, no webgpu, no webgl, just to show it's possible. https://www.youtube.com/@SpiroFloropoulos
I can help with team management (hiring or building a team) of programmers.
Go ahead and tell me how cacheable your SSR page is. If it was a static file? Oh yeah it never changes! How convenient! Maybe that's the point!
People who promote SSR are simply trying to rope frontend devs into their P2 or P1 incident responses and use them as whipping boys. This shit has to stop.
If you don't suspect your web devs are doing all kinds of cache-busting dog shit on your backend ruining your performance dude idk what to tell you other than: what year do you think it is and who do you think you hired?
It's SSR nonsense constantly spammed on sites like this that make you think it's a good idea and ultimately give inexperienced devs the green light to do all kinds of dumb shit that carries heavy technical debt once you need to meet an SLA that is more realistic than anyone who seriously uses HTMX on anything at that scale. There's no excuse for using tools like this other than ignorance.
Do you have a proper link to the webtransport-p2p idea? I've done a few searches but I think there's some mix of current implementation and deprecated implementation somehow.
I don't know why it's fallen off, to be honest, or what was raised against it. Highly desireable to a lot of p2p folk, a very promising webrtc datatransport replacement.
I am building a WASM based "grid editor". It's really just a way to build a UI for anything (desktop, mobile, web) by slicing up a grid and putting content in it. Then you can export the grid in an extremely portable format that can be reas anywhere (no, not json, even simpler) and use that grid data to implement your UI. The grid data contains the content or references to content which you can just apply on render.
visualgrideditor.app
Mad with Odin, compiled to WASM, vanilla JS and has Laravel integration. I just need to alpha test this more and see if there's anybody who wants to use it.
reply