141–150 of 158 posts
Earlier quoted context omitted.
npm is certainly not something everyone has.
Not everyone it's a web developer. Sysadmin and system programmers (and older millenials) don't care and don't want to install anything related to NPM.
Earlier quoted context omitted.
Thing is… who is regularly running `npm update` or `cargo update` to keep local software up to date? I wouldn’t, because I might be in a repo and it starts upgrading all my local dependencies, and I’m not gonna add a text editor as a dev dependency. I’ll happily take the binary, or a tar.gz with the binary in it, though. (Btw I love how it’s following the old DOS aesthetic)
The npm distribution here is just the binary, you run npm install again and it upgrades to the latest binary. That's convenient
Dear Santa, this year I don’t need gadgets - all I want is a Borland Turbo Vision–style console text editor with windows, tabs, and syntax highlighting. I promise to be good and keep my code compiling.
How 'bout the editor that ships with Lazarus?
How complete is the LSP feature support? Could we also get support for tree-sitter parsers and DAP (Debug Adapter Protocol) for an integrated debugging experience, just like the old Turbo and "Quick" text-mode IDEs?
LSP is working but requires polish. Go to definition, completion suggestions, inlay type hints and symbol highlighting are all working (probably not as pretty as they should) Tree-sitter is supported and used internally for a subset of languages for syntax highlighting (other languages use textmate grammars). What exactly do you mean by support for tree-sitter parsers? I wasn't aware of Debug Adapter Protocol! I'll t…
It's a great start of course, but even just documenting anything that's clearly still missing would be helpful.
Interesting license choice, would why did you choose version 2 instead of 3?
Honestly it reflects on my, uh, experience - I still think of GPLv3 as a "new" license. I don't have a particular reason. Maybe I should switch.
A very real example of that is that Ratatui (MIT license) and Codex (Apache2). I feel comfortable reading and using code and ideas from either side and have them influence the design of the other side [1][2]. I don't feel comfortable in the same way reading any GPL licensed code (2 or 3) due to the inherent legal risk that entails.
Your personal views on software freedoms definitely trump my personal opinion as a developer here, so I'm not too stressed if you disagree with this. A solid amount of crates in the rust ecosystem are MIT or Apache 2 (or both), and I really encourage authors of new libs, apps, to choose the same licenses for giving back in the same spirit.
[1]: https://github.com/openai/codex/blob/main/codex-rs/tui/src/c...
Add them to your comparison benchmarks.
Earlier quoted context omitted.
I get the frustration, but I think the npm option actually makes sense here. A lot of users who’d benefit from a fast Rust tool aren’t Rust developers and won’t have Cargo installed. Shipping it through npm lowers the barrier while still giving everyone the performance benefits. It’s not a knock on Cargo, just a way to make the tool more accessible.
npm is certainly not something everyone has.
Dear Santa, this year I don’t need gadgets - all I want is a Borland Turbo Vision–style console text editor with windows, tabs, and syntax highlighting. I promise to be good and keep my code compiling.
Thanks Santa.
If you are doing TUI, you can't miss Kakoune and Helix as popular editors. Add them to your comparison benchmarks.
Earlier quoted context omitted.
Can't it be packaged as a binary/whatever that would install without either cargo or npm?
You can use: cargo install fresh-editor Or you can use npm Or you can download release binary packages from Github releases. The problem is which option to make more prominent / first