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?

> food is painfully bland

You mean like... not invested with tons of sugar? What kind of bland are we talking about?

It's time to stop.

Kysely looks like the thing most people would want. It's not a full ORM though - just a well-typed query builder.

https://kysely.dev/

Pretty sure the maintainer is also a Discord mod.

DRY is by far the most overrated software engineering principle and constantly pushing for it only leads more developers down the way of creating wrong, irreversible abstractions.

"Can't" as in "don't want to"

Sir, watch out! Your monocle is about to drop into the scotch!

Date guys. Problem solved.

I don't get why GitHub doesn't adopt it and make it a standard. Especially the lack of caches is annoying.

Funny, I also thought of Vue immediately.

Can we agree on not posting anything directly from twitter? It's absolutely useless without an account.

Or you use the correct types and avoid these "problems" alltogether.

It's not possible to bake in a cold oven. Why does your type allow it then? Why don't you encode the state directly?

  oven := ColdOven.heat()
  bakedPizza := oven.bake(pizza)

As a 13 year old, I can confirm that we always mention our age before anyone asks.

> ... it's not intuitive how deep I am within nested scopes

The ONLY piece of information that is available to you regardless of how deep you are into a function is INDENTATION. Your curly braces won't help you.

Besides that, you should seriously reconsider your coding style if this is an actual problem for you.

Indentation provides visual structure. Matching braces hardly add value to it.

It will always stay "Twitter" simply because you cannot use a search engine with "X"

why?