frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Perplexity partners with Nvidia to launch Portable Computer

https://venturebeat.com/infrastructure/perplexity-partners-with-nvidia-to-launch-portable-compute...
1•gmays•50s ago•0 comments

CrowdGPT – AI Owned by Everyone

https://www.crowdgpt.net/#home
1•Retro_Dev•6m ago•0 comments

Itzma, an embedded vector database backed by object storage

https://github.com/sergiommarcial/itzma
2•Kh40sz3r0•11m ago•0 comments

Microsoft 365 outage leads to chlorine gas poisoning of 15 hotel guests

https://www.tomshardware.com/tech-industry/data-centers/microsoft-365-outage-leads-to-chlorine-ga...
6•ivewonyoung•16m ago•0 comments

Skydio's asymmetrical F10 Lightrunner solves a problem with fixed-wing drones

https://spectrum.ieee.org/skydio-f10-lightrunner-asymmetrical-drone
2•Gaishan•17m ago•0 comments

The first ping from Tonga (1997)

https://colo.to/firstping.html
2•Eric_Gullichsen•19m ago•0 comments

Show HN: I rewrote Doom2D Forever in Rust, playable in browser

https://doom2d.oddbench.co/
3•256cats•21m ago•0 comments

Advice for new (and old) devs with Dan Moore [video]

https://www.youtube.com/watch?v=cjTHn_lABlI
2•mooreds•22m ago•0 comments

What's Next for Nvidia?

https://steveblank.com/2026/11/15/whats-next-for-nvidia/
2•zdw•24m ago•0 comments

The efficient frontier of LLM inference

https://www.baseten.co/blog/the-efficient-frontier-of-llm-inference/#quantization
2•gmays•24m ago•0 comments

Mini.nvim Is Now on Tangled

https://tangled.org/nvim-mini.org/mini.nvim
2•nerdypepper•24m ago•0 comments

The Lancet Commission on 21st century global threats to health

https://www.thelancet.com/commissions-do/global-threats-to-health
2•fosco•25m ago•0 comments

Parcel: A desktop mail client for Linux, built with Zig

https://tangled.org/rockorager.dev/parcel
2•nerdypepper•25m ago•0 comments

How do groups work on Linux? (2017)

https://jvns.ca/blog/2017/11/20/groups/
2•zenincognito•27m ago•0 comments

The single router in southern Arkansas that ground air travel to a halt

https://www.msn.com/en-us/news/other/the-single-router-in-southern-arkansas-that-ground-air-trave...
3•CharlesW•29m ago•0 comments

Estonia to close all border crossings with Russia after attack on drone maker

https://www.theguardian.com/world/2026/nov/15/estonia-to-close-all-border-crossings-with-russia-a...
3•howard941•31m ago•0 comments

Show HN: Wipeout-style mini racer written in C++ compiled to WASM for browser

https://gamedevpl.github.io/silnik3d-od-zera/demko/
3•fullstackwife•42m ago•1 comments

Why your Wi-Fi slows down when more devices connect

https://www.engadget.com/2313934/wifi-slows-down-when-devices-connect/
3•zenoware•43m ago•0 comments

How to Get Mentorship

https://mirawelner.com/posts/cube.html
1•mirawelner•45m ago•0 comments

Reddit's traffic is down 13%, partly thanks to AI Overviews

https://www.businessinsider.com/reddit-traffic-down-13-percent-similarweb-google-ai-overviews-202...
11•madihaa•46m ago•1 comments

Rebuild it from the picture Dynamic Programming

https://nokku.payanai.com/interview-prep/dsa/dynamic-programming
2•payanai•48m ago•0 comments

A step toward defining the Standard Model on a lattice

https://openai.com/index/step-toward-defining-the-standard-model
4•acossta•51m ago•0 comments

GLM Models Cut AI Coding Costs 90% for 2k Engineers

https://finance.biggo.com/news/71888475bad974d6
6•iwayato•52m ago•0 comments

Jensen Huang might return to Nvidia as CEO

https://www.reuters.com/world/china/jensen-huang-discusses-comeback-nvidia-ceo-with-allies-ft-rep...
78•YakubYilmaz•55m ago•50 comments

When Failure Becomes Expensive: How Systems Reorder What Is Worth Protecting

https://notesonordering.substack.com/
3•CornorReed•56m ago•0 comments

Extinct 'vampire camel' once stalked North American plains – Science – AAAS

https://www.science.org/content/article/extinct-vampire-camel-once-stalked-north-american-plains?...
5•rbanffy•57m ago•0 comments

Building a Company Without Losing Your Marriage

https://founderreports.com/interview/what-a-startup-does-to-a-founders-marriage/
3•peterchane•1h ago•0 comments

The Joy of Fuck-You Money (2018)

https://thedeepdish.org/fuck-you-money/
2•downbad_•1h ago•1 comments

The Lyttle Lytton Contest 2026 winners

https://adamcadre.ac/lyttle/2026.html
2•agluszak•1h ago•0 comments

