#Fleek is transitioning from fleek.co to fleek.xyz this month!
What will be better about Fleek . xyz?
- Lightning-fast performance (powered by #fleek_net)
- Full #Nextjs Support (launching September)
- #FleekFunctions (lightning-fast, permissionless #edge #functions)
- Low Cost (50-80% cheaper than #Vercel on average)
- #OpenSource (starting with the CLI/SDK in September)
#webDev #web3 #serverless #blockchain #web #webHosting #cloud #crypto
> Previously, #FleekFunctions were accessible only via the #FleekCLI. That’s changed with this new release as you can now create, manage, and customize #Fleek #Functions directly from the Fleek app UI!
#javaScript #webdev #serverless #web3 #blockchain #dweb #distributed #permissionless #depin #crypto
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)
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
#3) the code for #FleekFunctions lives on IPFS, which means it's public, which means that people can view-source your backend!!! 🤯
