1. 34
    1. 6

      It always disappoints me when a News page on site doesn’t have an RSS feed.

      1. 7

        It does have an Atom feed : https://helix-editor.com/atom.xml

        Unfortunately web sites often only advertise their feeds in the source. I’ve taken the habit of letting my feed reader discover them, or directly read the source.

        It’s in the HTML <head> by the way:

        <link rel="alternate" type="application/atom+xml" title="Atom" href="https://helix-editor.com/atom.xml">
        1. 4

          Firefox and others long ago removed the RSS button. I use this extension to add it back

        2. 4

          Unfortunately web sites often only advertise their feeds in the source

          That is the correct choice. Users shouldn’t be burdened with technical details like “atom feed URL” just let them subscribe to the URL they can see and let the feed be autodetected.

        3. 2

          Odd, I swear I checked the source but apparently I must have mistyped when searching.


      2. 2
    2. 3

      I don’t get using WebAssembly as a plugin system.

      1. 19

        I think it’s mostly that it allows distributing plugins without having to recompile them for different platforms, while offering a wide range of languages that target WASM. Other editors offer one or few languages for extensions limiting what people can do and in the case of VIM for example, the initial scripting language was not exactly great. So by using WASM you say like: Okay you can use whatever you like as long as you all use the nice APIs.

        1. 17

          I also think there’s a potential reliability + simplicity win in having your plugins run sandboxed inside the editor itself, vs. needing to spawn and supervise a bunch of child processes and then talk to them over some bespoke protocol.

          WASM has a lot of the same properties as classic shared object based binary plugins, without the whole mess of crash and security-hole risks that come from dropping a bunch of unknown machine code into your main process.

    3. -1

      Modal, terminal based text editor written in… Rust? In 2022?

      Wouldn’t C be a better fit here, considering the 70s sensibilities?

      1. 15

        Wait til you find out that people write vim plugins in typescript

      2. 14

        It’s okay to not like things

      3. 4

        I think your sarcasm was on lost on people here. I detected and appreciated it.

        1. 2

          Guess I’m dense, could you explain?

          1. 3

            It’s my impression that Emacs and Vim are largely inspired by development in editors from the 70s and 80s. The joke is that developing tools with their aesthetic would lead one toward C to reflect the time period appropriately.

      4. 2

        Until the new Strict Provenance work, Rust embraced the PDP-11’s model of memory, so it seems very appropriate here.

    4. 1

      I played with it last night while editing a small Ruby app on my Windows gaming rig and found it pleasant. I think I’ll continue to use it in place of an OOTB, unconfigured vim on that machine and see how it goes. Hilariously, VScode crashes after ~90 minutes on that machine so maybe I’ll pick back up on a Go project I was developing while in Overwatch queues…

    5. 1

      Is there a way to disable line numbers? Line numbers conflict with copying text between terminals, and I only found an option between “relative” and “absolute” (not “none”, alas).