6 ms·

Same. I tried zed but it doesn't come close.

bayindirh 2y ago
Zed tries too hard to be magical, plus their license terms are not the best. Before anyone asks any further. See the CLA [0] and the Privacy Policy [1]. [0]: https://zed.dev/cla https://zed.dev/cla [1]: https://zed.dev/privacy-policy https://zed.dev/privacy-policy
- vollbrecht 2y ago
  I may see your first point, but how is GPL3 worse than a closed source software?
  - BoredPositron 2y ago
    Corps usually have problems with gpl software being used.
    - saagarjha 2y ago
      Everyone knows if you touch GPL you get cooties
      - bayindirh 2y ago
        Thanks for the info! I might be immune then. I swim in that thing.
      - user432678 2y ago
        Yet the whole world runs on Linux with no issues :shrugs:
    - bayindirh 2y ago
      It's not the GPLv3 license, it's the attached CLA and Privacy Policy.
  - bayindirh 2y ago
    The code might be GPLv3, which is my favorite license BTW, but they have a "nice" CLA [0] and Privacy Policy [1] which doesn't inspire confidence. I think CLA is a nuanced thing, since Eclipse also has one and didn't rugpull anyone ever, but their Privacy Policy states that the tool is chockful with telemetry and can collect any personal and non-personal data as they see fit. When somebody tells that you can opt-out of this, I have a hard time believing that the switches are connected to anything. [0]: https://zed.dev/cla https://zed.dev/cla [1]: https://zed.dev/privacy-policy https://zed.dev/privacy-policy
- WD-42 2y ago
  It's GPL. How is the license not the best?
  - bayindirh 2y ago
    See the attached CLA [0] and Privacy Policy [1]. [0]: https://zed.dev/cla https://zed.dev/cla [1]: https://zed.dev/privacy-policy https://zed.dev/privacy-policy
    - WD-42 2y ago
      And yet, ST is closed source. Still a wild comparison. This isn’t just license preference either. I would imagine the efforts of the sublime lsp people would be greatly eased if they had access to the source. But nah zed bad because cla.
      - bayindirh 2y ago
        No it's not. I mostly find closed source application with clear lines more trustworthy than openwashed software. I'm a big Free Software supporter. For my personal projects, I only use (A)GPLv3 or later. However, I have a problem with software which comes with "GPLv3 BUT..." licenses. We have seen how CLAs weaponized against their contributors with rugpull license changes. Also, Zed was closed source at first. I had beta access to that thing. Then they pivoted to "Open source with closed source collaboration servers" thing, and they claimed rights on anything passing through their servers (collaboration / zed-ai). When software stops being local-only, being Free Software loses half the meaning, because you can do all the nefarious things on the backend, without people seeing them. "We only send harmless usage data" you may say, but you don't say how you process and which other signals you mix into that data from other sources or data brokers. That's a problem. Remember Go's opt-out telemetry debacle. The math was solid, it was anonymous, yes. However it was forced opt-out via an environment variable, so the burden was continuously on us, the users. If the Go team didn't change it to opt-in, I was ready to drop Go as a programming language, like many individuals and companies. Now the telemetry is opt-in, and users have better control. These things are nuanced. We should be diligent. For example, Eclipse (my favorite IDE for the last two decades) has CLA, but they never abused the power they have, plus that thing is Apache 2.0 licensed. However, Zed's actions, combined with their privacy policy, doesn't inspire confidence, so I don't use it, and share my view about Zed. If you don't agree that's fine, but pointing fingers like that is not. As I said, I have chosen BBEdit over sublime 15 years ago, and still use that, and if BBEdit can detect and run any supported LSP OOTB, like magic, Sublime can do the same technically. So they should barrage the bug tracker. It's on Sublime to make it better. It's closed source, so the developer has forced themselves to fix it by making it closed source.

Zed tries too hard to be magical, plus their license terms are not the best. Before anyone asks any further. See the CLA [0] and the Privacy Policy [1]. [0]: https://zed.dev/cla https://zed.dev/cla [1]: https://zed.dev/privacy-policy https://zed.dev/privacy-policy

vollbrecht 2y ago
I may see your first point, but how is GPL3 worse than a closed source software?
- BoredPositron 2y ago
  Corps usually have problems with gpl software being used.
  - saagarjha 2y ago
    Everyone knows if you touch GPL you get cooties
    - bayindirh 2y ago
      Thanks for the info! I might be immune then. I swim in that thing.
    - user432678 2y ago
      Yet the whole world runs on Linux with no issues :shrugs:
  - bayindirh 2y ago
    It's not the GPLv3 license, it's the attached CLA and Privacy Policy.
- bayindirh 2y ago
  The code might be GPLv3, which is my favorite license BTW, but they have a "nice" CLA [0] and Privacy Policy [1] which doesn't inspire confidence. I think CLA is a nuanced thing, since Eclipse also has one and didn't rugpull anyone ever, but their Privacy Policy states that the tool is chockful with telemetry and can collect any personal and non-personal data as they see fit. When somebody tells that you can opt-out of this, I have a hard time believing that the switches are connected to anything. [0]: https://zed.dev/cla https://zed.dev/cla [1]: https://zed.dev/privacy-policy https://zed.dev/privacy-policy
WD-42 2y ago
It's GPL. How is the license not the best?
- bayindirh 2y ago
  See the attached CLA [0] and Privacy Policy [1]. [0]: https://zed.dev/cla https://zed.dev/cla [1]: https://zed.dev/privacy-policy https://zed.dev/privacy-policy
  - WD-42 2y ago
    And yet, ST is closed source. Still a wild comparison. This isn’t just license preference either. I would imagine the efforts of the sublime lsp people would be greatly eased if they had access to the source. But nah zed bad because cla.
    - bayindirh 2y ago
      No it's not. I mostly find closed source application with clear lines more trustworthy than openwashed software. I'm a big Free Software supporter. For my personal projects, I only use (A)GPLv3 or later. However, I have a problem with software which comes with "GPLv3 BUT..." licenses. We have seen how CLAs weaponized against their contributors with rugpull license changes. Also, Zed was closed source at first. I had beta access to that thing. Then they pivoted to "Open source with closed source collaboration servers" thing, and they claimed rights on anything passing through their servers (collaboration / zed-ai). When software stops being local-only, being Free Software loses half the meaning, because you can do all the nefarious things on the backend, without people seeing them. "We only send harmless usage data" you may say, but you don't say how you process and which other signals you mix into that data from other sources or data brokers. That's a problem. Remember Go's opt-out telemetry debacle. The math was solid, it was anonymous, yes. However it was forced opt-out via an environment variable, so the burden was continuously on us, the users. If the Go team didn't change it to opt-in, I was ready to drop Go as a programming language, like many individuals and companies. Now the telemetry is opt-in, and users have better control. These things are nuanced. We should be diligent. For example, Eclipse (my favorite IDE for the last two decades) has CLA, but they never abused the power they have, plus that thing is Apache 2.0 licensed. However, Zed's actions, combined with their privacy policy, doesn't inspire confidence, so I don't use it, and share my view about Zed. If you don't agree that's fine, but pointing fingers like that is not. As I said, I have chosen BBEdit over sublime 15 years ago, and still use that, and if BBEdit can detect and run any supported LSP OOTB, like magic, Sublime can do the same technically. So they should barrage the bug tracker. It's on Sublime to make it better. It's closed source, so the developer has forced themselves to fix it by making it closed source.