Hyper.app: https://hyper.is/
hyperapp: https://github.com/hyperapp/hyperapp
Hyper.sh: https://docs.google.com/presentation/d/1nrfEcCITAofSDPFTIkiA...
Adding this to the list https://news.ycombinator.com/item?id=14634284
Also, the .sh does make this particular example at least slightly distinctive.
Note: It's an entirely reasonable question to ask, which makes it all the sadder.
> 16-bit wordlength, 2048 words RAM (magnetic core memory), 36,864 words ROM (core rope memory)
Source: https://en.wikipedia.org/wiki/Apollo_Guidance_Computer
As you can see this workload is only using about 6% of the available memory. For event loop driven systems like Node.js or Nginx, or Go the workload is almost always CPU bound not memory bound:
I've written small Go programs that can consume around 15-20MB on low traffic. But they also have huge spikes in memory usage when you have concurrent requests hitting them.
Setting up a container with a cronjob that, once per day, executes a simple shell script which curls a REST endpoint, parses the relevant information, and sends an email out to a pre-defined mailing list or puts it to a slack channel... Yeah, that's pretty simple to pull off within that memory footprint.
Cheapest single container with a publicly accessible IP (FIP) assuming a 1GB Docker image size.
S1 container: 1.03/month
FIP: $1/month
RootFS Container Volume (10GB@$0.1/GB/month): $1/month
Container Image (1GB@$0.1/GB/month): $0.1
Total monthly price: $3.13/month