FWIW, I really like what Tangled is doing and I agree that we need a federation of forges. Which is why, I am planning to use ATproto too for public repositories in the code forge I am building, https://juju.bi
Thanks, missed that part. I would still be interested in knowing how much additional storage that adds, if the OP is interested in updating the article.
1. `color` feature and thus the `anstream` dep is optional.
2. Even if you use it, it handles all the behaviour correctly regarding the piping and no color support, which is why it is a dependency in the first place.
This ulid Postgres extension doesn't have any performance issues compared to native uuidv7 in Postgres. https://github.com/pksunkara/pgx_ulid. Just wanted to bring it up since it looks like the author didn't come across it when looking for ulid generators in postgres.
Implementing support for UUIDv7 does not equal implementing support for ULID. ULID needs to be treated as a first class citizen (type, read format, storage format, converters) instead of being an afterthought result from UUIDv7.
We reduced our service server costs to 1/6th by moving from Heroku to Lambda. And that's not even considering the main benefit of a big computational request not blocking other requests (which is why we moved to it in the first place).
Can I suggest API Blueprint [1]? It is much more human friendly and easier to work on API design. Apiary has tools for complete API lifecycle management.
Disclaimer: I work on making API Blueprint better.
http://github.com/pksunkara
https://www.linkedin.com/in/pksunkara
[ my public key: https://keybase.io/pksunkara; my proof: https://keybase.io/pksunkara/sigs/YXTiDymHTSwfTfEjI2dZWnYM9dPA_eYyck8jXzPT71Y ]