vault backup: 2025-08-31 16:39:44

Affected files:
.obsidian/workspace.json
fleeting-notes/2025-08-30.md

Author: chiubaca

.obsidian/workspace.json

@@ -191,10 +191,10 @@
   },
   "active": "7dfc68670be31672",
   "lastOpenFiles": [
+    "fleeting-notes/2025-08-23.md",
     "fleeting-notes/2025-08-30.md",
     "fleeting-notes/2025-08-27.md",
     "fleeting-notes/2025-08-04.md",
-    "fleeting-notes/2025-08-23.md",
     "conflict-files-obsidian-git.md",
     "permanent-notes/media-server.md",
     "permanent-notes/whats-installed-on-my-macbook.md",

fleeting-notes/2025-08-30.md

@@ -4,6 +4,6 @@ tags:
   - cloudflare
 ---
 
-cloudflare workers are fast becasue they run on V8 isloates which are similar to AWS to lambda, but way faster . v8 islolates take 5ms to be created vs lambsas which can take up to 800ms
+Cloudflare workers are fast because they run on V8 isloates which are similar to AWS to lambda, but way faster . v8 islolates take 5ms to be created vs lambsas which can take up to 800ms
 
- worker are cheaper than lambdas becasue you're only billed on execution time ,whereas lambda are charged on total running timeS. This is a big point for AI applications, as most of the time when calling models is waiting for the LLMs to respond.
+ Cloudflare workers are cheaper than lambdas because you're only billed on execution time, whereas lambdas are charged on total running time. This is a big point for AI applications, or any applications which has long waiting times. Lambdas are not efficient or optimised for these types of applications but CF workers are