Live data from Hacker News

Microsoft Edit

github.com

121–130 of 337 posts

Re: Microsoft Edit

#121
post #6
post #4

Earlier quoted context omitted.

That may be the written goal, but I doubt that's the actual reason the project exists.

Yeah ... I don't think there's any overlap between "users largely unfamiliar with terminals" who want something easy to use, and 'Linux users who are sufficiently technical that they would even hear about this repo'.

It's a windows 11 terminal editor. Don't get confused by the fact that it also works on Linux.

Re: Microsoft Edit

#123
post #6

Earlier quoted context omitted.

Yeah ... I don't think there's any overlap between "users largely unfamiliar with terminals" who want something easy to use, and 'Linux users who are sufficiently technical that they would even hear about this repo'.

Here's a scenario. You're running a cluster, and your users are biologists producing large datasets. They need to run some very specific command line software to assemble genomes. They need to edit SLURM scripts over SSH. This is all far outside their comfort zone. You need to point them at a text editor, which one do you choose? I've met biologists who enjoy the challenge of vim, but they are rare. nano does the job…

> You're running a cluster, and your users are biologists producing large datasets. They need to run some very specific command line software to assemble genomes. They need to edit SLURM scripts over SSH. This is all far outside their comfort zone. You need to point them at a text editor, which one do you choose?

Wrongly phrased scenario. If you are running this cluster for the biologists, you should build a front end for them to "edit SLURM scripts", or you may find yourself looking for a new job.

> A Bioinformatics Engineer develops software, algorithms, and databases to analyze biological data.

You're an engineer, so why don't you engineer a solution?

Re: Microsoft Edit

#124

Earlier quoted context omitted.

The title is a bit confusing depending how you read it. Edit isn't "for" Linux any more than PowerShell was made for Linux to displace bash, zsh, fish, and so on. Both are just also available with binaries "for" Linux. The previous HN posts which linked to the blog post explaining the tool's background and reason for existing on Windows cover it all a lot better than a random title pointing to the repo.

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.

Re: Microsoft Edit

#125
post #16

I used to recommend micro[1] to people like those in the target audience of this editor. I wonder if that should change or not. -- 1: https://micro-editor.github.io/

Last time I checked, micro should have been called macro based on the binary file size.

Well, it is orders of magnitude larger than nano, so...

Re: Microsoft Edit

#126

Meanwhile, they forced AI Copilot bloat into Notepad, whose singular use-case was supposed to be that it does one thing well without unnecessary features.

I recall reading Raymond Chen mentioning that Notepad actually gets more exercise than you'd expect; it's a common guinea pig for features: https://devblogs.microsoft.com/oldnewthing/20180521-00/?p=98...

Re: Microsoft Edit

#128
post #48

Back in 1993, I would open up binary files in edit and enjoy seeing hearts.

That, the DOS defrag visualisation, and the hex-editing my own savegames is pretty much why I'm a developer today.

Ah, the memory of going to bed while the 500MB harddrive defrags over-night, sleeping next to the endless clicking and spinning

Re: Microsoft Edit

#129

Earlier quoted context omitted.

As they explained, they needed a text editor that works in a command line (for Windows Core server installs), works across SSH (because for a while now Windows included an SSH Server so you can completely manage it through SSH), and can be used by non-vi-experienced Windows administrators (i.e. a modeless editor).

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

nano's great but the shortcuts are a bit oddball, from the perspective of a Windows guy.

Re: Microsoft Edit

#130

Earlier quoted context omitted.

As they explained, they needed a text editor that works in a command line (for Windows Core server installs), works across SSH (because for a while now Windows included an SSH Server so you can completely manage it through SSH), and can be used by non-vi-experienced Windows administrators (i.e. a modeless editor).

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.

Post reply on HN