Lobsters's Avatar

Lobsters

@lobste.rs.web.brid.gy

[bridged from https://lobste.rs/ on the web: https://fed.brid.gy/web/lobste.rs ]

31 Followers  |  0 Following  |  1,922 Posts  |  Joined: 17.11.2024  |  1.1745

Latest posts by lobste.rs.web.brid.gy on Bluesky

Preview
Nixpkgs module system config modules graph Comments
07.08.2025 16:44 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
More shell tricks: first class lists, jq, and the es shell Comments
07.08.2025 16:01 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
Jepsen: Capela dda5892 Comments
07.08.2025 14:44 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
hardmode-triangle-0 Comments
07.08.2025 11:29 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
Forsp: A Forth+Lisp Hybrid Lambda Calculus Language Comments
07.08.2025 08:03 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
Preview
RFC 9457 - Problem Details for HTTP APIs I found this RFC referenced in the docs of Litestar (https://docs.litestar.dev/latest/usage/plugins/problem_details.html – via https://lobste.rs/s/xoyolt/litestar_is_worth_look), and found it to be an interesting take on error handling. It reminds me of an all job where the rule was that all user-visible errors must have proper documentation and instructions for the user on how to go about resolving them (even if often the solution was to contact your admin). I think the idea can apply not just to HTTP APIs. I prefer it to generic exceptions that usually describe only the immediate error (some file not found let’s say) but don’t provide enough context about where the incorrect inputs are coming from and how to resolve the issue. Comments
07.08.2025 06:26 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
Preview
HTTP/1.1 must die: the desync endgame Comments
07.08.2025 02:21 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
Preview
LF AI & Data Foundation Hosts Vortex Project to Power High Performance Data Access for AI and Analytics Comments
06.08.2025 21:18 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
zig-error-patterns Comments
06.08.2025 15:01 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
Preview
Why hx-boost is actually the most important feature of htmx Comments
06.08.2025 14:13 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
The how and why of GitHub to Codeberg Comments
06.08.2025 11:50 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
Preview
Why are Windows semiannual updates named H1 and H2? Comments
06.08.2025 08:14 β€” πŸ‘ 0    πŸ” 1    πŸ’¬ 0    πŸ“Œ 0
Rethinking devtools: Escaping the Cloud and SaaS trap Just thinking out loud. If not for a gazillion other reasons, a recent outage from Postman should remind us again why proper design decisions matter in devtools. API workflows shouldn’t live in the cloud. A LOT of devtools shouldn’t live in the cloud. Some tools can’t work without it, all good. But a whole lot of them are there just because of some poor design choices. Yet… * No cloud? No outage. * No cloud? No sync issues. * No cloud? No data security gaps. So why keep forcing it where it doesn’t belong? And it’s not even just the cloud. Cloud is awesome for some stuff. SaaS-like designs are dragging devtools into the same trap. As a matter of fact, devtools in general shouldn’t feel like SaaS platforms. Unless we’re going through app usage dashboards - tabs, and mouse actions are not built for devs. Devtools should prioritize developer control, not just pay-per-seat subscriptions. P.S. No need to send me Postman alternatives. I already work on building an awesome one, but chose not to promote it in this post.
06.08.2025 07:00 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
Preview
cosmopolitan: build-once run-anywhere c library Comments
06.08.2025 01:06 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
Be Careful with Go Struct Embedding Comments
06.08.2025 00:11 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
Have you ever regretted open-sourcing something? Inspired by: https://news.ycombinator.com/item?id=44766771
05.08.2025 19:38 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
Preview
Gleam v1.12.0 released Comments
05.08.2025 18:07 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
Preview
Quickshell, building blocks for your desktop Comments
05.08.2025 16:17 β€” πŸ‘ 0    πŸ” 1    πŸ’¬ 0    πŸ“Œ 0
Preview
Lisp interpreter with GC in 662 lines of Odin (and <500 lines of C) Comments
05.08.2025 06:50 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
What trick of the trade took you too long to learn? I really liked this question from https://news.ycombinator.com/item?id=44789068
05.08.2025 04:45 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
Markdown Monster Comments
04.08.2025 22:16 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
p-fast trie: lexically ordered hash map Comments
04.08.2025 21:00 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
Preview
The Generativity Pattern in Rust Comments
04.08.2025 18:07 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
Introducing luzer, a coverage-guided Lua fuzzing engine Comments
04.08.2025 15:46 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
How we made JSON.stringify more than twice as fast Comments
04.08.2025 14:09 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
Rust, Python, and TypeScript: the new trifecta Comments
04.08.2025 10:33 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
More retrocomputing, less nostalgia Comments
04.08.2025 09:13 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
So you want to parse a PDF? Comments
04.08.2025 03:08 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
Preview
The Q Programming Language Comments
04.08.2025 02:53 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0
Preview
a parser for typescript types, written in typescript types Comments
04.08.2025 02:10 β€” πŸ‘ 0    πŸ” 0    πŸ’¬ 0    πŸ“Œ 0