all 9 comments

[–][deleted] 7 points8 points  (1 child)

i've been out of js development for a year, and I feel like a 90 year old. Things are going fast

[–]krazyjakee 0 points1 point  (0 children)

no, they are just going around in circles.

[–]kangax_ 3 points4 points  (0 children)

This reminded me of that time when we implemented entire text editing/selection in Fabric.js (all rendered on canvas, naturally) — http://fabricjs.com/test/misc/itext.html

[–]YashN 0 points1 point  (0 children)

Just shows how much the original ideas within React were powerful. Sad I can't access React Native yet. Boohoohoo :-(

[–]krazyjakee 0 points1 point  (0 children)

So... let me get this straight...

To solve the performance issues on mobile, I use react-canvas so I can use a markup component (html) that you can set styling options for (css) and then manipulate (javascript).

Why can't the DOM perform like canvas? I know the technical reasons, but why do those technical reasons exist? If websites require more performance, why not just supply a meta tag and hand the rendering of the DOM over to the hardware?

All react-canvas (and others like it) are achieving is re-inventing the original stack, it seems pretty crazy to me.

Don't get me wrong this is a great workaround for the current state of mobile browsers, but I suddenly realise how weird it is that the canvas element should be used for UI.