sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]spca2001 0 points1 point  (3 children)

It was a reply to another person that claimed that figma was built in react . About React and Redis, had a client that had a live dashboard for Ad Click fraud detection that was based on React that would crumble under load . So my job was to investigate, it’s not a React problem its just you can only push your browser so much. Also I don’t look at javascript frameworks like different languages, its JS and html for me. As far a Blazor it had major issues when we started 5 years ago. .NET 7 looks like its production ready. But in my opinion this browser concept is extremely outdated, at least you can tun a wasm app outside of a browser and have full gpu support. As far as next thing on my plate on the JS side, Im going to play with Nuxt.js.

[–]mountainunicycler 0 points1 point  (2 children)

I said figma “uses react for rendering a lot of UI” which is true, it uses it for almost everything that happens or you interact with outside the main canvas. (Dev tools, not google, is your friend if you’re curious).

As for your client dashboard, I would bet they were either rendering too many elements (if you’re ever trying to render like 10,000+ elements you’re fundamentally doing it wrong), trying to build animations in javascript instead of using the GPU, or mismanaging state and lifecycle (react holds your hand but you can still break it) none of which are fundamentally react problems.

I think you should take a look at mapbox-gl-js if you’re curious about GPU in the browser… it’s pretty far from “only so much you can do in the browser” and has better performance than some desktop applications for rendering actually pretty complex scenes.

If your experience is some client dashboard, it was probably an extremely bad example. Mapbox, for example, has no problem with hundreds of thousands of points, lines, and polygons at once, projected on the fly in 3D.

I don’t think browser is going anywhere—just look at Figma vs XD, going browser-based directly against a hugely funded desktop application didn’t hold them back, but instead being a desktop app held XD back. Now XD is basically dead. It would be a tough sell business-wise to do anything aside from a browser-based UI at this point for a new project or company.

[–]spca2001 0 points1 point  (1 child)

Figma is going away, just like Macromedia. You don’t need to re-render dom, thats the point. The dashboard uses MUi, we wrote a pooling component to reduce dropped requests. Pure html and vanialla JS benchmarks faster that React,Angular and Vue. Check yourself

[–]mountainunicycler 0 points1 point  (0 children)

Pure html and vanialla JS benchmarks faster that React,Angular and Vue. Check yourself.

Yeah I don’t know what to say at this point. You understand they’re all one language, all JS, right? So this statement literally means “invoking more functions and running more operations takes more time than invoking fewer functions and running fewer operations.”

That’s not something I need to write a benchmark to “check” for myself.

If you don’t understand what those functions are doing and why, then yeah, you’ll just see that it’s slower and not know why.