164 karma · joined August 24, 2023
It seems that you cannot, in one database call, make a transaction?
You would need to push your transfer to the depot, then poll until it has been accepted.
If you do not poll, then your transaction may be written but as a no-op.
Does this increase latency for such applications?
indexes = function(data)
query = function(indexes)
How does this model a classic banking app where you need to guarantee that transfers between accounts are atomic?Really? I never had problems using some JVM base image and deploying via a Docker image, which is what I would be doing anyway.
Have you tried to do this in Python?
A Node comparison would be more appropriate.
If every did their neighbor's laundry (say) and charged a fee, then everyone would be doing the same amount of laundry and have the same amount of money, yet GDP would rise?
Why does that require deep clones?
I simply do:
return {
...current
foo: "bar"
};What's the use-case?
Is it impossible to prove memory safety in the general case due to the halting problem?
As for maintainability, it's not clear to me that reams of imperative code is easier to maintain than something terse and declarative. In fact, probably the opposite.
I have high hopes that models will end up a bit like Linux servers, where everyone is building on open foundations.
Would they? The history of programming is full of great ideas that took a very long time to reach mainstream adoption. We also did some things that in hindsight were bad ideas, but for a time were very popular.
This is because the programming language "market" is not rational. It moves at the speed of education, not the speed of innovation. People learn a language and they make useful things with it. Why would they stray into niche languages and PL research?