I'm a little annoyed that for a Rust based tool the recommended installation command is to use npm. Why? Is Cargo not good enough? Cargo seems exceptionally well to me.
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.
Show HN: Fresh – A new terminal editor built in Rust
101–110 of 158 posts
Re: Show HN: Fresh – A new terminal editor built in Rust
#102Earlier quoted context omitted.
Thanks for reminding me. Unfortunately yes, it's because of v8 (for Deno). For extensions, the choice was either TypeScript (and get this bloat) or go with Lua and a much smaller binary (but less popular language). But - I just realized stripping it brings it down to 76MB so I guess that's ok! Will push a commit :)
> For extensions, the choice was either TypeScript (and get this bloat) or go with Lua and a much smaller binary (but less popular language). Incredible, the technical choice got overridden by popularity, leading straight to bloat
Re: Show HN: Fresh – A new terminal editor built in Rust
#103I'm a little annoyed that for a Rust based tool the recommended installation command is to use npm. Why? Is Cargo not good enough? Cargo seems exceptionally well to me.
Re: Show HN: Fresh – A new terminal editor built in Rust
#104I'm a little annoyed that for a Rust based tool the recommended installation command is to use npm. Why? Is Cargo not good enough? Cargo seems exceptionally well to me.
Can't it be packaged as a binary/whatever that would install without either cargo or npm?
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
Re: Show HN: Fresh – A new terminal editor built in Rust
#105You should put standard keyboard bindings as a pitch on the website as well. Most people in the market for a terminal editor are probably looking for something that doesn't require them to learn a set of keyboard shortcuts that's entirely different from every other piece of software that they use. I searched for that desperately until I discovered micro[1]. Here's a quick comparison between micro and fresh: - Fresh i…
Getting included in distributions is a worthy goal... So many things to do
Re: Show HN: Fresh – A new terminal editor built in Rust
#106Earlier 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.
Re: Show HN: Fresh – A new terminal editor built in Rust
#107I'm a little annoyed that for a Rust based tool the recommended installation command is to use npm. Why? Is Cargo not good enough? Cargo seems exceptionally well to me.
I did it because not everybody has cargo installed. I'm using cargo-dist to create this npm package.
Re: Show HN: Fresh – A new terminal editor built in Rust
#108Good keybindings, some are missing compared to what normally works, e.g., in the browser text input area or in gnome-text-editor (Ctrl-Shift-Up/Down was one I directly ran into). I've found https://github.com/gphalkes/tilde to work quite well, it also supports the system clipboard. Nice to see a Rust alternative.
ctrl+shift+up/down - not sure what you mean it to do? In VSCode it adds multiple cursors directly above/below. In other editors I think it moves (shifts) the current line up or down.