3 ms·

I am starting a new web project next week (first web project in years), thank you for your explanation. I like treating code as data and vice-versa so i figure

• eyelidlessness 6y ago
  I’d strongly encourage looking at Next.js (with TypeScript if you prefer or have an open mind to it; TS support is first class now with no additional action needed than using .ts/.tsx files). It’s really great out of the box for many common web needs, has sensible defaults but easily configurable using other common tools, provides SSR/SSG/many optimizations out of the box, and a great track record of continual improvement.
• ergothus 6y ago
  Re: comparing to jQuery. A lot of the ease and benefits depends on your style. If your code pattern was to have variables holding your state and rendering html based on that, you will have an easy transition to React ( and likely didn't suffer horrible pains with jQuery). If your code style is to update the DOM to reflect your state, and when you need to know something about state, you read the DOM, then React will feel odd and complex (and you likely have had jQuery projects work great until they hit a level of complexity and then they suddenly become brittle and hard to change) This is why I prefer React - the best practices if React are just the best practices for functions. (That and I don't like the pseudo js syntax of Vue with the mysterious scoping)