I've been thinking about restarting work on #Tapir. Development stopped because I hit a wall with the database system. Writing Tapir in #Deno was a long sequence of yak-shaving without much payoff; most of my dev time was spent implementing JSON-LD, Web Signatures, and a database layer that *should* have been a library if Deno had better Node compatibility at the time.
Conversation
Notices
-
Embed this notice
Adam Nelson (arnelson@fosstodon.org)'s status on Saturday, 04-May-2024 10:13:56 JST Adam Nelson - 洪 民憙 (Hong Minhee) repeated this.
-
Embed this notice
Adam Nelson (arnelson@fosstodon.org)'s status on Saturday, 04-May-2024 10:13:56 JST Adam Nelson It's been a while, and the Deno ecosystem has improved a lot. Drizzle looks promising as an ORM layer (better than my hacked-together one), and more Fediverse projects in Deno are popping up (#Fedify looks really cool!). But I'm rethinking Deno.
There were 3 things that drew me to Deno initially:
- Ease of install (just run the app from a URL)
- Cloud platforms (Deno Deploy w/ Deno KV)
- JavaScript (I know the language, and it has a big ecosystem)But all 3 didn't work out the way I planned.