Add `"features": {"inline_completion_provider": "supermaven"}` to your Zed settings and you can have the best of both worlds :D
HN user
jvmancuso
- open-source vs closed fork of vscode
- transparent assistant panel vs opaque composer. you control your own prompts (cf. [0])
- in Zed the assistant panel is "just another editor", which means you can inline-assist when writing prompts. super underrated feature imo
- Zed's assistant is pretty hackable as well, you can add slash commands via native Zed extensions [1] or non-native, language-agnostic Context Servers [2]
- Zed's /workflow is analogous to Cursor's composer. to be honest it's not quite as good yet, however it's only ~1 week old. we'll catch up in no time :)
- native rust vs electron slop. Zed itself is one of the larger Rust projects out there [3], can be hard to work with in VS Code/Cursor, but speedy in Zed itself :)
[0] https://hamel.dev/blog/posts/prompt/
[1] https://zed.dev/docs/extensions/slash-commands
[2] https://zed.dev/docs/assistant/context-servers
[3] https://blog.rust-lang.org/inside-rust/2024/08/15/this-devel...
we call the latter a "Context Server", basically any process that communicates via JSON-RPC over stdio can do it. documentation for that is here: https://zed.dev/docs/assistant/context-servers
For whatever reason, fsspec is not that well known. It has less than 800 stars on github.
Sorry, I was the 800th, your post is now outdated!
Thanks for the suggestion! The reason average pooling is faster than max pooling is that the former uses only addition, which is quite a bit faster than comparison in MPC. The smooth max requires both exponentiation and division, both of which are significantly more expensive than doing the comparison in ReLU or max pooling.