It got pushed a couple sprints and we've got it on the plan for next quarter as long as no new features come in before then.

Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety.

Isn't replit more for vibe coding and Cluade Code for actual coding? They seem like very separate products.

Even though I don't use DBOS, that blog post is gold.

For a project with minimal users, we get a lot of DBOS posts.

Why such negativity? What have you shipped?

I think this post is riddled with bots. One is marketing another competing offer, others complaining about the UI component not being open source too...

We may be a small startup, but we're growing fast with no shortage of production users who love our tech: https://www.dbos.dev/customer-stories

Not really.

https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu... - Not even 3 full pages worth over the past 5 years, though the first page is entirely from this year. It's maybe 2-3 a month on average this year, and a lot are dupes.

https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que... - Nim, for comparison, which doesn't really make a dent in the programming world but shows up a lot. The first 15 pages covers the same time period.

I have a Luggable and love it! So quiet and yet loads of airflow!

They're definitely amazing for the price. I like that you can do quick back and forth with them. but they're not very smart. When I need something to actually analyze or write good code and not just refactor and move things around, they're not good for that.

Agreed. For harder tasks, I like to go to GPT 5 thinking mode, but I'm considering other options.

Some times I've had faster success with some of the larger Qwen3 models (480B and 235B variants). I like them in combination with the Repomix CLI to copy an entire project into context and get a response very quickly with some of the accelerated providers like Cerebras.

Maybe it's verbose internally? When I run it, it's just extremely fast. So the verbosity doesn't seem to affect things.

High read/write and low-ish size. Also it's faster.

> High read/write and low-ish size. Also it's faster

You posted a vague and meaningless assertion. If you do not have latency numbers and cost differences, you have absolutely nothing to show for, and you failed to provide any rationale that justified even whether any cache is required at all.

At 10k RPS you'll see a significant cost savings with Redis over DynamoDB.

ElastiCache Serverless (Redis/Memcached): Typical latency is 300–500 microseconds (sub-millisecond response)

DynamoDB On-Demand: Typical latency is single-digit milliseconds (usually between 1–10 milliseconds for standard requests)

> At 10k RPS

You would've used local memory first. At which point I cannot see getting to those request levels anymore

> ElastiCache Serverless (Redis/Memcached): Typical latency is 300–500 microseconds (sub-millisecond response)

Sure

> DynamoDB On-Demand: Typical latency is single-digit milliseconds (usually between 1–10 milliseconds for standard requests)

I know very little use cases where that difference is meaningful. Unless you have to do this many times sequentially in which case optimizing that would be much more interesting than a single read being .5 ms versus the typical 3 to 4 for dynamo (that last number is based on experience)