kSPvhmTOlwvMd7Y7E

Even something as ubiquitous as JSON is not handled in the same way in different databases, same goes for Dates, and UUID. I am not even mentioning migrations scripts. As soon as you start writing raw SQL, I pretty sure you will hit a compatibility issue.

I was specifically talking about python, can't argue with golang. OK you have a valid point for performance, gotta keep an eye on that. However, I am satisfied for our CRUD api

and how you run your tests? Do you spawn a DB backend for test purposes?

You don't even mention the 2 main advantages:

• ORM lets you to use plain objects over untyped strings. I take typed anything over untyped anything, everyday
• ORM lets you to use multiple database backends. For ex, you don't need to spawn a local postgres server, then clean/migrate it after each test suit, you can just use in-memory sqlite for that. OK this has some gotchas, but that's a massive improvement in productivity

Advertisement is a fucking syphilis, a cancer and a gangrene combined. Don't tell me what to watch what to visit

Unfortunately sometimes the code base is fuckd up beyond repair, it can't even be tested. that's why i submitted 3000 line PR ☠️

All IO related stuff should be a replaceable dependency

But this is very readable tho

Aw, of course, go ahead Microsoft's OCaml, we ll definitely visit you

It's not "every system" which proves all truth is inconsistent right? Propositional logic, and first order logics are both sound, and complete. The article talks about propositional logic, so in my understanding, it should be complete and sound too.

fair enough.

Why every class creates its own logger? That might make sense, but looks suspicious

Use global imported variables for configs.

it's «la torture» tho …