Regarding the "Durable Queueing Tradeoffs", doesn't Kafka prove you can be both durable and highly performant?
Readit Newsmd3911027514 commented on I solved a distributed queue problem after 15 years dbos.dev/blog/durable-que... · Posted by u/Bogdanp
md3911027514 commented on 95% of Companies See 'Zero Return' on $30B Generative AI Spend thedailyadda.com/95-of-co... · Posted by u/speckx
It’s interesting how self-reports of productivity can be wrong.
For example a study from METR found that developers felt that AI sped them up by 20%, but it empirically it slowed them down by 19%. https://metr.org/blog/2025-07-10-early-2025-ai-experienced-o...
Pytype and mypy check native annotations.
Well yes but with native annotations the linter you’re already using can do a lot of the type checking work so for many teams it’s not worth it to add Pytype or mypy
Pytype was cool before Python type annotations became widespread. It seems to me like the industry is naturally moving toward native type annotations and linters and away from static analyzers like Pytype and mypy.
md3911027514 commented on OPA maintainers and Styra employees hired by Apple blog.openpolicyagent.org/... · Posted by u/crcsmnky
Isn't Styra like a company of like 50-100 people? Seems like it'd be a bummer to be an employee at the company that gets left behind.
I think we need to get back to state where we take software licenses serious in letter and in spirit. The transitions Redis made are pristine on a legal and moral level. Feeling betrayed is absolutely uncalled for.
I mean isn't lying bad? They literally made public statements saying they "will always remain BSD." https://redis.io/blog/redis-license-bsd-will-remain-bsd/
how does it take hundreds of hours to swap out a back end when you're using a trivial protocol like redis?
did you switch out the client or something? maybe the problem is not using pluggable adapters? is your business logic coupled to the particular database client API? oof.
I know the cluster clients are different (been there, done that) but hundreds of hours, seriously? or was that just hyperbole?
By switch I mean that all new projects use Valkey instead of Redis, and we've invested hundreds of hours into those new projects. We've also tried stuff with the Valkey Glide client.
Your company invested hundreds of engineering hours switching from Redis to a clean fork of Redis?
By switch I mean that all new projects use Valkey instead of Redis, and we've invested hundreds of hours into those new projects.
I very much doubt that anyone will stick with valkey after the PaaS providers switch back to just offering Redis proper.
Why would PaaS providers switch back to offering Redis? They've clearly all already invested a lot in Valkey (AWS, GCP, Heroku).