251–254 of 254 posts
Earlier quoted context omitted.
It does if you're debugging performance issues.
If you need good performance to debug "performance issues" - lack of good performance - I don't think you will solve your problem.
Earlier quoted context omitted.
Theoretically, wasm shouldn't have more access, though I would be moderately concerned about bugs, and better access for timing and rowhammer. Practically, it's mostly used for tracking and making users' machines execute even more inscrutable code. IMO, if you need wasm for |"normal" pages and apps, you're doing something wrong. There are notable exceptions (say machine emulators, maybe 3d games and such), but they a…
It's ridiculous to me to even call these things web browsers anymore. A more realistic term is any-type-of-application-cross-platform engine. But that's not really concise. Why did the web have to become the primary development platform for nearly everything, with WebAssembly, WebGL, notifications, etc? I, for one, am a fan of the fact that Gemini is growing in adoption (at least as far as I can tell). Such a nice, s…
Earlier quoted context omitted.
Your own comment makes it pretty clear that React is not immediate mode. Not the immediate mode that everyone understands anyway. Your "traditional immediate" and "react immediate" are just terms you made up. React is clearly a different thing to immediate mode and retained mode. You don't have to cram everything into those two categories. We could do with a word for it though. I don't think the guy you linked is a R…
> Not the immediate mode that everyone understands anyway. Your "traditional immediate" and "react immediate" are just terms you made up. The terms, yes. The descriptions and understanging of React (as an immediate mode wrapper over DOM) is shared across the community, all the way to Wikipedia: "One way to have the flexibility and composability of an immediate mode GUI without the disadvantages of keeping the widget…
Earlier quoted context omitted.
It's an alternative that gives them the updatability of JS. When they describe their original (JS/C++) architecture they mention this as a motivating factor: > This architecture split allows us to deliver new features and bug fixes without having to go through the very slow process of updating the C++ layer. The downloadable code is delivered through a fully automated continuous integration and delivery pipeline that…
>probably more reliance on the app update systems of third parties. Exactly right. Big platforms with guaranteed support is one thing, but here's the situation for smart TVs right now: It's 2022. You build an app for SuperScreen's latest range of smart TV. You update it every so often, and SuperScreen are happy to certify those updates and help you push them. It's 2023. You port your app to SuperScreen's latest range…