Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Edit is now open source

devblogs.microsoft.com

Post reply on HN
Print view View original

81–90 of 191 posts

Re: Edit is now open source

#81

Post by jftuga »

bpshaver wrote: post #26
90s_dev wrote: post #23

Earlier quoted context omitted.

Or kilo[1] [0]: https://github.com/antirez/kilo/

Or Micro[0] [0]: https://github.com/zyedidia/micro

Micro is nice because it is a single-file, stand-alone executable that has mouse support, macro record/playback and syntax highlighting. (I haven't checked Nano recently). It is great for making quick edits to json configs, shell scripts, python scripts, etc. Syntax highlighting and line numbering are key. If I need to make a really quick edit, it is much faster to use this than waiting for VS Code or PyCharm to load. You also stay focused. By this I mean, your eyes don't leave the terminal window that you are currently working in. This allows me to more quickly complete the task at hand.

Re: Edit is now open source

#82

Post by karunamurti »

lhecker wrote: post #53

Hey all! I made this! I really hope you like it and if you don't, please open an issue: https://github.com/microsoft/edit To respond to some of the questions or those parts I personally find interesting: The custom TUI library is so that I can write a plugin model around a C ABI. Existing TUI frameworks that I found and were popular usually didn't map well to plain C. Others were just too large. The arena allocator e…

Why not webassembly ABI?

Re: Edit is now open source

#83

Post by qingcharles »

lhecker wrote: post #53

Hey all! I made this! I really hope you like it and if you don't, please open an issue: https://github.com/microsoft/edit To respond to some of the questions or those parts I personally find interesting: The custom TUI library is so that I can write a plugin model around a C ABI. Existing TUI frameworks that I found and were popular usually didn't map well to plain C. Others were just too large. The arena allocator e…

Why Rust over a compiled .NET lang? (e.g. C#)

Re: Edit is now open source

#84

Post by mplanchard »

criddell wrote: post #59
porcoda wrote: post #50

Earlier quoted context omitted.

I’m guessing this isn’t just to optimize for binary size. If you have the resources to avoid third party dependencies you eliminate the burden of having to build a trust case for the third party supply chain. That is the number one reason we sometimes reimplement things instead of using third party packages where I work: the risk from dependencies along with the effort required to establish that we can trust them is…

Microsoft has recently said AI writes 30% of their code. Reimplementing things isn’t as expensive as it once was.

I took a glance around this project, and it seems to be really high quality Rust. I would be shocked if it was AI-generated to any significant degree, given my own less-than-impressive results trying to get LLMs to write Rust.

Edit: I see the author isn’t very familiar with Rust, which makes it even more impressive.

Re: Edit is now open source

#86

Post by thaumasiotes »

Weird choice of name for their new software, given there is already a pretty prominent editor from Microsoft named "edit".

https://en.wikipedia.org/wiki/MS-DOS_Editor

They seem to have given it the same name because they want to preserve the command. But the headline is... misleading.

Re: Edit is now open source

#87

Post by emmelaich »

6c696e7578 wrote: post #43
arghwhat wrote: post #3

Yay for finally having a default text editor that works over ssh. Managing windows servers over ssh is a bit of a pain without. They could just have packaged nano, but oh well.

I am truly behind the times. I didn't know you can ssh into a Windows system.

You can also run a ssh server in WSL2. You'll need to proxy connections to it or run a vpn though to have it visible from the outside. I use tailscale.

Re: Edit is now open source

#88

Post by lhecker »

qingcharles wrote: post #83
lhecker wrote: post #53

Hey all! I made this! I really hope you like it and if you don't, please open an issue: https://github.com/microsoft/edit To respond to some of the questions or those parts I personally find interesting: The custom TUI library is so that I can write a plugin model around a C ABI. Existing TUI frameworks that I found and were popular usually didn't map well to plain C. Others were just too large. The arena allocator e…

Why Rust over a compiled .NET lang? (e.g. C#)

Pretty much exclusively binary size. Even with AOT C# is still too large. Otherwise, I wouldn't have minded using it. I believe SIMD is a requirement for writing a performant editor, but outside of that, it really doesn't need to be a language like C or Rust.

Re: Edit is now open source

#89

Post by lhecker »

karunamurti wrote: post #82
lhecker wrote: post #53

Hey all! I made this! I really hope you like it and if you don't, please open an issue: https://github.com/microsoft/edit To respond to some of the questions or those parts I personally find interesting: The custom TUI library is so that I can write a plugin model around a C ABI. Existing TUI frameworks that I found and were popular usually didn't map well to plain C. Others were just too large. The arena allocator e…

Why not webassembly ABI?

I'm not familiar with that, so I can't say. If you have any links on that topic, I'd appreciate it.

Generally speaking, the requirement on my end is that whatever we use is as minimal as it gets: Minimal binary size overhead and minimal performance overhead. It also needs to be cross-platform of course. This for instance precludes the widely used WinRT ABI that's being used nowadays on Windows.

Post reply on HN