In microservice world.
Do you want to track features in each service or have a source of truth using flagd
I prefer central source of truth
266 karma · joined August 8, 2018
Cool stuff
Lost you here. A better person by using old school IDEs? What are you smoking
A better person used LLM and whatever tool he gets at disposal to get job done ASAP and then goes outside to enjoy life with fellow humans
Well other orms do that as well ofc. But I feel this is a low level as it can get
Check the repo here https://github.com/grmkris/drizzle-pg-notify-audit-table
Sadly my motivation did not last long. Nice project
Let me define schema with drizzle and use its generated objects to interact with db. Postgres driver for server SQLite driver for client
Anyone else feel the same ?
So building a good API layer + web app gives you possibility to build a good native app on top of same API later when your idea is validated
For js/node
1st It caches node modules making it faster and space efficient
2nd It creates a root node-modules and then a node-module for each sub package. Which makes it much easier to work with monorepo packages. With a single node-modules you can accidently import packages that your package doesn't declare in package.json
A good quality meal with some wine and dessert will cost you +40$ for sure
If I have an API sever and then instead of calling those apis from client, I make all db calls on the server and then render the html. How much of processing that was done was spent on rendering html.
Also I wonder how react server components and serverside rendering go with localfirst software?
I love localfirst web apps, they seem kinda incompatible with serverside apps
Or go fully into supabase ecosystems and also use their types and their built in migrations and types