←back to thread

Microsoft Edit

(github.com)
486 points ethanpil | 1 comments | 25 Jun 25 00:07 UTC | HN request time: 0.001s | 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 #
magicalhippo ◴[25 Jun 25 02:27 UTC] No.44373143[source]▶
At work we have to modify some 500 MB XML's every now and then, as the source messes them up in non-repeating ways occasionally.

Typically we just hand edit them. Actually been pleasantly surprised at how well VS Code handles it, very snappy.

replies(1): >>44375916 #
1. pprnm ◴[25 Jun 25 11:10 UTC] No.44375916{3}[source]▶
I use the CudaText for big files. It is like open source Sublime.