←back to thread

Microsoft Edit

(github.com)
486 points ethanpil | 4 comments | | HN request time: 0.63s | source
Show context
pulkitsh1234 ◴[] No.44374546[source]
Geniunely curious, how projects like these get approved in an org at the scale of Microsoft? Is this like a side project by some devs or part of some product roadmap? How did they convince the leadership to spend time on this?
replies(3): >>44374646 #>>44375218 #>>44376242 #
dark-star ◴[] No.44374646[source]
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).
replies(1): >>44374677 #
llarsson ◴[] No.44374677[source]
Telling people to use nano would of course have been next to impossible. Much easier to rewrite a DOS-era editor in Rust, naturally.
replies(7): >>44374746 #>>44374944 #>>44375036 #>>44375421 #>>44375449 #>>44376739 #>>44381803 #
1. oersted ◴[] No.44375036[source]
micro would have been an even better choice, the UX is impressively close to something like Sublime Text for a TUI, and very comfortable for those not used to modal editors.
replies(3): >>44375214 #>>44376474 #>>44379014 #
2. aembleton ◴[] No.44375214[source]
This is the first time I've heard of micro. More info here: https://micro-editor.github.io/
3. subjectsigma ◴[] No.44376474[source]
I like micro and use it occasionally. I like this even more. I booted up the editor and instantly thought “it would be nice if there was a clickable buffer list right about…” and then realized my mouse was hovering over it. My next instant thought was that micro should have implemented this feature a long time ago
4. mixmastamyk ◴[] No.44379014[source]
It doesn’t have a menu for windows devs, and is supposed to be small and light. Two strikes against.