Not sure I understand because that's what it is basically. The Rust part is just for the routing; it decides whether to serve the form or the generated calendar file.

What they mean is that instead of using "serverless" hosting running a rust program to generate ics files you could literally just have a statically hosted html file that uses a couple lines of javascript to generate the ics files within the browser, so there would be no rust or server component at all.

You could just host it with github pages.

Actually I'm confused why you're saying:

> The Rust part is just for the routing

Because it appears that you're generating the ics files in rust?

Got it. The generator logic is in Rust yes. I could have written it in JavaScript as well but it was just easier for me to do that part in Rust. Should have mentioned that. Of course you could host a static HTML with JS on Github pages, but Github pages also runs on a server. So to answer the original question, yes you do need some server for it unless you make it a command line app.

You need a browser and a file. In your example you need a server to make the file and and a browser.

True, but for others to resolve the calendar entries you'd need to serve that file somewhere.

/me glances at serverless in the title. Man, I would not want to have to technically design anything with you. You can't just say a thing is something and then say "oh well it's not actually but it could've been if I had made it entirely differently." ...

You can serve a static HTML page from anywhere. GitHub pages, S3, maybe even Dropbox. Running a Rust binary is an order of magnitude more complex than that.