Live data from Hacker News

Microsoft Edit

github.com

151–160 of 337 posts

Re: Microsoft Edit

#151

Earlier quoted context omitted.

> rewrite This is not a rewrite. Maybe it’s slightly inspired by the old thing, especially with having GUI-style clickable menus (something not seen often in terminal editors), but it’s much more modern.

I still see it as rewrite even if you only use the original as inspiration. But that's just semantics

If they hadn’t called it “edit” you wouldn’t have thought of it as a rewrite.

Re: Microsoft Edit

#152

Earlier quoted context omitted.

> rewrite This is not a rewrite. Maybe it’s slightly inspired by the old thing, especially with having GUI-style clickable menus (something not seen often in terminal editors), but it’s much more modern.

I still see it as rewrite even if you only use the original as inspiration. But that's just semantics

It's no semantics. It's just a lie

Re: Microsoft Edit

#153

Earlier quoted context omitted.

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?

For a text editor, yes, absolutely. As developers, we rotinely need to work with large data sets, may it be gigabytes of logs, csv data, sql dump or what have you. Not being able to open and edit those files means you cant do your job.

But are you really trying to do that on a Windows Server? I feel like there are better tools for the job.

Re: Microsoft Edit

#154

It'd be nice if they didn't recommend winget for installation though. winget is an egregious security risk that Microsoft has just like pretended follows even minimal security practices, despite just launching four years ago with no protection from bad actors whatsoever and then never implementing any improvements since.

winget is just Windows developers' version of curl | bash . Yet another example of Microsoft copying Linux features.

Windows already has

irm | iex

Re: Microsoft Edit

#155

About a month ago I heard Microsoft had their own Linux distribution to help Microsoft Windows users feel more at home. From memory, it was a rather simple GNOME setup. Nothing special. I am surprised Micrsooft didnt use the opportunity to create a micrsoft specific Linux distro that replaces bash with powershell, or Edit with vim, nano and other choices as well as .NET and Visual Studio Code by developer installs. M…

> I am surprised Micrsooft didnt use the opportunity to create a micrsoft specific Linux distro

The last one didn’t do so hot, they named it “Xenix”

Re: Microsoft Edit

#156
post #10
post #2

Fun. I must admit I don't really know who this is for , but it seems fun.

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]

That's pretty handy. I was having to use bash -c "vi myfile.txt" which was a bit annoying.

Re: Microsoft Edit

#158

Nano is completely ok for this. Nope, let's burn some cash and reinvent the wheel. Instead of donating to Nano devs, or hire some of them or something. Stupid corp at their finest.

Nano is a bare-bones editor with its own wacky key-bindings. What is the point? If I want to learn new key-bindings I'll learn a full-featured editor.

msedit's key-bindings are based on IBM CUA. It's immediately familiar to a great many people.

Re: Microsoft Edit

#159
post #124

Earlier quoted context omitted.

TIL PowerShell exists for Linux. But.. why?

Well why not? Is there supposed to be a single elected shell for Linux? Powershell on Linux is just one of plenty others.

I'm not against it. Absolutely go for it.

I just wonder what was the reason to port it and then I would like to have a word with a real living person who is actually using that shell.

Re: Microsoft Edit

#160

Earlier quoted context omitted.

Telling people to use nano would of course have been next to impossible. Much easier to rewrite a DOS-era editor in Rust, naturally.

> rewrite This is not a rewrite. Maybe it’s slightly inspired by the old thing, especially with having GUI-style clickable menus (something not seen often in terminal editors), but it’s much more modern.

It does seem "modern" in the sense that it is incredibly limited in functionality (EDIT.COM from DOS is much more full-featured) and deviates from well-established UI conventions.

CUA-style menubars aren't that uncommon in textmode editors. Midnight Commander's editor has traditional menubars with much more extensive functionality, as does jedsoft.org's Jed editor. Both of these also support mouse input on the TTY console via GPM, not just within a graphical terminal.

Post reply on HN