* it’s purpose built for mega-sized monorepo models like Google (the same company that created it)
* it’s not at all beginner friendly, it’s complex mishmash of three separate constructs in their own right (build files, workspace setup, starlark), which makes it slow to ramp new engineers on.
* even simple projects require a ton of setup
* requires dedicated remote cache to be performant, which is also not trivial to configure
* requires deep bazel knowledge to troubleshoot through its verbose unclear error logs.
Because of all that, it’s extremely painful to use for anything small/medium in scale.
You seem pretty young, honestly. You likely don't remember a time when websites displayed a message "Only works in IE", or "Only works in Netscape". It was not a good time for the web.
For sure. The idea here (or at least how I've been using it) is to use Atomic as catchall place to put personal notes, interesting articles, research ideas .. pretty much anything, and Atomic will handle the categorization and knowledge synthesis. For example, I have a knowledge base that uses RSS to sync top Hacker News articles and I'll occasionally generate new wiki-style articles which summarize and synthesize the articles based on top-level categories (AI, hardware, philosophy, you name it).
> Disclaimer: This is an entire day worth of Claude Opus tokens. I don't claim I understand how it works, but I did my best to direct Claude to minimize the baseline diffs, of which it removed quite a few.
reply