• vext01@lemmy.sdf.org
    link
    fedilink
    arrow-up
    11
    ·
    1 year ago

    Wait, packer is dead? Feels like I’ve been through 100 damned packed managers.

    What should one use now then?

    • SkipperWannabe@lemm.ee
      link
      fedilink
      arrow-up
      7
      ·
      edit-2
      1 year ago

      The notice on packer suggested to use either lazy or pckr

      NOTICE:

      This repository is currently unmaintained. For the time being (as of August, 2023), it is recommended to use one of the following plugin managers instead:

      lazy.nvim: Most stable and maintained plugin manager for Nvim.

      pckr.nvim: Spiritual successor of packer.nvim. Functional but not as stable as lazy.nvim.

    • ck_@discuss.tchncs.de
      link
      fedilink
      arrow-up
      5
      ·
      1 year ago

      As long as it still works for you, there is no need to switch. Resist the urge to follow the hype, it just means you’ll spend less time doing something actually productive.

    • tubofboldts@lemm.ee
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Yeah I’ll stick with packer until some breaking change maybe happens with neovim in the future. I say this with no knowledge of the other two options, but everything with packer is so damn easy I can’t imagine lazy or pckr being any easier.

    • Slotos@feddit.nl
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Been using minpac since forever. It has all the minimal functionality and is a perfect dead project one doesn’t have to worry about.

      One day I might switch to lazy, but so far I’m too lazy to.

    • deriver@fosstodon.orgOP
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      @skipperwannabe

      Does “still works” mean null-ls works just as well today on Neovim v0.9.2 (and/or latest nightly) as it did on Neovim v0.9.1 when the null-ls archival announcement was made about two months ago or that it “still works” as long as you can work around issues stemming from a change(s) to Neovim since the null-ls archival announcement?

      Since Neovim v0.9.2 “is a maintenance release, focused on bug fixes and performance improvements”, I assume its the former.

      • SkipperWannabe@lemm.ee
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        For me, it works as well on nightly without any modifications as it did when the archival announcement was made. But I only use formatters and one or two linters. So can’t confirm for other features.

        That said, I am thinking about changing to conform.nivm for formatting.