Comment by 201984

Comment by 201984 4 days ago

12 replies

Comment from the author: https://lobste.rs/c/wmqvug

> Since someone mentioned forking, I suppose I’ll use this opportunity to advertise my fork of Zed: https://github.com/zedless-editor/zed

> I’m gradually removing all the features I deem undesirable: telemetry, auto-updates, proprietary cloud-only AI integrations, reliance on node.js, auto-downloading of language servers, upsells, the sign-in button, etc. I’m also aiming to make some of the cloud-only features self-hostable where it makes sense, e.g. running Zeta edit predictions off of your own llama.cpp or vLLM instance. It’s currently good enough to be my main editor, though I tend to be a bit behind on updates since there is a lot of code churn and my way of modifying the codebase isn’t exactly ideal for avoiding merge conflicts. To that end I’m experimenting with using tree-sitter to automatically apply AST-level edits, which might end up becoming a tool that can build customizable “unshittified” versions of Zed.

haneefmubarak 4 days ago

> relying on node.js

When did people start hating node and what do they have against it?

  • bigstrat2003 4 days ago

    For Zed specifically? It cuts directly against their stated goal of being fast and resource-light. Moreover, it is not acceptable for software I use to automatically download and run third-party software without asking me.

    For node.js in general? The language isn't even considered good in the browser, for which it was invented. It is absolutely insane to then try to turn it into a standalone programming language. There are so many better options available, use one of them! Reusing a crappy tool just because it's what you know is a mark of very poor craftsmanship.

  • leblancfg 4 days ago

    > When did people start hating node

    You're kidding, right?

    • WestCoader 4 days ago

      Maybe they've just never seen a dependency they didn't like.

  • max-privatevoid 4 days ago

    It shouldn't be as tightly integrated into the editor as it is. Zed uses it for a lot of things, including to install various language servers and other things via NPM, which is just nasty.

  • muppetman 4 days ago

    You might not be old enough to remember how much everyone hated JavaScript initially - just as an in-browser language. Then suddenly it's a standalone programming language too? WTH??

    I assume that's where a lot of the hate comes from. Note that's not my opinion, just wondering if that might be why.

    • skydhash 4 days ago

      JavaScript is actually fine as the warts have been documented. The main issue these days is the billions of tiny packages. So many people/org to trust for every project that uses npm.

      • zahlman 4 days ago

        Nobody is forcing you to use the tiny packages.

        The fact that the tiny packages are so popular despite their triviality is, to me, solid evidence that simply documenting the warts does not in fact make everything fine.

        And I say this as someone who is generally pro having more small-but-not-tiny packages (say, on the order of a few hundred to a few thousand lines) in the Python ecosystem.

        • hollerith 4 days ago

          The point is that Zed's developers have chosen to include prettier, which probably transitively includes many other NPM packages.

          Node and these NPM packages represent a large increase in attack surface for a relatively small benefit (namely, prettier is included in Zed so that Zed's settings.json is easier to read and edit) which makes me wonder whether Zed's devs care about security at all.

  • woodson 4 days ago

    I guess some node.js based tools that are included in Zed (or its language extensions) such as ‘prettier’ don’t behave well in some environments (e.g., they constantly try to write files to /home/$USER even if that’s not your home directory). Things like that create some backlash.

  • aDyslecticCrow 4 days ago

    Slow and ram heavy. Zed feels refreshingly snappy compared to vscode even before adding plugins. And why does desktop application need to use interpreted programming languages?

  • Sephr 4 days ago

    For me, upon its inception. We desperately needed unity in API design and node.js hasn't been adequate for many of us.

    WinterTC has only recently been chartered in order to make strides towards specifying a unified standard library for the JS ecosystem.