Lobste.rs

1

Jujutsu support in Reviewboard (reviews.reviewboard.org)

submitted 7 minutes ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

We were considering migrating repos at $JOB to Jujutsu, but the lack of support in Reviewboard was a showstopper. I guess we have no excuse now. Comments

2

TUI version of dmidecode tool (github.com)

submitted 57 minutes ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

Comments

3

1

RFC 9457 - Problem Details for HTTP APIs (datatracker.ietf.org)

submitted 2 hours ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

I found this RFC referenced in the docs of a web framework (Litestar; https://docs.litestar.dev/latest/usage/plugins/problem_details.html), 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

4

2

onion-lang (github.com)

submitted 3 hours ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

Comments

5

1

Reasoning about systems' state spaces (youtu.be)

submitted 5 hours ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

Comments

6

1

HTTP/1.1 must die: the desync endgame (portswigger.net)

submitted 6 hours ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

Comments

7

2

What Happens When You Start Panic!ing (www.youtube.com)

submitted 10 hours ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

Comments

8

1

One Billion Row Challenge (2024) (curiouscoding.nl)

submitted 10 hours ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

Comments

9

1

An easy-to-implement, arena-friendly hash map (nullprogram.com)

submitted 10 hours ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

Comments

10

1

uBlock Origin Lite for Safari (mjtsai.com)

submitted 10 hours ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

It’s finally here, thanks Raymond Hill! Comments

11

1

LF AI & Data Foundation Hosts Vortex Project to Power High Performance Data Access for AI and Analytics (www.linuxfoundation.org)

submitted 10 hours ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

Comments

12

2

Litestar is worth a look (www.b-list.org)

submitted 12 hours ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

Comments

13

0

Out-Fibbing CPython with the Plush Interpreter (pointersgonewild.com)

submitted 9 hours ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

Comments

14

1

Implementing Viewstamped Replication protocol (2023) (distributed-computing-musings.com)

submitted 12 hours ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

Comments

15

4

70 Companies You Didn't Know Were Using Rails in 2025 (thoughtbot.com)

submitted 20 hours ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

Comments

16

3

The how and why of GitHub to Codeberg (www.arscyni.cc)

submitted 20 hours ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

Comments

17

1

zig-error-patterns (glfmn.io)

submitted 17 hours ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

Comments

18

1

Scaling Correctness: Marc Brooker on a Decade of Formal Methods at AWS (podcasts.apple.com)

submitted 17 hours ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

Comments

19

4

The wall confronting large language models (arxiv.org)

submitted 1 day ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

Comments

20

1

Why hx-boost is actually the most important feature of htmx (dev.to)

submitted 18 hours ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

Comments

21

2

Bag of words, have mercy on us (www.experimental-history.com)

submitted 21 hours ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

Comments

22

1

Project Ire autonomously identifies malware at scale (www.microsoft.com)

submitted 21 hours ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

Comments

23

1

What's new in Gleam 1.12? (video walkthrough) (www.youtube.com)

submitted 21 hours ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

Comments

24

1

Python performance myths and fairy tales (lwn.net)

submitted 23 hours ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

Comments

25

1

Rethinking devtools: Escaping the Cloud and SaaS trap (lobste.rs)

submitted 1 day ago by rssbot@lemmy.bestiver.se to c/lobsters@lemmy.bestiver.se

0 comments fedilink

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.