I'm starting to think that the whole "static-only website" meme from the early 2010s along with the normalization of static-site generators like Jekyll were a psyop to get websites dependent on big tech, such as using Disqus for comments, Google Analytics instead of hit counters, or Google Site Search for search functionality.
There is nothing wrong with static-sites or static-site generators, but there is a case to be made for server-side scripting, even on personal websites.
I agree.
Have used static site generators, such as Hugo, and mostly been a good experience.
However, the concept of a website being a program instead of just a collection of documents is really interesting and I would like to eventually do more with that.
#webdev
@matthew
>However, the concept of a website being a program instead of just a collection of documents is really interesting and I would like to eventually do more with that.
If you are talking about webapps that replace desktop programs, don't. I think there is a case for the web being more than a remote document retrieval tool, but only in a limited sense. Shopping sites, social media sites Internet forums, guestbooks, wikis, etc have their place, but we don't need any more examples of "photoshop in the browser".
I've been thinking of this idea for years. It's a network protocol where the client is simply a JIT compiler and the server serves source code for games and other software. Kind of like Adobe Flash, except that it doesn't use the web browser and the source code for software is always available (not counting obfuscation).
I'm very much appreciate wikis.
> but we don't need any more examples of "photoshop in the browser"
Yeah, we agree on that, too 😄