←back to thread

Microsoft Edit

(github.com)
486 points ethanpil | 1 comments | | HN request time: 0.403s | source
Show context
anyfoo ◴[] 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-- ◴[] 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 ◴[] 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 #
WD-42 ◴[] No.44372820[source]
Who cares? It’s fun. Programming can be fun.
replies(2): >>44372829 #>>44372966 #
_verandaguy ◴[] No.44372966[source]
I'm not saying that doing this can't be fun, or even good to learn off of, but when it's touted as a feature or a spec, I do have to ask if it's a legitimate point.

If you build the world's widest bike, that's cool, and I'm happy you had fun doing it, but it's probably not the most useful optimization goal for a bike.

replies(2): >>44373496 #>>44378833 #
1. legends2k ◴[] No.44378833[source]
I don't think a sentence in a big report page is counted as touting.