Here's a (somewhat) old fashioned way of building software that should make a comeback:
A long running daemon server that runs a full language interpreter and responds to user commands – without constantly shutting itself off.
It's not the right fit for *every* situation, but it kills me to see how many python/node/ruby/etc scripts fire up and entire runtime just to run a few commands – only to kill that runtime off even though they'll predictably need it again a few seconds later.
@codesections fastcgi is great, except it's a giant security hole because every user task might leak data to the next.
@codesections that depends on what you're doing. If you have something that ribs every few seconds, you most likely already do have a daemon.
@codesections This is how Emacs client / server setup works and it's beautiful.
@codesections, this is Erlang/OTP’s wheelhouse. I suggest starting with Elixir for the more familiar syntax. One of its superpowers is being able to connect a REPL to a currently running app to see what it’s doing.
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.