kolanos
kolanos on Hacker News
> About $2.4 billion out of this is already frozen by Circle and Tether. Some of the big ones:
How does freezing crypto work in this context?
Other providers might have better isolated KV stores?
Isn't this the most common PHP stack?
Why would someone contribute more than they are legally required?
Durable execution comes with overhead that you'll need to determine whether or not fits your use case. If you're looking for raw speed then durable workflows are going to be a steep trade off. Most workflows should be durable by default, though, so it is more the rule than the exception.
Posted by
kolanos on Sunday September 13, 2026 @12:52PM
from the twitter.com dept.
Do they get the same backlash if they went with a source available license similar to MongoDB or Elastic?
Until they solve the ~250ms latency, which would require replacing bluetooth with a lower latency option, I'm not interested.
This screw up ended up costing id Software millions in sales. With the Doom franchise they only included the first episode in the shareware version. But to save a buck I guess they decided this was better than mailing a second CD with the full game on it. Then doubling down on that greed by putting their entire game library on the disc. This is right about the time John Romero and John Carmack parted ways, can't help but wonder if this debacle played a role. And by all accounts Quake's development was painful, so imagine this happens after going through hell getting a game out the door.
Yes, this is correct. I have a distinct memory of playing Space Quest (forget if I or II) on a CGA monitor and then seeing it on my friend's EGA monitor and being blown away.
It's an LLM flooding the zone.
Agree. I've been delving deep into Rust for some personal projects, and while there are some sharp edges (that likely won't go away) the tooling, ecosystem and general ergonomics more than make up for it. Hoping I'm not in the minority of relative newcomers and that the language continues to thrive.
About a decade ago I heard John complaining on No Agenda about a sound card mixer problem he was having in Linux. I had the same model card so I emailed offering some debugging advice. He responded almost immediately and we went back and forth trying things. If memory serves it was a config issue with pulseaudio. It was the highlight of my week.
$1.7-billion isn't a mundane detail Michael!
This team could have stopped here and still had something interesting (albeit not novel) to show. But the hype cycle was too tempting.
This archive link is not working for me.
We must have joined around the same time, 17498. Funny to call us late when this would have been July 2008, or ~3 months after public launch.
Posted by
kolanos on Wednesday April 01, 2026 @12:26PM
from the sciencenews.org dept.
Was kind of expecting Jim Ross and Bobby Heenan's voices, but that would likely get you sued. Fun nonetheless.
For a little context. Salesforce changed their enterprise structure, effectively doubling their prices and my guess is many of their larger customers fled the platform. The enterprise pricing organized dynos into blocks and without notice they doubled the minimum block unit you could have. As a result, you ended up paying for dynos you weren't even using because they were now rounding up, sometimes by thousands of dollars worth of dyno blocks. So if you thought Heroku was expensive before, now it just didn't make any financial sense at all. For the other PaaS out there: don't do this.
Does this mean Keynote and Pages are now paid products? Aren't they included with Mac OS?
996 is a work schedule that derives its name from its requirement that workers clock in from 9:00 am to 9:00 pm, 6 days per week, resulting in employees working 12 hours per day and 72 hours per week.
> (Benchmarks run on PyPy 3.11, Intel i5-8365U, 8 Cores, 100 connections)
Why not benchmark Flask/FastAPI with 8 workers instead of 4 for a more apples-to-apples comparison?
China currently only holds about 2% of U.S. debt. What is the risk exactly?
Found this in their roadmap [0]:
> Managed ECS-EC2 clusters in preview
> AWS has a long standing issue with the ECS agent randomly disconnecting, resulting in orphaned EC2 instances which can cause traffic or deployment degradation.
> We have attempted to solve this a few ways in the past, but there were still critical edge cases falling through.
> So we bit the bullet, and developed a robust, full featured ECS cluster management solution to solve this problem once and for all.
> It's currently in private preview. To get early access before we roll it out to everyone, contact support.
I found elsewhere in the Flight control docs where they recommend ECs+EC2. While I'm not surprised to hear about issues with ECS+EC2, given the reported issues above I don't know if I'd recommend it in my docs. Fargate is a far better option for most use cases, at least in my experience. Unless you need specialized instance types, like GPU workloads.
[0]: https://roadmap.flightcontrol.dev/changelog