• AutoBuilder
• @github@anaclumos@rsc-swr

OpenClaw, Hermes, Poke를 쓰며 느낀 단점들

내가 만약 워크스페이스 에이전트를 만든다면 어떻게 만들까?

메모리

• 육하원칙에 맞게 기억해야하는데, 이걸 잘 못 함
  • 맥락을 종종 헷갈려함
• 메모리 툴을 명시적으로 불러야 함
  • 이는 Hermes에서 많이 완화된 부분

Slack

• 답장을 매번 하려 함. 쓰레드에 달리는 모든 글에 답을 함.
  • 매번 답할 필요는 없음. 필요할 때만 하면 됨.
• 언급하지 않은 메시지는 읽지 않음.
  • 모든 워크스페이스의 변화를 계속 보고 있어야 함, 그리고 기억해야 함

Yarn is another package manager for JavaScript that Facebook developed as a more efficient and reliable alternative to npm. It was released in 2016, several years after npm.

Here are a few features of Yarn:

1. Speed and Efficiency. Yarn is known for its speed and efficiency. It uses a deterministic installation algorithm that ensures the exact dependencies are installed in the same structure every time.
2. Offline Mode. Yarn has a feature where it can install packages from a local cache if they have been downloaded before, making it possible to work offline.
3. Security. When installing packages, Yarn first suggestions their checksums for integrity before actual code execution takes place.
4. Workspaces. Yarn has a native feature called "workspaces" to manage mono repo (mono repository) architectures, which can make it easier to manage projects with multiple sub-packages more accessible.
5. Compatibility. Yarn supports the npm registry, so you can access the many libraries that npm hosts.

Comparison between npm and Yarn

• Performance. When Yarn was first released, one of its main advantages over npm was its performance. Yarn offered faster package installation. However, since npm version 5, the performance gap has significantly reduced.
• Security. Yarn has the edge over npm because it uses checksums for every package before they are installed, ensuring its integrity.
• Offline mode. Yarn can reuse previously downloaded, making it possible to install packages without an internet connection, which npm can't do.
• Workspaces. While both package managers support managing multiple packages within the same top-level root package, Yarn's workspace feature is more advanced and configurable.
• Lockfile. Both npm and Yarn generate a lock file (package-lock.json for npm, yarn. lock for Yarn), which helps lock dependencies down to a specific version, making installations more reliable between different systems.
• Documentation. npm tends to have better and more comprehensive documentation than Yarn.