omn1

Same. Used shuttle for https://endler.dev/2022/zerocal/ lately and was super happy with the experience. I no longer have to worry about hosting and can focus on the product instead.

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

Update: self-hosting works now. Added instructions to the docs. Have fun.

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.

Good question. It depends on your definition of serverless. Strictly speaking there is no serverless, there's always some infrastructure somewhere.

However the calendar file gets created out of thin air from the GET parameters alone. There is no state or storage involved. Other calendar apps have a backend with a DB; this one doesn't. Now whether that counts as truly serverless is up to you I guess. It's as close as you could get with a calendar I'd say. Not easy to get the point across in a title. ;) Hope that helps.

You could do that but you'd have to create the ics file manually and not every platform allows you to share ics files. My original use-case was Github. Wanted to share invites for https://github.com/hello-rust/community. Github prevents sharing ics. Another thing is that people could edit a link in-place to e.g. update the time without creating a new file.

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.

Thanks for the info. I thought I fixed that lately [1]. I don't have an iPhone to test it with but I'll see what I can do.

At least on the Chrome viewport emulator it looks fine to me...

https://github.com/mre/endler.dev/commit/bc1187d290d153455b0...

That's correct.

It's just Rust, so it can be. Will add a `main.rs` and some instructions, but PRs are welcome if someone beats me to it. ;) https://github.com/mre/zerocal/issues/9

Author here, had a lot of fun building this as it's just ~100 lines of Rust code + some CSS/HTML. If someone is looking for a fun thing to contribute to during Hacktoberfest, the code is on Github: https://github.com/mre/zerocal Will mainly use it for myself to send out event links to friends.

ripgrep by BurntSushi (https://github.com/BurntSushi/ripgrep)

Which is weird because the unicorn is an inlined image (png), encoded in base64. Seems like they broke it.

Even though the status page (https://www.githubstatus.com/) shows no issues, I'm still getting the occasional 500. It seems to be happening quite irregularly. They are possibly facing a lot of load.

They did actually. You can paste an image into a Markdown file with cmd/ctrl+v.

I maintain a couple of bigger Github repos and blogs and was shocked at how many links break on a regular basis, so I wrote my own link checker in Rust [1] and started donating to the Wayback Machine. Please consider doing so, too as the web would be a worse place without them. [2]

[1]: https://github.com/lycheeverse/lychee [2]: https://archive.org/donate/

Same. Few years ago I started a little list of linters. Just kept adding tools and the list is huge now thanks to lots of contributors. https://github.com/analysis-tools-dev/static-analysis Still love adding new linters there when I cross their path. :)

The organizers of the previous RUST devroom (2018, 2019, 2020) decided that we won't be organizing it this year as a huge part of FOSDEM is getting people in the same room and being able to create face to face discussions on the back of the

We announced it here a while ago: https://www.reddit.com/r/rust/comments/j03i80/fosdem_2021_on...

We were encouraging others to fill the gap if they wanted but no one really stepped up so... ;) I hope that next year we'll be back in person.

Me too. Shout out to the orga team who always provides cheap (but great!) sandwiches and mate. That's FOSDEM to me. That and the nerdy discussions in the rain while waiting in the food truck queue.

You can use pot: https://github.com/pizzamig/pot

Great post! I like articles where the author has practical experience in two languages and compares them. Helps me make better decisions for future projects.

You're right about the massive amounts of C/C++ code out there. I'd disagree that the integration is harder than with C++, though.

Calling Rust from C and vice versa is fairly straightforward and there are automatic code generators for doing so. Things just get wrapped into an `unsafe` block and that gives you the same guarantees you'd have with C++ (none, basically). From there you can start to gradually rewrite critical parts in safe Rust and profit from the cargo ecosystem along the way. In that sense there's even an advantage for Rust over C++ in my book.