Chemical spills into drainage ditch at SpaceXAI in Southaven

https://wreg.com/news/chemical-spills-into-drainage-ditch-at-spacexai-in-southaven/
30•mikhael•1h ago•9 comments
Open in hackernews

Show HN: Stack Error – ergonomic error handling for Rust

https://github.com/gmcgoldr/stackerror
27•garrinm•1y ago
Stack Error reduces the up-front cost of designing an error handling solution for your project, so that you focus on writing great libraries and applications.

Stack Error has three goals:

1. Provide ergonomics similar to anyhow.

2. Create informative error messages that facilitate debugging.

3. Provide typed data that facilitates runtime error handling.

Comments

tevon•1y ago
This is awesome! Will give it a try in my next project.

How does it keep track of filename and line number in a compiled binary? I'm fairly new to rust libraries and this doesn't quite make sense to me. I know in JS you need a source-map for minification, how does this work for a compiled language?

fpoling•1y ago
Rust provides file!, line! and column! macros that expands into a compile-time constants that the compiler embeds then into the executable. This way no source map at runtime is necessary as the relevant errors are constructed from those constants.

Presumably StackError just uses those macros.

But for debugging a source map is still necessary and is a part of various debug formats.

rhabarba•1y ago
I still prefer the Anyhow solution, but I like the approach here.
IshKebab•1y ago
Isn't this strictly superior to Anyhow? What do you like more about Anyhow?
rhabarba•1y ago
I prefer Anyhow's non-intrusiveness: "Result" is still "Result" and all I need is a "?". I agree with Stack Error's documentation that Anyhow can't help with debugging that well, but it's "good enough" in my opinion.
IshKebab•1y ago
Result in `anyhow::Result` though. It's still a different type. Or do you literally mean you like that it is still spelt the same?

And I think you can still use `?` with this if you don't want to add any context... Not 100% sure on that though.

rhabarba•1y ago
Might as well be my limited understanding from what I can read behind the link, to be fair.
garrinm•1y ago
Anyhow still makes things easier for application development. The main drawback is that the resulting error type doesn't implement std::error::Error, so it's not suitable for library development (as pointed out in the anyhow documentation). Stack Error is a bit less ergonomic, but suitable for library development.
shepmaster•1y ago
I hope to read through your crate and examples later, but if you have a chance, I’d be curious to hear your take on how Stack Error differs from my library, SNAFU [1]!

[1]: https://docs.rs/snafu/latest/snafu/index.html

garrinm•1y ago
I played around a bit with SNAFU a couple of years ago, but I'm haven't worked deeply with the library so there might well be some features I'm not aware of.

I think SNAFU is more like a combination of anyhow and thiserror into a single crate, rather than Stack Error which leans more heavily into the "turnkey" error struct. Using the Whatever struct, you get some overlap with Stack Error features:

- Error message are co-located.

- Error type implement std::error::Error (suitable for library development).

- External errors can be wrapped and context can easily be added.

Where Stack Error differs:

- Error codes (and URIs) offer ability for runtime error handling without having to compare strings.

- Provides pseudo-stack by stacking messages.

Underlying this is an opinion I baked into Stack Error: error messages are for debugging, not for runtime error handling. Otherwise all your error strings effectively become part of your public interface since a downstream library can rely on them for error handling.

lilyball•1y ago
If the macros only exist to get file and line information, you could do the same thing by using `#[track_caller]` functions combined with `std::panic::Location` to get that same info. For example, `stack_err!` could be replaced with

  impl StackError {
      #[track_caller]
      fn new_location(msg: impl Display) -> Self {
          let loc = std::panic::Location::caller();
          Self::new(format!("{}:{} {msg}", loc.file(), loc.line()))
      }
  }
such that you call `.map_err(StackError::new_location("data is not a list of strings"))`. A macro is nice if you need to process format strings with arguments (though someone can call `StackError::new_location(format_args!(…))` if they want), but all of your examples show static strings so it's nice to avoid the error in that case.

The use of `std::panic::Location` also means instead of baking that into a format string you could also just have that be an extra field on the error, which would let you expose accessors for it, and you can then print them in your Debug/Display impls.

Speaking of, the Display impl really should not include its source. Standard handling for errors expects that an error prints just itself with Display because it's very common to recurse through sources and print those, so if Display prints the source too then you're duplicating output. Go ahead and print it on Debug though, that's nice for errors returned from `main()`.

garrinm•1y ago
Thanks for the insight, I wasn't aware of `track_caller`. I'll definitely be looking into this. I was scratching my head trying to figure out how to make file and line number usage consistent and customizable, this looks like the answer!

You're also right that this will pretty much eliminate the need for macros.

That's also a very key insight about Display vs. Debug printing. I'll be looking into that as well.

Thank you for the thoughtful reply.

DavidWilkinson•1y ago
Dei here, from the team behind Error Stack [1] (a similarly named existing, context-aware error-handling library for Rust that supports arbitrary attachments). How does Stack Error, here, compare?

[1]: https://crates.io/crates/error-stack