Nice: a web service that creates a calendar event from a URL

The author takes the example of a tree structure.

TL;DR; Start with lifetimes, if it is not enough and you don't need a specific guarantee: Box, then go for Rc or Arc if needed.

Various way to print "Hello World!" in rust

Advantages of types: they are here to help, improve readability, and provide context

How it is optimized to be the fastest possible.

All that we did to get this speedup is implement the Serialize trait using one line for the body of the serialize method!

But implementing the trait directly loses the possibility to serialize the structure with the #derive(Serialize) macro.

Instead, you should implement it on wrapper types that act like formatters.

Also for efficiency: format_args! doesn't allocate or even apply the formatting! It only returns Arguments which is a formatter that borrows its arguments.

The author shares its point of view on Shuttle that needs little to nearly 0 configuration to get started.

Zerocal was the first project I deployed on Shuttle. The principle was very simple yet innovative: encode calendar data directly into a URL. [https://endler.dev/2022/zerocal/]

#project #idea improve the UI or make a custom one that calls the API
#project #idea use such API to generate other files. Contacts?

Ok not bad at all. I still think Rust is not meant for prototyping, but let's give it a try.

This project looks interesting.

• No VDOM
• Rust syntax
• CSS scoping
• Routing & SSR & SSG
• Tauri support
• Htmx integration

Will it be worth it for you? If you need to iterate rapidly, probably not. If you have a known scope, or can absorb more upfront cost? Definitely consider it. You’ll end up with bulletproof software. With the WebAssembly angle becoming stronger every month, the prospect of writing perfect software once and reusing it everywhere is becoming a reality sooner rather than later.

As I am using Typescript on a daily basis, it helped to have such a comparison 😃

It looks interesting! In JS, snapshot testing is a must because objects are everywhere.
It can be useful in Rust too.

I may want these parts in the future:

I am connecting the folding API in Neovim to the Tree-sitters folding functions

Configuring 'puremourning/vimspector'

And also the parts starting from Cargo Power with Terminal Access. Let's keep the learning curve low and learn step by step.

A backend compiler and an alternative of LLVM