If you're keen to selfhost, here's a little experiment:
Build your own FaaS
→ Run functions on your infrastructure
Featuring
→ pinches of easy backend stuff
→ no UI
How to do it? 1/N 🧵
#buildinpublic
@dubya_brian@cnakazawa I’m not denying innovation. You call innovation what was launched yesterday. It didn’t pass no test at all. “successfully” has another meaning.
I like the new stuff and the focus on performance, but you’ll be a greater fool if you listen to every new kid in town.
I have a very different take on this.
Node should not follow. Being leader has very different priorities and responsibilities. Let the chasers try to innovate.
I'm not against them, I want them more. But, mind they use tricks to get traction, and this typescript affair is an example (It's not just stripping types, you have to bake the specific business-logic inside your runtime).
I like the feature to run ts directly. But, this is just another silly frontend mindset echo-chamber: "No build step".
Almost every language has a build/packaging step. And often more the one. Every tooling, every runtime, ... the list is very very log. (i'm talking about proper apps not one-liners).
It's just a tooling/workflow issue and a total lack of aptitude to agree on one solution instead of creating dozens, because I'm smart than you or have I business build upon it.
So, "Like to run ts", yes! But let the wisdom of time give a proper say before giving in.
@jo4code@_buildspace@_nightsweekends The feature set are not compelling enough for that price point
I will develop first the foundation, and if I get some traction I’ll add more value on top