frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Claude's Workbench – Claude architects and reviews, local LLMs write the code

https://github.com/a-schaefers/claudes-workbench
1•telecommuter•4m ago•0 comments

Synty Studios Joins Unity, Bringing Artist-Made Assets to Unity Spark

https://unity.com/blog/synty-studios-acquisition
1•gmjosack•5m ago•0 comments

Apple Just Added Face Unlock to iPhone Duo

https://www.macrumors.com/2026/11/16/iphone-duo-face-unlock-hands-on/
1•mgh2•7m ago•0 comments

In the Age of A.I. Slop, a Montebello Metalhead Still Proudly Draws Art by Hand

https://lataco.com/black-metal-punk-album-art
1•cdrnsf•8m ago•0 comments

DOJ to review DoorDash-Instacart merger

https://www.reuters.com/world/doordash-instacart-merger-be-reviewed-by-doj-sources-say-2026-11-16/
1•JumpCrisscross•8m ago•0 comments

Apple Watch and Garmin are so wrong! How many calories do you burn in a day?

https://macrocodex.app/knowledge/rethink/how-many-calories-do-you-burn-in-a-day-apple-watch-and-g...
1•faangguyindia•12m ago•0 comments

Show HN: Win98 PE Interpreter in WebAssembly – StarCraft and Diablo on Phones

https://wine-assembly.berrry.app/
1•vgrichina•13m ago•0 comments

Meta would 'consider' pulling services from Canada if lawful access bill passes

https://www.cbc.ca/lite/story/9.7424473
2•colinprince•15m ago•2 comments

Show HN: Omnistew – 3D multiplayer RTS written in Rust, playable in a browser

https://omnistew.io/
1•omnistew•16m ago•0 comments

The AI Ascent

https://medium.com/@chipmunkworks/the-helicopter-problem-9bfec2cfdfab
1•treelover•18m ago•1 comments

Geographic Data Science with Python

https://geographicdata.science/
1•teleforce•19m ago•0 comments

Claude Is Always Right

2•KenPainter•19m ago•2 comments

Habits PhDs Must Unlearn to Build a Startup [video]

https://www.youtube.com/watch?v=u-8KpXcPYCw
1•gmays•24m ago•0 comments

Claude Mythos slashed software work to onboard AMD GPUs to around three days

https://www.tomshardware.com/tech-industry/artificial-intelligence/anthropic-says-claude-mythos-s...
2•nsoonhui•28m ago•0 comments

Show HN: 1.499x speedup and 28.5% dynamic energy drop on A40 via BF16 tiling

https://cwtractors.com
3•ktractor123•32m ago•0 comments

Are forensic experts biased? Scientist's claims spark outrage – Science – AAAS

https://www.science.org/content/article/forensic-experts-biased-scientists-claims-spark-outrage
2•wglb•39m ago•0 comments

The Weather at Home

https://alexhowells.com/writing/the-weather-at-home/
3•nixgeek•39m ago•0 comments

Show HN: Fundlark-open source tool help early-career researcher find funding

https://github.com/dryang21/Fundlark
1•dryang21•42m ago•0 comments

It's ok that computers are (sometimes) better than us

https://stackoverflow.blog/2026/10/30/it-s-ok-that-computers-are-sometimes-better-than-us/
2•mooreds•43m ago•0 comments

Nvidia rules out Jensen Huang comeback as campaign for his return grows

https://www.reuters.com/legal/transactional/silicon-valley-leaders-back-call-jensen-huangs-return...
2•A_D_E_P_T•44m ago•0 comments

Running coding agents without handing them my credentials

https://blog.antonio.cx/running-agents-with-lend
10•antoniomika•45m ago•2 comments

Friselle: The ingenious Italian bread that can last for a year

https://www.msn.com/en-ca/food-and-drink/recipes/friselle-the-ingenious-italian-bread-that-can-la...
5•BiraIgnacio•45m ago•0 comments

Show HN: Free weekly backups for Supabase Free projects (pg_dump to R2)

https://github.com/liulewis/supabase-free-backup-lite
1•agricalc•50m ago•0 comments

Own your AI, at full speed

https://www.ycombinator.com/launches/XcZ-rightnow-own-your-ai-at-full-speed
5•Jr23_xd•50m ago•0 comments

My Annoying Coworker Claude

https://sharamp.com/personal/claude/
1•BrokenMirror•52m ago•0 comments

Old SaaS Model Is Dead. Software Is a Plug-In. The Hard Part Is Getting Picked

https://www.thestateofai.com/news/saas-is-dead-software-plug-in-ai-assistants
2•Gaishan•52m ago•0 comments

Collisions in Hash Functions

https://collisions.zksecurity.xyz/
1•baby•53m ago•0 comments

The Cyanotype Network

https://network.studiowetware.com/index.html
2•Beachkilla•54m ago•0 comments

TimesFM-3: A zero-shot foundation model for multivariate forecasting

https://research.google/blog/timesfm-3-a-zero-shot-foundation-model-for-multivariate-forecasting/
4•gmays•55m ago•3 comments

Gemini Decision 1 can't separate AI voices made after 2024

https://echo.ls/posts/gemini-decision-ai-voices/
1•maplet•56m 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