Zezima

command line interface interface

by the time you are scheduled to get a CT scan, the possible diagnosis which lead to the CT scan is almost certainly riskier than the cancer.

Move along...

An amazing example of Rust's abilities. More impressed by the relentless iterative approach taken by the author. Nicely done.

As a Recurse Center participant and alum, these rules form an important and largely silent backbone of the community's culture.

Often reading rules causes strong reactions. Seeing how those same rules are implemented makes all the difference.

Rather than discussing the rules, I'll share experiential evidence: the community is welcoming to beginners, gentle, curious, kind, playful, and above all else: supportive.

The rules are a helpful "buck" to stop at should mistakes or conflict - small or large - arise (which rarely occurs). The key is commentary and forgiveness.

The experience of attending a batch at recurse is largely regarded as their best for many of my fellow Recursers - it certainly is one of mine.

If you're curious please reach out to them. I'm also happy to chat or answer any questions (and give a glowing review).

So happy to see Dusa on HN. Was a joy to see you work on it while in batch at RC. Congrats!

I have this as well, it's mildly entertaining but not overpowering. The floaters only appear when looking at a very bright blue clear sky, it never triggers otherwise.

When it does I can pause, appreciate the show, and then go back to my day. It's a fun one for sure.

The person's name is Cal

Thank you!! So hard to sift through hundreds of products.

Can anyone identify the laptop stand in the promo video at 0:30?

Seconding Zola. Fantastic project. I built a site with > 200 pages (including media) in 90ms on an M1 MacBook Pro.

There is no plug-in ecosystem unfortunately.

Shortcodes are nice and a modest replacement. Missing any headless CMS integration naturally because it's statically typed and compiled.

The code you wrote would be a valid use for `MyError`

Not the poster. What exactly are you asking about?

The usage of the error type the OP wrote is to get the line number of any error without using a macro on top of every single function in our crate.

The person who wrote `MyError` accomplished it by defining their error type as "something that can be constructed from any other error" (`impl From<E: StdErr> for MyError`) and additionally heap-allocated the original error with `Box::new(error)`.

So the usage would be to write one single error type in a crate which can "capture" or be constructed from any error type `E` and also prints out the line number of that error via `impl Display for MyError`.

Wikihouse is awesome! Thanks for that introduction