We just also shouldn't call releases with no source "open source".
I wouldn't really have a complaint with their source being released as Apache 2. I just don't want the term "open source" diluted to including just a release of build artifacts.
> It just seems like we're taking the descriptions we have too literally from an era where medical terminology was often metaphorical
And content creators. I hope I am not the only one who took this plague as a true historical event where people 100% started dancing out of nowhere and died dancing because of scary content I consumed at a younger age like "Top 10 Unexplained Cases Of Mass Hysteria"
Apparently the name stuck because some libraries and websites already adopted the term even if there was no Web3 at all. Lol Jack Dorsey's already working on a Web5 that nobody is interested either.
I think that the real Web3 will be mature and developed enough that there will be no need to create a bunch of apps boasting they're on the Web3 nor libraries abstracting Web3 APIs called "web3.js" before the term is even tangible
This is awesome!
Admin panels are fine to me, but honestly this is a much more beautiful and productive approach. Very cool project.
Is an Astro template/integration a possibility? I'd love an editable static site that triggers Netlify builds. I actually have an Astro project on Netlify CMS that I wouldn't mind moving to this.
The way I see it, Deno was built to be an executable, Typescript-first, Web API first and have a robust security model. Bun is built to be an executable and blazingly fast while still learning from some of Deno's hits and misses.
