derekperkins

I appreciate you carrying the torch for MySQL here, since most opinions are based on setups over a decade old, with little to no bearing on how it runs today

"let me meet your fat fruit friends" https://youtube.com/shorts/Cp4093Dzt4E

Depends on the underlying database, and you'd have to test your query to have any level of certainty.

That being said, query planning is generally where Oracle/MSSQl outshine MySQL/Postgres, especially for pruning unnecessary joins. BigQuery is great at it IME.

Olric is awesome, we've been using it for 2 years in prod. No complaints.

If I could downvote this AI slop marketing, I would

Here's a better implementation if anyone is interested (not mine) https://github.com/puzpuzpuz/xsync#map

We've been active users of go-trafilatura and love it

I'm not sure either of those examples is true. For servers, Linux won, but that's just a fraction of OS usage. MySQL still has much higher usage rates than Postgres, particularly at massive scale, so calling that "won" is premature at best

They didn't have particularly great reasons to migrate at the time besides the team wanting to write rust. That article is just trying to provide validation

Lago continues to pretend to be OSS, when it's unusable as is. I had so much hope for it, and while I don't begrudge them monetizing, it's a sham. You can't even make a refund with the OSS license.

A frozen banana that WON'T make you sick and kill you.

https://x.com/bluthquotes/status/732749820348096512

Another maintained fork https://github.com/mailgun/groupcache

No, and no clustering / HA yet I believe. It is awesome though with the right use case. We've had it in prod for a few years now

Came here to recommend the Challenger Sale

I very much appreciate your deep knowledge of MySQL, and willingness to share amidst the sea of postgres fans. There's a reason both are popular and widely used.

Lago is mocking the very idea of OSS. You can't even issue a refund self hosted.

Change and use slog with the zap adapter

Just an egg please

Huge fans of Buf Connect. We run vanilla gRPC servers on the backend and have a typed experience through to the frontend

It also has materialized views built in so you don't have to run dbt manually

This. We're doing billions of daily usage aggregations in MySQL with generally less than 5s delay

Avoid Chargebee at all costs. I've never made an architectural decision I regretted more.

My thoughts exactly

What a fantastic article

That seems more likely to be company culture related and only slightly influenced by the language.

Anecdata: I'm a white American who grew up in China and it didn't impact me, nor in my experience most of the kids in my international school. Single adults who go back however are more likely to self select based on attraction.

Hyperswitch seems to just be payments, not billing...

You can't even refund with the OSS version. It's so hamstrung as to be completely unusable for a real business

No. In almost no circumstances will it be worthwhile to switch either direction. While people on HN love to nit-pick on the margins, the core functionality for both is 95% overlapped.

That's thrown around by people who have been around a long time, but hasn't been true by default for a decade, since 5.7 was released.