1,314 karma · joined October 13, 2014
Edit: Never mind. Misunderstood what this is.
https://github.com/gajus/surgeon
For context, it was created to support my previous business Applaudience. We had to build scrapers for (literally) thousands of cinema websites. At some point we migrated from custom scrips to Surgeon routines and reduced overall codebase size by 70% LoC. It was a huge time saver in terms of both writing new integrations and debugging when things go wrong.
The reality is that data extraction is a highly specialized task and you need specialized software to do it well. Tools like Surgeon can abstract a ton of complexity, but they have steeper learning curve.
I still use it whenever I need to scrape anything and you can combine it with anything that outputs HTML e.g. Playwright.
Ultimately business died (covid was brutal) and I moved on to even more exciting things, but this remains one of those technologies that I wish would have received more adoption.
https://github.com/gajus/slonik#user-content-slonik-how-are-...
It is not going to be the default because it is way slower.
https://github.com/gajus/slonik/actions/runs/6616647651
Test node_version:18 test_only:postgres-integration is taking 3 minutes.
Test node_version:18 test_only:pg-integration is taking 38 seconds.
It is possible that this is an issue with https://github.com/gajus/postgres-bridge, but I was not able to pinpoint anything in particular that would explain the time difference.
That
I was recently exploring the space, and Kysely came on top as a framework with broader adoption.
Highlights:
* Grafana and Loki seems to be favorite
* https://datalust.co/seq is the easiest to deploy (single container)
* https://github.com/tstack/lnav CLI based tool
Every time I see it I think "barf"
https://github.com/vercel/turbo/issues/986#issuecomment-1477...