I would be lying if I said that I was a professional Ocaml developer.

I do definitely think the Jane's library is very hard to read... But that might be my inexperience

I personally think regular, procedural code is much easier to read ¯_(ツ)_/¯

If you want to read some monads in the wild, go check the code for Jane's Street "core_unix.command_unix"

Otherwise, GADT, but they are used sparingly because they make type inference undecidable

Sorry to that guy, but Python is a terrible choice for GUI. It simply doesn't even exist in the wild, except in newbies' minds. You should pick something that allows you to* easily & immediately* reload your GUI in progress without restarting the program; AND also maybe think about how to distribute your GUI on other computers without requiring them to duplicate your python setup

Meh. He s wrong and he knows it. Computer science is definitely about efficient use of computational resources and memory.

React +python + postgres/sqlite

We have a solution

Did they pay every news outlet out there to publish stupid titles? That's not a fucking apology. Stop pretending

Your last question is equivalent to : why there so many math theories? Can't we just reuse the old ones?

New language appear as a natural product from research in type theory for ex

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

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 …