frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Amazon selects Pattinson as the next Bond

http://007.danieldeboulay.com
1•deboulaymxf•2m ago•0 comments

My Dog Ate a Freshness Packet – Silica Gel vs. Oxygen Absorber – PetToxCheck

https://pettoxcheck.com/dogs/my-dog-ate-freshness-packet/
1•marcus_marchett•6m ago•0 comments

Lockheed Taps OpenAI to Solve F-35 Challenges

https://www.bloomberg.com/news/videos/2026-10-02/lockheed-taps-openai-to-solve-f-35-challenges-video
1•unknown-unknown•8m ago•0 comments

Show HN: I made a site showcasing The Elm Architecture in many other languages

https://tea.rinn7e.com/
1•rinn7e•11m ago•1 comments

HomeView Teardown: A Surprising Step Backward

https://www.ifixit.com/News/120317/homeview-teardown-a-surprising-step-backward
2•gnabgib•15m ago•0 comments

OpenAI is starting to panic [video]

https://www.youtube.com/watch?v=UcEtgDu2t4U
2•Bender•17m ago•1 comments

Show HN: Ferrovec Retrace – semantic search over pages you've read, all local

https://github.com/singhpratech/ferrovec/tree/main/extensions/retrace
2•aiexplore369•18m ago•0 comments

Staged Publishing on Nuget.org

https://devblogs.microsoft.com/dotnet/nuget-staged-publishing/
1•soheilpro•18m ago•0 comments

QuadGate – 4-gate control plane that keeps agent KV prefix caches warm SHow HN

https://github.com/blagoslov333-cloud/quadgate
1•blagoslov333•18m ago•0 comments

Cutting Web Audit Overhead by 92% with Agentic Chrome DevTools

https://developer.chrome.com/blog/policybazaar-agentic-audit
1•bqc•20m ago•0 comments

Bank CEOs, NSA Tell Congress That AI-Driven Patches Are Behind Outages

https://www.washingtonsun.com/technology/bank-ceos-nsa-tell-congress-ai-driven-patches-behind-out...
3•ryeights•21m ago•0 comments

Show HN: A Codenames-style wordgame that benchmarks LLMs

https://wordspies.com/hn
1•hardicecream•24m ago•1 comments

Show HN: Convert EML/MBOX mailboxes to PDF in the browser, no upload

https://mailtopdf.top/en
1•mainliufeng•27m ago•0 comments

Show HN: Spillway – HTTP API load testing on macOS

https://spillwayapp.com/
1•edwardaux•28m ago•0 comments

Fate of the Galaxy Release. A long time ago, in a forum not so far away

https://www.fateofthegalaxy.net/
1•keks24•29m ago•1 comments

Calgary high school says too many students are getting food delivered

https://www.cbc.ca/news/canada/calgary/st-francis-high-school-calgary-food-delivery-app-9.7425320
2•canucker2016•29m ago•0 comments

Frontier models have few guardrails around autonomous weapons

https://www.vals.ai/blogs/autonomous-warfare
1•kartoshka•30m ago•0 comments

TheToolGenius – 35 zero-upload, client-side web utilities

https://thetoolgenius.online/
2•_just_a_develop•30m ago•0 comments

Framework Wireless Touchpad Keyboard

https://frame.work/products/framework-wireless-touchpad-keyboard
2•throwaway2037•38m ago•0 comments

FastFrames: Video Generation at Interactive Latency

https://huggingface.co/apple/FastFrames-L
2•CharlesW•38m ago•0 comments

Why valid Kubernetes YAML still breaks in prod and how to catch it before deploy

https://zhukovskyi.space/blog/kube-tooling-why/
2•andronaft•39m ago•0 comments

#1 on Sesame's TurnBench with a 14.9M-parameter turn-taking model

https://spero.patientdesk.ai/blog/kuroko
3•oncelozgul•41m ago•0 comments

LibreOffice RCE via ODF Form Datasource JDBC Code Execution

https://ii4gsp.github.io/libreoffice-rce/
2•DeepLogin•43m ago•0 comments

Does This Man Have a Right to the Data from His Own Brain?

https://www.nytimes.com/2026/11/17/business/brain-data-access-rights-buckwalter.html
1•reaperducer•45m ago•0 comments

Pakistan's solar revolution success is causing the national grid to crumble

https://www.bbc.com/news/articles/ckvg2n2q3103o
1•thisislife2•50m ago•1 comments

Waymo Pulls Its Cars from All U.S. Freeways Temporarily

https://www.nytimes.com/2026/11/17/us/waymo-ban-california-freeway.html
8•mikeocool•59m ago•0 comments

The Tech Leadership Blueprint: a practical handbook for engineering leaders

https://www.amazon.com/Tech-Leadership-Blueprint-battle-tested-organizations-ebook/dp/B0HRHWZ4JC
5•ricardovano•1h ago•3 comments

Opus 5.5 is not more expensive than Qwen4 Max

https://hominis.eu/blog/effort-levels/
2•Topfi•1h ago•0 comments

Building Always-On Agents

https://claude.com/resources/articles/building-always-on-agents
1•bluesnowmonkey•1h ago•0 comments

NSA's classified internal network reportedly goes offline

https://www.bbc.com/news/articles/cqvg2mg8g0pyo
4•Lyngbakr•1h ago•0 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