Funny, this mirrors almost exactly a decision I made after about a year of struggling with ELPA packages breaking on me repeatedly.
I ended up cutting Emacs off from ELPA entirely, settled on a ~700-line init.el, and now use Emacs as a glorified Org-mode agenda keeper. It's been heavenly (especially with a dedicated monitor).
The one thing I'm still working out is syncing with calendars and email.
Interesting. I use ELPA/MELPA all the time and find things pretty stable for my own uses. Surprisingly so, in fact. I honestly expected more hiccups. I wonder whether itβs differences between the packages that we use or the complexity of the configuration or what. Mostly I spend my time in Clojure mode with CIDER and Magit. Iβm not trying to run email and calendar in Emacs.
I can imagine a camera-based input that would help detect the wagging of a tail, or continued interest in the visuals as an indicator of doubling-down on a given feature.
The dog could actually vibe code a game to their liking, but with the wrong input (a keyboard) it's a missed opportunity.
HN has been a wonderful source of both news and community - it connected me to my industry in ways that could only have been achieved otherwise by moving to SF or NYC.
In a way, it feels like a great continuation of my Slashdot years.
I get pulled into a fair number of "why did my AWS bill explode?" situations, and this exact pattern (NAT + S3 + "I thought same-region EC2βS3 was free") comes up more often than youβd expect.
The mental model that seems to stick is: S3 transfer pricing and "how you reach S3" pricing are two different things. You can be right that EC2βS3 is free and still pay a lot because all your traffic goes through a NAT Gateway.
The small checklist I give people:
1. If a private subnet talks a lot to S3 or DynamoDB, start by assuming you want a Gateway Endpoint, not the NAT, unless you have a strong security requirement that says otherwise.
2. Put NAT on its own Cost Explorer view / dashboard. If that line moves in a way you didnβt expect, treat it as a bug and go find the job or service that changed.
3. Before you turn on a new sync or batch job that moves a lot of data, sketch (I tend to do this with Mermaid) "from where to where, through what, and who charges me for each leg?" It takes a few minutes and usually catches this kind of trap.
Cost Anomaly Detection doing its job here is also the underrated part of the story. A $1k lesson is painful, but finding it at $20k is much worse.
Hey, just a friendly reminder that this is HackerNews, not The Lancet.
I have seen past comments here debating many relative basic concepts on medicine. Please don't take medical advice from engineers. Drink water, exercise, eat well. Otherwise seek medical advice from a doctor.
You just opened my eyes to IMSLP and I would like to thank you for that. For years I have been chasing music scores that were just the right level for my kids.
Hard to believe it's been 27 years. I remember when it was still in beta, and how exciting it was to have an open source alternative to Internet Explorer.
I ended up cutting Emacs off from ELPA entirely, settled on a ~700-line init.el, and now use Emacs as a glorified Org-mode agenda keeper. It's been heavenly (especially with a dedicated monitor).
The one thing I'm still working out is syncing with calendars and email.