frodowtf

Fascinating how Cuba is still standing in spite of all embargoes.

... the obligatory "historical context" nobody asked for.

If you want to use this pattern, you'll probably end up with a lot of duplicated code e.g. for SQL query builders. I could imagine that Rust makes this kind of pattern easier due to traits and macros. A lot of languages do not have these features.

And then of course Rust people care about correctness more in general.

It also seems to have the same concurrency issues as described in the article. At least from my experience the "database is locked" error appears quite often.

Usually, I go with openapi-generator and pick the typescript-fetch template. You can use that with whatever js-based frontend framework you want.

> writing a lot of boilerplate code to connect the frontend and backend.

OpenAPI. django-ninja supports it out of the box.

> ... very low user adoption of Home Screen web apps.

Well, if nobody wants to play with our total clusterfuck of inconsistent APIs, we might as well drop support for them >:(

so why is nobody implementing stuff in smalltalk?

Well, that comment is definitely "masculine"

As long as casinos are a thing, Bitcoin stays a thing.

Well, I don't.

`panic` has nothing to do with error handling though. If you use it, you know that your callers cannot recover from it.

Throwing an exception implicitly delegates error handling back to the caller, but they are not even notified about it. (talking about OCaml)

People say that OCaml is like Rust, but unlike Rust, OCaml has Exceptions that could appear everywhere. How is that safe?