←back to thread

Microsoft Edit

(github.com)
486 points ethanpil | 1 comments | 25 Jun 25 00:07 UTC | HN request time: 0.478s | source
Show context
anyfoo ◴[25 Jun 25 00:27 UTC] No.44372516[source]▶
Fun. I must admit I don't really know who this is for, but it seems fun.
replies(5): >>44372607 #>>44372679 #>>44372736 #>>44373224 #>>44373591 #
tim-- ◴[25 Jun 25 01:06 UTC] No.44372736[source]▶
It's for people that want to use the Windows Terminal to edit files. The old `edit` command has been unsupported on Windows since 2006, so there was no Microsoft-provided editor that could be used in the command line since then.

It's impressive to see how fast this editor is. https://github.com/microsoft/edit/pull/408

> By writing SIMD routines specific to newline seeking, we can bump that up [to 125GB/s]

replies(3): >>44372789 #>>44373783 #>>44376123 #
_verandaguy ◴[25 Jun 25 01:14 UTC] No.44372789[source]▶
Is... this a meaningful benchmark?

Who's editing files big enough to benefit from 120GBps throughput in any meaningful way on the regular using an interactive editor rather than just pushing it through a script/tool/throwing it into ETL depending on the size and nature of the data?

replies(7): >>44372802 #>>44372819 #>>44372820 #>>44372879 #>>44373088 #>>44373143 #>>44375280 #
tim-- ◴[25 Jun 25 01:30 UTC] No.44372879[source]▶
As a specific benchmark, no. But that wasn't the point of linking to the PR. Although the command looks like a basic editor, it is surprisingly featureful.

Fuzzy search, regular expression find & replace.

I wonder how much work is going to continue going into the new command? Will it get syntax highlighting (someone has already forked it and added Python syntax highlighting: https://github.com/gurneesh9/scriptly) and language server support? :)

replies(1): >>44372981 #
1. _verandaguy ◴[25 Jun 25 01:52 UTC] No.44372981[source]▶
Right, these are more useful features, IMO, than the ability to rip through 125GB of data every second. I can live without that, but syntax highlighting's a critical feature, and for some languages LSP support is a really big nice-to-have. I think both of those are, in this day and age, really legitimate first-class/built-in features. So are fuzzy searching and PCRE find&replace.

Add on a well-built plugin API, and this will be nominally competitive with the likes of vim and emacs.