The brand new Microsoft Edit, which is the successor of the old MS-DOS-editor will come soon to Linux as well?

There is a discussion going on how to call ms edit executable under Linux at: https://github.com/microsoft/edit/discussions/341

Microsoft Edit is fully written in Rust. And the source-code is actually fully open-source as well under MIT license 😮.

I personally would like see them calling it dos-edit or just dosedit, since that would be kinda funny. But I understand it will be called ms-edit instead.

I know Linux already has vi, vim, neovim and nano, … and more… However is kind of ironic to see this binary be shipped to Linux distros. Of course it’s already added to Arch btw: https://aur.archlinux.org/packages/ms-edit-git

Official GitHub page.

  • thingsiplay@beehaw.org
    link
    fedilink
    arrow-up
    38
    ·
    2 days ago

    Why would anyone on Linux want to use a Microsoft terminal editor, when especially on Linux we have a long history of very strong and good terminal editors? I mean really, why?

    • webghost0101@sopuli.xyz
      link
      fedilink
      arrow-up
      11
      ·
      2 days ago

      Because the same people who might be forced to use this tool on the job are the same who like linux.

      They do the same with powershell en vscode and you can just remote terminal from linux into windows.

      Its a small investment in making developers more comfortabel with their toold and thus increase chance they will use them.

  • macniel@feddit.org
    link
    fedilink
    arrow-up
    32
    arrow-down
    2
    ·
    edit-2
    2 days ago

    laughs in

    • ed
    • nano, pico
    • emacs
    • vi, vim, neovim, nvchad
    • kate
    • gedit
    • mousepad
    • vscode, oss
  • Shape4985@lemmy.ml
    link
    fedilink
    arrow-up
    19
    ·
    2 days ago

    I cant wait to never install this. Immediately forgetting it exists. A big linux selling point is moving away from the microsoft ecosystem

        • Colloidal@programming.dev
          link
          fedilink
          English
          arrow-up
          1
          ·
          7 hours ago

          Why build another CLI editor?
          What motivated us to build Edit was the need for a default CLI text editor in 64-bit versions of Windows. 32-bit versions of Windows ship with the MS-DOS editor, but 64-bit versions do not have a CLI editor installed inbox. From there, we narrowed down our options…
          Many of you are probably familiar with the “How do I exit vim?” meme. While it is relatively simple to learn the magic exit incantation, it’s certainly not a coincidence that this often turns up as a stumbling block for new and old programmers.
          Because we wanted to avoid this for a built-in default editor, we decided that we wanted a modeless editor for Windows (versus a modal editor where new users would have to remember different modes of operation and how to switch between them). This unfortunately limited our choices to a list of editors that either had no first-party support for Windows or were too big to bundle them with every version of the OS. As a result, Edit was born.

          TL;DR: We tried nothing and were all out of options.

          • melroy@kbin.melroy.orgOP
            link
            fedilink
            arrow-up
            1
            ·
            4 hours ago

            I actually understand why Microsoft would create their own terminal editor again. It kinda make sense and they now have it fully in their own control.

            Not only it the binary under the magic 200k file size limit. They can now also better integrate it with windows and their key bindings etc.

  • altphoto@lemmy.today
    link
    fedilink
    arrow-up
    10
    arrow-down
    2
    ·
    2 days ago

    The proper answer is don’t even touch that xit. It could be a front for automatic AI installs or something where you learn that you can opt out of it but 5 years after they stole the data.

    Microsoft is a totally evil company and so is meta, yahoo and Google.

  • ToxicWaste@lemm.ee
    link
    fedilink
    arrow-up
    7
    ·
    2 days ago

    MS should finally make teams available on linux. like it used to be.

    but they know it would make switching to linux too easy for BYOD users. so they give us a terminal editor. and try to compete with vim and nano?

  • bitwolf@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    10 hours ago

    It’s only a matter of time before MS figures out a copilot ncurses ui and Trojan horses the editor