1. 22
  1.  

  2. 11

    As cool as this looks, I feel like a proprietary editor is a hard sell these days.

    1. 3

      Is it? I’ve used sublime for years, and only really switched to VSCode because it had more extensions and a bigger community. Only having a limited time trial feels like a much bigger obstacle, since developers hate to pay for stuff

      1. 3

        I don’t mind paying for things but my main concern has become longevity.

        On the mac in particular where they frequently break backwards compatibility I want to know that the software will keep working for forever and every time I buy commercial software for the mac that gets broken. Their license servers don’t stay up or they lose interest in it for long enough that Apple switches CPU architectures or macOS versions underneath it and it doesn’t work anymore.

        I’ve spent about $200 on 1password licences and they’re just about to drop support for the way I use them and there’s basically nothing I can do to keep it working once Apple changes some insignificant thing that Agilebits would have to update it for. That might be a Firefox or Safari plugin architectural change or even just an SSL certificate that needs renewing.

        At least with something open source I can go and do that myself

        1. 3

          Paying for stuff isn’t the barrier, at least not for me. It’s the lack of hackability and extensions.

          I guess if they had a robust plugin system, that could make the lack of source easier to swallow, but it’s still unlikely to have many plugins or a big community, because it’s proprietary.

          1. 2

            Sublime was hackable, had extensions, had a robust plugin system. In fact, both atom and VSCode are very much inspired on sublime, and this is as well, just from looking at it. The assertion that a piece of software won’t have plugins or a big community ** because** it’s proprietary is just incorrect.

            1. 5

              Sublime is from another time where VSCode and Atom didn’t exist. This is very anecdotal, but most developers I see nowadays are using VSCode wethers 5-10 years ago most of them were using Sublime.

              I guess this editor has a niche for Rust and Go developers who want IDE with native performance, but at the cost of extendability.

      2. 4

        Never thought about using the Structure/Outline as a symbol minimap. I’m gonna try it like that in my IDEs.

        1. 1

          Playing with editors, this looks well done.

          • It must be much better to switch editors; just having Tree Sitter is not enough.
          • It needs more killer features for me to consider switching.
          • Proprietary editors need more value: there is a high cost to their precarious future maintenance.
          1. 1

            Just curious, but what is Zas Editor itself written in?

            1. 2

              Rust and Swift: source

              1. 1

                Rust for the backend and Swift for the frontend.

              2. 1

                If I worked on a Mac I’d be all over this.