Okay, so #1) Fleek Functions are a kind of serverless function which lives on a blockchain. That means they execute on other people's computers. Think of them as Lambda functions without the involvement of Jeff Bezos
https://fleek.xyz/docs/platform/fleek-functions/
#fleek #fleekxyz #blockchain #lambda #aws #cloud #functions #serverless #fleekNet #fleekNetwork #ipfs #webDev
#2) these functions can be made public, like a common library.
For example; you know how there are a million HackerNews clients, and they all hit the same API? Imagine if someone published a function that fetches HN comments or whatever, and then anyone could use that function in their own app!
AWS isn't this ambitious; they don't mind if everyone has to implement their own fetchHackerNews function.
#3) the code for #FleekFunctions lives on IPFS, which means it's public, which means that people can view-source your backend!!! 🤯
So, I'm thinking; what if I build polyfill.io, but on the Blockchain! Hey come back..
Hear me out; #fleekfunctions are immutable, and transparent. So long as the #fleeknetwork nodes can be trusted to execute the code properly (I presume there are cryptographic guarantees of output validity) then it could be safer from supply chain attacks.
#webDev #polyfillio #polyfill #supplyChain #hacking #web3 #blockchain #fleek #javaScript
TIL that #fleekFunctions run in a "#Deno-based" runtime. This means that some #nodeJS APIs are not available ( `fs`, `os`, `child_process`), and presumably a few standard #Web APIs will be.
Also, functions are bundled by esbuild at deploy time, so you can use some #NPM dependencies.
Unfortunately, there's not a good local development, or remote debugging story yet though there is [a utility for outputting console messages to function responses: ](https://www.npmjs.com/package/fleek-function-utils)
🪬🍄🌈🎮💻🚲🥓🎃💀🏴🛻♓🧿
