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

111–120 of 191 posts

Re: Edit is now open source

#111

Post by divbzero »

arghwhat wrote: post #79
zozbot234 wrote: post #44

Earlier quoted context omitted.

This could be a great text-mode IDE with the addition of some LSP, tree-sitter and DAP support. There is already an open issue about possibly adding support for tree-sitter grammars for fast syntax highlighting, but they do mention that this requires some sort of optional plugin system to avoid bloating up the codebase severely (for example, the tree-sitter grammars within the Helix editor take up hundreds of megabyt…

That just feels like scope creep. Notepad would also be neat with some better keybinding support, plugins, lsp, ... - but then it wouldn't be notepad, and theres countless not notepads out there. Tools like nano (well, pico) exist to provide a reliable and always available minimum feature set. If you expand it, then you end up with something that is neither the minimum nor capable enough to sensibly compete with full…

Well, Notepad is introducing AI support which already feels like scope creep to me…

https://support.microsoft.com/en-us/windows/enhance-your-wri...

Re: Edit is now open source

#113

Post by mixmastamyk »

Ericson2314 wrote: post #37
fredoralive wrote: post #35

Earlier quoted context omitted.

64 bit Windows, the only sort now with W11, doesn’t have MS-DOS support, so doesn’t have the old edit to start with.

Didn't know 32-bit Windows was completely gone.

DOS was extended to 16-bit. ;-)

Re: Edit is now open source

#114

Post by dmos62 »

geysersam wrote: post #109
criddell wrote: post #59

Earlier quoted context omitted.

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

How much cost reduction does 30% ai written code translate to? It's easy to imagine that ai doesn't write the most expensive lines of code. So it might correspond to 10% cost reduction. 10% is nothing to scoff at, but I don't think it should factor into the decision to rewrite existing packages or trust third parties if you're very security minded.

AI-writing has the cost of human orchestration, debugging, review. Code is now cheap to write, but for there to be a net efficiency gain, those other tasks have to not bloat too much.

Re: Edit is now open source

#115

Post by [deleted] »

andyferris wrote: post #74

I have to say, I really miss MS-DOS TUI apps like edit, the qbasic editor, and xtree-gold. The linux-terminal based ones just seem a bit off in comparison. Maybe it's mouse and keyboard support in terminals (shift-enter support, anyone?) aren't great? People have different aesthetics? I don't know... Next stop: VS-EDIT would be pretty cool :) (This with LSPs)

[deleted]

Re: Edit is now open source

#116

Post by dmos62 »

eviks wrote: post #108
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…

> So, why not have fun learning something new, writing most things myself? I definitely learned tons working on this, which I can now use in other projects as well. Because presumably you should have been doing it mostly for the benefit of Windows users, and wasting time because it’s a fun personal learning exercise means those users would suffer getting an underpowered app

Wow, what a disheartening comment. Did GP not explain why they did what they did? This is an open-source project, the author expressed joy in working on it, and you have the heart to tell him off. This is far below what I expect of HN.

Re: Edit is now open source

#118

Post by eviks »

dmos62 wrote: post #116
eviks wrote: post #108

Earlier quoted context omitted.

> So, why not have fun learning something new, writing most things myself? I definitely learned tons working on this, which I can now use in other projects as well. Because presumably you should have been doing it mostly for the benefit of Windows users, and wasting time because it’s a fun personal learning exercise means those users would suffer getting an underpowered app

Wow, what a disheartening comment. Did GP not explain why they did what they did? This is an open-source project, the author expressed joy in working on it, and you have the heart to tell him off. This is far below what I expect of HN.

Did the comment not explain what the issue with that explanation is?

But maybe if you didn't misrepresent the situation so much you wouldn't lose your heart. This is not some tiny personal open source project where fun can be the only valid reason, but "will ship as part of Windows 11!", so millions of devices in a professional OS. Are your expectations so poorly calibrated that you have none in both cases? Why are they higher re. a forum comment?

Re: Edit is now open source

#119

Post by fredoralive »

JdeBP wrote: post #102
Ericson2314 wrote: post #37

Earlier quoted context omitted.

Didn't know 32-bit Windows was completely gone.

It's not even that 32-bit Windows is gone. It's that NTVDM is (years ago) gone. See discussion elsewhere on this very page.

AFAIK all 32-bit x86 versions of Windows 10 have NTVDM as an option, it's the dropping of 32-bit kernel Windows with Windows 11 that finally killed it.

Re: Edit is now open source

#120

Post by alternatex »

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.

Microsoft has no metric to track this and I can guarantee you that statement is for marketing purposes.
Post reply on HN