undefined | Better HN

0 pointscrooked-v7y ago0 comments

> This usually included weeks of work, after which it was possible to write web applications which could've been written with vanilla JavaScript on a static, handwritten HTML page in a single afternoon.

You can have a website up and running (not just locally, but live on the Internet) within literally 5 minutes using React and Heroku, netlify, now.sh or whatever. If it takes weeks to do that, you're doing something fundamentally wrong.

0 comments

lqet7y ago

It did not weeks to write the website, sorry if that was not clear from my original post. It took weeks to port existing JavaScript libraries into the ecosphere of the respective framework, to a point where it was indeed possible to write the website we wanted in 5 minutes.

> You can have a website up and running (not just locally, but live on the Internet) within literally 5 minutes using React and Heroku, netlify, now.sh or whatever.

Of course, I am not disputing this! But it is equally possible to have a website up in literally 5 minutes using vanilla JS + HTML + CSS and an nginx Server, without taking the dangerous bet that the framework you have chosen won't be obsolete in 2 years.

crooked-vOP7y ago

> without taking the dangerous bet that the framework you have chosen won't be obsolete in 2 years

That's why I specifically mentioned React and its API, as it's generic enough to have drop-in replacements or even frameworks that apply its basics to completely different kinds of rendering (https://github.com/vadimdemedes/ink). I find it unlikely that the basic idea of component trees, efficient one-way rendering of updated data, and JSX rendering will go away anytime soon, and none of that depends on the specific project named "React".

j / k navigate · click thread line to collapse