There’s a large number of tools that expand the options available to you as a front end developer (as well as tools that are part of the ecosystem that supports the first set of tools). Basically all of those tools are built around the assumption that you can just use javascript.
You can build sites that function without that, that have javascript as an optional thing that spruces up the site for people who use it. But you will be putting in more effort. ReactJS (which Lesswrong 2.0 is built on), is built around the premise that you literally just use javascript for everything (HTML is rendered out of javascript files). This has a lot of benefits. You don’t need to have three sorts of files (html, javascript, and css) for every component of your page, and it’s generally easier to automatically test your site if you know what you’re doing.
I don’t think this was necessary or inevitable, but it is the way things have shook out.
I humbly request this to be unpacked.
There’s a large number of tools that expand the options available to you as a front end developer (as well as tools that are part of the ecosystem that supports the first set of tools). Basically all of those tools are built around the assumption that you can just use javascript.
You can build sites that function without that, that have javascript as an optional thing that spruces up the site for people who use it. But you will be putting in more effort. ReactJS (which Lesswrong 2.0 is built on), is built around the premise that you literally just use javascript for everything (HTML is rendered out of javascript files). This has a lot of benefits. You don’t need to have three sorts of files (html, javascript, and css) for every component of your page, and it’s generally easier to automatically test your site if you know what you’re doing.
I don’t think this was necessary or inevitable, but it is the way things have shook out.
Why not use something like.. werc? http://werc.cat-v.org/
Granted, if you’re using Windows, you’re out of luck.