5 ms·
> a downside about React is the fact that your template is also JavaScript Everytime I read this (and it still seems to happens in 2019) I just don't get it--I
by nightnight 7y ago
> a downside about React is the fact that your template is also JavaScript
Everytime I read this (and it still seems to happens in 2019) I just don't get it--I don't get why people want to stick to the past. It's the best thing which could happen, everything is JS, FE development finally got bearable, no, enjoyable! It freed us from all the subpar patterns before.
- erokar 7y agoWhat is it you don't get? The parent post clearly states why this can have performance costs. Other modern frameworks like e.g. Svelte solves rendering without making templates JS.
- nightnight 7y ago> performance costs They are overstated. You are not building Photoshop in the browser 99% of the time. Dev productivity should have a higher prio => everything in JS and nobody needs some FE VM with bytecode (wtf, I mean when we already talk about Ember, Ember interfaces are not really the fastest one despite having their own small VM). This is what I don't get, sticking to the past and requiring stuff which doesn't make sense.
- erokar 7y agoSticking to the past? You talk as if JSX is the final solution in dev productivity, after which nothing else is even worthy of consideration. JSX has pros and cons, as does e.g. Vue's and Svelte's templating approaches. Something even better will surely appear, or already has.