it was called "Slow arse". This was because it was rather reluctant in handing out resources (memory fe).
Having fought it, I remember the system APIs being really well defined and picky (which was good). At one point, the C compiler had some identity issues "am I 32 bit, or 64 bit?"
pattern is there: first hit a public place (market, ...), then when people are scrambling to help, hit them again. "double-tap".
Seen in Gaza, Ukraine, Syria, Yemen, ...
It's quite cynical, the topic has its own Wikipedia page:
yes. but most of it is not to other countries. Most government debt (over 80% globally) is privately owned through sovereign debt instruments like bonds.
Humans are so good at pattern recognition it's uncanny. Back in the modem days, most people automatically recognised the most important phases of downloads because of the way they sounded .
I have the same. I'm looking at my laptop's screen as I type this, and if I close my eyes while typing I cannot even visualise said screen. Now, I can blind-type, recognise faces, navigate aso without any problem. I can even play chess quite well (fide ~2050, 2200 blitz on chess.com), but I cannot visualise a chess board, nor can I visualise my moves or the moves of my opponent.
However, I don't "see" (pun intended) it as a problem. On the contrary, I'm not wasting cycles on irrelevant details while I'm thinking.
If it makes you feel any better, I'm on the hyperphantasia end of the spectrum and it is honestly actively problematic sometimes. For me, it can be very difficult to work with things that I can't translate to visuals, mentally; and daydreaming, and memories can be so vivid they are distracting or disturbing. It's very much an asset in certain circumstances (like debugging code or fixing an engine), but there's a reason most people don't have that fidelity.
One of the problems with running the application code inside the database server is that you need to make application developers use the programming language(s) you prepared for them. The other is that you need to trust them to not do crash out, or do infinite loops. Good luck moving application developers from their choice into the right choice.
This is easy to fix. The SpacetimeDB folks could just add a phase to analyze the application developer’s code before running it to prove that it will definitely halt.
This is why you need to compile your code for spacetimedb to WebAssembly and it runs inside a VM. Use the language of your choice, and assume the code is only semi-trusted with the ability to have a watchdog. That part makes sense.
reply