>You only need JavaScript if you make a site that is basically an application. You may not even need that. As part of the process of learning Nim, I've been ma

>You only need JavaScript if you make a site that is basically an application. You may not even need that. As part of the process of learning Nim, I've been making a package repository that's designed to accept artifacts from a CI system, store them, and allow searching by a variety of different package metadata, including a web interface to manage all your artifacts. Not a complex webapp, but also not a trivial one. Anywho, I decided to set myself the challenge of using no javascript anywhere on the site. It's really not been much of a problem. The UX is different, which means the application UX design is different. But it isn't worse. The only thing I've run into and been unable to solve without javascript is that when you use the file picker to manually select a file on your computer for upload (rather than using the API), I can't update the page to show you which file you picked. Based on my experience, javascript is like a fine spice. A little bit of it added to your page in just the right amount can make an average web experience fantastic. Taking the cap off the JS shaker and just pouring it in is almost certainly going to make the experience far worse.