Recent submissions

Comment · 3 days ago
I used to use an older, more expensive version from FormLabs in my last company to print our (more accurate) version of Invisalign negatives, and we'd thermoform the aligners over the top of the cured resin (with a barrier).

The accuracy was great. They'd hold up. Printing took a while, but generally pretty solid as we scaled from in-house to full lab setup. They're great as resin printers go.

Comment · 11 days ago
Not really. Anthropic’s headcount isn’t huge, and only a subset of their employees are working on the frontier. It’s also easier when you’re a follower.
Comment · 1 month ago
Yes, this is the same as buying a unit and renting as in my original post.
Comment · 1 month ago
No, it doesn't. It states that if a landlord has 3 houses and exits the landlord market, those houses are either kept unused or sold and are available for new buyers.
Comment · 1 month ago
Small landlords don't own apartment buildings. They buy houses/units to rent, lowering availability for buyers. So, you'd at least want to look at the number of new apartment rentals available plus the number of first time house buyers to get a better picture.
Comment · 1 month ago
Sam is not an asshole. His twitter is great, he's definitely opinionated, and if you haven't had the luck of meeting him you might misread his tone as grumpy. It's not. It's sarcastic/dry humour and honest.

They build good stuff and care.

Comment · 2 months ago
Iroh seems more comparable to an L7 scoped Tailscale than it does IPFS. It's good, but pretty unrelated.
Comment · 3 months ago
indeed, every ~week with essentially the same thing: skip locked.
Comment · 7 months ago
Vitess was made by a... US tech company?
Comment · 7 months ago
Inngest's Durable Endpoints aim to solve the durable API problem without messy DB txns, all within some tolerance: https://www.inngest.com/docs/learn/durable-endpoints.

Other than that, yes, durable execution does all of this for you.

TLDR on Durable Endpoints: you can automatically use steps in API endpoints which checkpoint state in the BG, and then retry on failure. This means you can run jobs in the background _somewhat_ transactionally (somewhat because there's delay between checkpointing) to minimize any tradeoffs here. And, if you want full transactionality, don't buffer checkpoints in the BG and instead do it synchronously.

Also, Redis is good for medium scale load. We're hitting millions of RPS (aggregated) on our services (I work at Inngest) and it doesn't scale so well at this load, at all. We had to invest in other infra.

Comment · 8 months ago
AWS is down and so being a reseller ofc Vercel is down too.
Comment · 8 months ago
IDK, it looks like servers were up, connectivity worked well, and some builds were failing. Wouldn't call that a big issue, and the same thing was happening with Vercel due to their git clones etc. yesterday too.

IOW, doesnt look as bad as the title suggests?

Comment · 9 months ago
> And people die all the time.

Yes... but people can only focus on one thing at a time. We don't have 360 vision. We have blind spots! We don't even know the exact speed of our car without looking away from the road momentarily! Vision based cars obviously don't have these issues. Just because some cars are 100% vision doesn't mean that it has to share all of the faults we have when driving.

That's not me in favour of one vs the other. I'm ambivalent and don't actually care. They can clearly both work.

Comment · 10 months ago
If you're testing the interface, changing the implementation internals won't create any churn (as the mocks and tests don't change).

If you are changing the interface, though, that would mean a contract change. And if you're changing the contract, surely you wouldn't be able to even use the old tests?

This isn't really a go problem at all. Any contract change means changing tests.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton