You just described how the popular "anyhow" and "snafu" crates implement error handling

Even with anyhow there is a lot of boilerplate it seems to me dealing with crates that don’t use it. I haven’t tried snafu but its name does not inspire confidence.

Clanker (ai assistant) also love to unwrap and if you don’t catch them you have an abort waiting for you.

It's most useful for companies, where the goal is as much SSO as possible.

Check out mise: https://mise.jdx.dev/

We use it at $work to manage dev envs and its much easier than Docker and Nix.

It also installs things in parallel, which is a huge bonus over plain Dockerfiles

I declared nix bankruptcy earlier this year and moved to mise. It does 90% of what I need for only 1% of the effort of nix.

MercuryOS towards the bottom is pretty cool

MercuryOS [1, 2] appears to be simply a "speculative vision" with no proof of concept implementation, a manifesto rather than an actual system.

I read through its goals, and it seems that it is against current ideas and metaphors, but without actually suggesting any alternatives.

Perhaps an OS for the AI era, where the user expresses an intent and the AI figures out its meaning and carries it out?

[1] https://www.mercuryos.com/

[2] https://news.ycombinator.com/item?id=35777804 (May 1, 2023, 161 comments)

You can still get dragged to court for it[1], even if you may (eventually) win, lawyers are expensive.

[1]: https://techcrunch.com/2021/10/15/f12-isnt-hacking-missouri-...

But he wasn't dragged to court for it.

https://missouriindependent.com/2022/02/11/prosecutor-isnt-p...

I wrote a similar algorithm for pathfinding around vector shapes in Javascript, the implementation was surprisingly simple.

https://github.com/Wazzaps/FastPathfinder

I’ve reviewed the source code. It seems like starting with clear and accurate information about the obstacles could be an issue. Also, if the obstacles become very large, preprocessing will likely be necessary.

Oh~ That’s awesome! I’ll start analyzing the source code! Thank you!

It also includes 256kbps AAC audio (vs 128kbps for free users).

I have no idea what that is. You're talking about kilobytes per second? This feature makes it useful to use bluetooth or other non hardwired sound output?

Or use Tailscale to solve both issues at once

They also support (and recommend I think?) an eBPF-based sensor

Apparently CrowdStrike bypassed clients' staging areas with this update.

Source: https://x.com/patrickwardle/status/1814367918425079934