i hate monorepos but for Go the trial of constantly updating the go.mod if you have two repos that are interdependent or one dependent on the other it's a lot of rigmerole
compared to just keeping it together
once one part becomes stable you can push it out and any further patches later on will be small usually, and not so onerous as every time you are changing each one in parallel
having to make sure everyone who is working on one side knows what is happening on the other side
until a cluster of libraries are tested, stable, and the client is using them adequately, monorepo is the way TM
today's theme is concurrency and synchronisation
the issue of monorepos while in development is one example of a concurrency problem
the issue of replaceable events is another concurrency problem
i've just also posted a comment on my issue on the NIPs suggesting the idea that as well as keeping historical events, all replaceable events should have a "replaces event <id>" tag
and that will also make the replaced events into a blockchain btw
which i thought was funny
nostr:nevent1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcpr9mhxue69uhhyetvv9ujumtvv44h2tn0dekxjmn99uq3zamnwvaz7tmwdaehgu3wwa5kuef0qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcpz4mhxue69uhkummnw3ezummcw3ezuer9wchszxnhwden5te0wp6hyctkd9jxztnwdaehgu3wd3skuep0qythwumn8ghj7ct5d3shxtnwdaehgu3wd3skuep0qywhwumn8ghj7mn0wd68ytnzd96xxmmfdejhytnnda3kjctv9uqzqdu5y67uy9rrr8zv9q9jp0wxj4j94kdm7eadjlsskq92dgalhtw6ccaucn
it's a concurrency problem btw, that's why monorepos
every time you dissociate two things that are running in parallel and interacting you have to deal with synchronisation between the two processes, and if you don't you have a mess
Oddbean new post about login | logout