dhfuuvyvtt

The real test for AGI is if you put a million AI agents in a room in isolation for a 1000 years would they get smarter or dumber.

What's that got to do with microservices?

Edit, because you can avoid those things in a monolith.

See ya Cindy.

Literally Amazon marketplace.

Palestinian "news outlets".

Typescript doesnt blow up when someone passes a legacy assumption into a static typed area of dynamic code.

I've seen too many bugs with PHP static typing for it to be worth it in mature systems. It's great in greenfield, but yeah, old code is hard to work it into unlike typescript which tends to be more forgiving. Though, I will say, typescript is just as viral if not more so.

What makes them happy and what is the best outcome for them in the long run can be different things. Did you read the article?

Takes me around an hour or so to restore a 2tb drive from a HDD NAS with borg. Wasn't a full 2tb, and I might be off by an hour or so as it's been a minute. Usually I dd from the old drive to the new one over USB which doesn't take too long 30-40 minutes?

Why is a tailwind palette generator tailwind?

Its probably to be consistent across each platform, MySQL doesn't support named queries so they are likely avoiding using them for that reason, either that or the docs are old. :)

I'm not sure that's an issue? It would be an odd refactor to add a new side effect to the query you didn't want to apply across the board.

More likely you would introduce a new query that would get a new function call.

usersWithCountBetween(a, b)

vs

enabledUsersWithCountBetween(a,b)

If you mean, how to handle the addition of a new enabled flag that is passed in, that too would either require refactoring or a new function.

These aren't really things I would consider a problem but maybe I'm missing something?

Oh and you can configure the number of params before it replaces the params with an interface so things like this are easier to manage over time.

Simple queries aren't any easier with ORM, that's the point of sqlc, you write the SQL and then call it as a function. There's no extra abstraction or added steps on top.

Repeating portions of sql isnt really an issue for me either, it's the business end of the database, you want it all there in one location, spreading it around in a composible fashion is just one abstraction too far. I know SQL, I don't want to learn anything else on top.

SQLc isn't just raw SQL.

SQLc you write the queries, it generates the boilerplate functions to execute them.

This works better than an ORM because you don't have to deal with an ORM.

If you're writing a lot of dynamic queries I think you should opt for a query builder, not an orm.

For me, I write almost nothing but static queries, SQLc is just so much nicer to use.

I don't mind having to do the odd dynamic query from scratch.

I just wish sqlc supported named Params in MySQL, the resulting function param ordering is a little annoying.

And then there's me: never left the datacenter in the first place.

Precedent is the win, not the fine.

Now anyone can file the same suit and they'll need to settle.

Because they keep turning out to be true?