Now if I train a foundation models with docs from library of Alexandria and only those texts of that period, I would have a chance to get a rudimentary insight on what the world was like at that time.

And maybe time shift further more.

I guess you can freeze some compiler options to give you consistent results.

Now, a hacker/state who has penetrated a device can do an upload of data from the local decice to a CNC server.

But that seems risky as you need to do it again and again. Or do they just get into your device once and upload everything to CNC?

Seems like jumping right into the code can be a bit overwhelming if you have no background on the topic.

Very new to these APIs and their usages.

Would it not be appropriate to extend the compiler for visualising relationships between software components with zoom-in and zoom-out facilities. Zoom-in takes you to Assembly and zoom-out to the CTO.

It solves a problem that others have not solved. Which problem is that? And how better does it work than whatever there was?

>non-sharded, strict serializable, fault tolerant, key-value store that supports point writes, reads and range reads.

k-v store, non-sharded, fault tolerant, reads and range reads. Redis has these.

>strict serializable

Redis's single threaded model does this (maybe, not entirely sure).

Please help me understand why is this comparison orthongonal or does it really replace redis in ways that I don't understand.

Nginx eixsts, why do I need to learn caddy?

Redis exists, why do I need to learn FundationDB?

>I needed a quick and easy web server

I am trying to reason with what I know, but wouldn't something like "python -m http.server 9000" suffice? Or nginx? These are battle tested and python is there on most platforms.

Or is there more depth to this specific web server that others don't have?