News for hackers. Stuff that matters.
Re:Amp – A complete text editor for the terminal by mario0b1 on Thursday November 22, 2018 @02:33AM (#18508477)
>A modal, keyboard-driven interface inspired by Vim that makes navigating and editing text fast.

But what does it do different than vim? Having competition is good, but I don't see any "that's why you should use amp and not vim"-reason. Where is it?

Re:Amp – A complete text editor for the terminal by tbrock on Thursday November 22, 2018 @07:32AM (#18509596)
I thought it was pretty clear actually: it works out of the box with no configuration (batteries included).

> Amp is complete from the start.

As a long time vim user, the more advanced you get the more customized your vimrc and plugins become and you aren’t able to just walk up to vim somewhere else and be efficient (pairing with another vim user becomes impossible). Shared defaults are a powerful thing! Convention over configuration.

Imagine we even both like using the nerd tree plugin but can’t agree what the leader key should be mapped to in order to activate it: a common problem.

That’s why you see the most advanced vim users go back to a minimal vimrc which admittedly makes it a less useful editor.

I think we can all agree vims defaults are crap and without plugins it doesn’t have all of the features of a modern editor.

Re:Amp – A complete text editor for the terminal by phlyingpenguin on Thursday November 22, 2018 @07:51AM (#18509676)
> it works out of the box with no configuration (batteries included).

You don't really believe that, do you? Competent users tend to have preferences. There's no need to worry about installing plugins if you have to have a .vimrc to begin with, just have the .vimrc do the installing as well.

Re:Amp – A complete text editor for the terminal by ronjouch on Thursday November 22, 2018 @08:16AM (#18509794)
Sure, but "Competent users tend to have preferences" doesn't exclude slow evolution of sane-by-default preferences for programs part of a same class. A newcomer text editor, say, comes in town, settles its default configuration as the sanest of previous generations, while existing programs of the same class are (reasonably!) stuck due to compatibility.

Which means newcomer text editors need less configuration, and users generally staying closer to the default stable, tested configuration.

You can argue that you're part of a margin needing XYZ specific setting, or that new programs don't necessarily make good default config choices. To me it feels generally reasonable to believe so.

Case in point, with text editors / light IDEs. I did Sublime Text -> Atom -> VSCode. At each step, the size of my config size decreased. Of course I still have a VSCode settings.json, but it's twenty lines. My sublime prefs are ~100 lines, my .vimrc is hundreds :)

Re:Amp – A complete text editor for the terminal by phlyingpenguin on Thursday November 22, 2018 @08:31AM (#18509878)
The plugins you need to make Atom/VSCode great (no experience with modern Sublime) definitely count as configuration in my book, and often come with their own configuration load. If I sit down at a new machine, they won't be there. Most of my .vimrc is a couple of lines per plugin configuring the plugins, for example.
Re:Amp – A complete text editor for the terminal by wasted_intel on Thursday November 22, 2018 @09:46AM (#18510249)
You're going to get a fuzzy file finder, Git integration, syntax highlighting, symbol navigation, and and a package manager immediately available to you in those editors. None of those are available in Vim by default; that's the inspiration for Amp.

There are additional perks to including things by default, too. Jump mode is a good example of that: it's integrated with its select mode. You can start a selection and then switch to jump mode to move the cursor to complete the selection.

Lastly, there's simplicity in including things rather than asking new users to pick from a dizzying array of plug-in options. Rails is a good example of this: there's a lot of functionality that could have been left to 3rd-party gems, but having the framework include them by default means they'll work out of the box, and there's a single canonical solution to [sessions, templates, ORM, routing, etc].

Re:Amp – A complete text editor for the terminal by kingosticks on Thursday November 22, 2018 @10:39AM (#18510579)
I don't disagree with your approach but I'd just point out, since it's a little ironic, that rust's standard library is a good example of the opposite approach!
Re:Amp – A complete text editor for the terminal by wasted_intel on Thursday November 22, 2018 @10:55AM (#18510677)
You're absolutely right. :)

I'm going to resist adding everything but the kitchen sink to Amp. Upcoming features like tasks and language server protocol support will allow Amp to integrate with language/framework-specific tools as easily as possible, but without steering Amp towards any specific choices. I couldn't avoid that with syntax highlighting; it's just too essential (and it powers the symbol jump mode). It's definitely a balancing act!

Re:Amp – A complete text editor for the terminal by paavoova on Thursday November 22, 2018 @12:11PM (#18511160)
Vim doesn't have syntax highlighting? News to me. Git and file finder is available to you by opening a new terminal tab/window and simply using git/standard unix utils. There's no need to integrate such features when you can extend a terminal into an IDE as your needs suit.
Re:Amp – A complete text editor for the terminal by wasted_intel on Thursday November 22, 2018 @12:22PM (#18511220)
Vim has very simple highlighting, and doesn't support symbol jump; that's why ctags is an external dependency for that behaviour.

As for a file finder, I'm curious how you can use a separate tab to open that in the current instance of Vim? From when I'd last used it, most folks were using Ctrl-P to solve that problem, and usually with an external indexer like fzf or ag.

Re:Amp – A complete text editor for the terminal by oblio on Thursday November 22, 2018 @08:11AM (#18509773)
Fragmentation also hurts the ecosystem. Just look at Linux distributions or desktop environments to see the effects.

The best thing is to provide some sensible overridable defaults and basic functionality expected these days from a programmer's editor, such as simple project management: index files, fuzzy file finder, etc. Vim and Emacs are a pain in the butt for precisely this reason: they don't take ANY decision, they just throw the entire burden on the user. They're forgiven because they're classics, but any kind of editor launched in 2018 would be utterly ignored if it didn't have these features.

Re:Amp – A complete text editor for the terminal by wiz21c on Thursday November 22, 2018 @08:52AM (#18509978)
>> Fragmentation also hurts the ecosystem. Just look at Linux distributions or desktop environments to see the effects.

I don't think so. I've never felt that having 10 linux distributions was a problem, I just can pick between at least two super robust choices : Debain, RedHat. I can even choose between inkscape, krita, gimp. Or KDE and Gnome...

You can argue that progress would be faster if we have less choices but more choices also means more developpers...

Re:Amp – A complete text editor for the terminal by PurpleRamen on Thursday November 22, 2018 @10:55AM (#18510674)
Choice is a process which can hurt when it takes too long or when you lack the ability to execute the process itself or in a good manner.

See https://en.wikipedia.org/wiki/Overchoice and https://en.wikipedia.org/wiki/Analysis_paralysis

This is BTW no limited to OSS but AFAIK it comes from sales-research. People confronted with to many products of similar type can end in a deadlock, avoiding those products or even start to avoid the whole category.

> You can argue that progress would be faster if we have less choices but more choices also means more developpers...

More developers reinventing the wheel doesn't automatically make the wheels faster. It can mean healthy competition, but it also can mean wasted ressources. It's case by case.

Re:Amp – A complete text editor for the terminal by wiz21c on Friday November 23, 2018 @08:48AM (#18516366)
yup, now that I read myself again, I see my bias. For me, more developpers working on several "identical" GPL'ed software makes the viability of the GPL software better... So, well, I'm biased :-)
Re:Amp – A complete text editor for the terminal by lvncelot on Thursday November 22, 2018 @02:41PM (#18512068)
On the one hand, I agree. I've spent whole days just checking out software alternatives, booting new distros, DEs, hosting webapps, just to see what they were like, and it's always great fun.

On the other hand it can hurt - for example I'd like to have my main workstation running mainly one gui framework. (Or at least, most of the software). But the KDE/GTK split makes the most popular and sensible software to use for most cases pretty much evenly distributed between those two. (Though this is obviously not a major issue, just an example).

Re:Amp – A complete text editor for the terminal by oblio on Thursday November 22, 2018 @09:12AM (#18510061)
It definitely hurts mainstream adoption. And it also kills distribution of most commercial desktop applications.
Re:Amp – A complete text editor for the terminal by wasted_intel on Thursday November 22, 2018 @08:08AM (#18509754)
Amp, and convention over configuration in general, don't prevent configuration, they just try to avoid it. There are a bunch of things you can configure in Amp, if you'd like: https://amp.rs/docs/#configuration
Re:Amp – A complete text editor for the terminal by phlyingpenguin on Thursday November 22, 2018 @08:18AM (#18509808)
That's not really what I was doubting (I could see that). I just doubt that it's likely to not need a configuration file if I were to replace vim with it. In GP's assertion that this is the best reason to use Amp over vim, that's not really a huge benefit in the end. A config is a config is a config, or something to that effect.
Re:Amp – A complete text editor for the terminal by wasted_intel on Thursday November 22, 2018 @09:21AM (#18510109)
Unfortunately, configuring Vim is rarely just pulling a config file. Pathogen and Vundle have made installing/tracking plug-ins easier, but unless things have changed, those tools required their own bootstrapping outside of simply being referenced in the config.

And that's just for Vimscript plug-ins. There are several situations (e.g. fuzzy file finders) where external binaries are preferable, for performance reasons. The idea is to include those directly in Amp, so that it's _only_ a configuration file that's needed, if at all.

Re:Amp – A complete text editor for the terminal by phlyingpenguin on Thursday November 22, 2018 @12:01PM (#18511090)
All depends on your taste. My .vimrc handles ensuring that I have a plugin manager installed and that it installs those plugins on my behalf if they aren't there. And I do all of that in ~10 lines of vimL config. It's totally reasonable to have your plugin/config ensure the external binaries exist as well. The popular golang plugin has a command for that.
Re:Amp – A complete text editor for the terminal by wasted_intel on Thursday November 22, 2018 @12:18PM (#18511198)
It ensures you have a plug-in manager installed, but it won't install it for you, right? I know that might seem like a minor nit, but if package management is considered an essential part of Vim, I'm of the mindset that it should work out of the box.

That said, Amp doesn't have plug-in support at the moment, so it's a little unfair for me to judge Vim on that front. But if it did, the package management portion would be baked in so that you'd only need to pull your configuration file and Amp would handle the rest. :)

Re:Amp – A complete text editor for the terminal by phlyingpenguin on Thursday November 22, 2018 @12:51PM (#18511369)
No. I have it install the manager. Literally all I need is the .vimrc and to start vim.
Re:Amp – A complete text editor for the terminal by Mashimo on Thursday November 22, 2018 @08:02AM (#18509731)
I have not tried amp yet, but just as an example why I switched shell. I use fish shell because of the sane defaults. I don't want to be bothered with setting up code completion and history size.

Just install it and use it. Works.

I like projects that provide similar experience.

Re:Amp – A complete text editor for the terminal by wasted_intel on Thursday November 22, 2018 @01:09PM (#18511476)
Yes, fish shell is a beautiful example of that philosophy! Its design documentation[0] reflects a lot of the values that drove me to create Amp.

[0] https://fishshell.com/docs/current/design.html

Re:Amp – A complete text editor for the terminal by tbrock on Thursday November 22, 2018 @10:26PM (#18514140)
Also see: Ruby on Rails
Re:Amp – A complete text editor for the terminal by wasted_intel on Thursday November 22, 2018 @10:30PM (#18514154)
Yep, another great example. :)
Re:Amp – A complete text editor for the terminal by tbrock on Thursday November 22, 2018 @10:25PM (#18514129)
Yes I do. Ever use textmate or Atom? Sure you can configure a bunch of keys if you want to change them but nobody ever does.
Re:Amp – A complete text editor for the terminal by sfifs on Friday November 23, 2018 @06:37AM (#18515861)
This discussion reminds me of the classic "standards" xkcd

https://xkcd.com/927/

Re:Amp – A complete text editor for the terminal by lunchables on Thursday November 22, 2018 @12:03PM (#18511108)
>and you aren’t able to just walk up to vim somewhere else

Is this something people do? I use a handful of machines and use git+stow for managing my vimrc. I've never had this problem where I need to "walk up to vim somewhere else" where I wouldnt just clone my dotfiles and stow my vim config. Takes all of 10 seconds and I'm up and running.

Re:Amp – A complete text editor for the terminal by jolmg on Thursday November 22, 2018 @02:15PM (#18511905)
I often need to use vim in servers that are not solely administered by me. It seems like bad etiquette to impose my configuration on my co-workers, so we leave it mostly unconfigured on these servers. There's also cases where I want to use vim in docker containers running web servers to debug by tracing execution in installed libraries by inserting prints and repl launching function calls, etc. It doesn't make sense to bother installing configuration each time the docker image is rebuilt, or including vim's installation and configuration in the Dockerfile.

I just do this minimal configuration on starting vim:

    :se et ai ts=2 sts=2 sw=2
Just that makes it usable enough for me to not feel a productivity loss most of the time.

EDIT: Key to that is not being so reliant on plugins, of course. I used to use a lot of plugins, but then focused on learning more of stock vim features, and doing more things in the shell. I now feel more productive without the plugins.

For example, I used to use NERDTree, but now I opt for using :e's path syntax. I don't get lost looking for files in the tree, scrolling around, opening directories. I just type stuff like :e %:h/fi<tab><enter> or :e %:s?local?global?<enter> to get straight to where I want without having to look at anything. I can probably work in vim blind-folded without a productivity loss (the only problem being remembering enough of the files I'm working on) and I find that awesome.

Re:Amp – A complete text editor for the terminal by ShinTakuya on Thursday November 22, 2018 @02:47PM (#18512101)
You're sharing accounts on servers or logging in directly as root? Either one sounds like a recipe for disaster.
Re:Amp – A complete text editor for the terminal by jolmg on Thursday November 22, 2018 @03:25PM (#18512296)
Sharing a normal user account. It's not ideal, but it's not that bad either. I think you're missing a lot of context to properly judge this, but to keep it short and avoid divulging details it boils down to balancing costs, risks, and benefits. Remember you know nothing about my work. It's easy to underestimate costs, overestimate the risks, and overestimate benefits without being fully informed of the situation.
Re:Amp – A complete text editor for the terminal by em-bee on Sunday November 25, 2018 @03:13AM (#18525943)
i switched away from emacs, and learned vi just because of that. to many servers with different versions of unix to make it worth the effort to install a different editor or customize its configuration.
Re:Amp – A complete text editor for the terminal by jhillyerd on Thursday November 22, 2018 @01:06PM (#18511454)
I'd say yes; there are many times I've ssh'd into a server and wanted to do a quick edit where I don't have my vimrc; not going to bother to install it.

Complexity increases when you want one vimrc with many plugins to work on Windows, Linux and OS X, and both in your work and home environments.

I'm not arguing that Amp is the answer. I don't think I'd stick with vim as my daily driver if I couldn't customize it, and have the plugins I do.

Re:Amp – A complete text editor for the terminal by etrautmann on Thursday November 22, 2018 @01:06PM (#18511458)
In my routine work in an academic lab, im using 10-15 machines plus a number of GCP instances. Syncing a .dotfiles repo is a huge pain, especially when you make a small change on one machine and don’t want to push/pull ever time you want to do anything on another machine.
Re:Amp – A complete text editor for the terminal by wting on Thursday November 22, 2018 @01:48PM (#18511749)
I fixed this problem for myself by automatically pulling down changes in the background upon opening a new terminal.

Since checking on every terminal open is unnecessary, I check on a probabilistic basis based on how often the backing git repo changes (0.5% - 3%, different repos for vim, dotfiles, configs).

Re:Amp – A complete text editor for the terminal by enriquto on Thursday November 22, 2018 @12:10PM (#18511144)
> I thought it was pretty clear actually: it works out of the box with no configuration (batteries included).

Actually, no. This is not clear at all looking at the website. Unless you assume that vim does not come with "batteries included", which sounds wrong to me. I for one use "raw" vim, without plugins nor configuration, and I am very happy with it.

(Strictly speaking, this is false: I have "set t_ti= t_te=" in my .vimrc so that the screen is not cleared when I exit, but I suppose this kind of fringe features are OK to be user-specified).

Re:Amp – A complete text editor for the terminal by joombaga on Thursday November 22, 2018 @12:19PM (#18511205)
> I have "set t_ti= t_te=" in my .vimrc so that the screen is not cleared when I exit

Oh wow, this is super helpful. Thank you!

Re:Amp – A complete text editor for the terminal by platz on Thursday November 22, 2018 @03:35PM (#18512378)
wish neovim could do that too
Re:Amp – A complete text editor for the terminal by slim on Thursday November 22, 2018 @12:21PM (#18511211)
Thanks for the tip
Re:Amp – A complete text editor for the terminal by beatgammit on Thursday November 22, 2018 @09:51AM (#18510283)
I use vim because I don't want the features of a "modern" text editor. My .vimrc is fairly basic at under 100 lines, and I only have a few plugins, which is mostly syntax files and syntastic.

I don't use stuff like NerdTree (I used to, but ended up not liking it), and mostly just stick to the features that come with it. As such, I can be very productive without much configuration at all, which is much of the reason I used vim in the first place.

I don't want another spin of vim because I lose one of its biggest benefits: ubiquity. The further I deviate from the base configuration, the less useful having vim available everywhere is.

Re:Amp – A complete text editor for the terminal by wasted_intel on Thursday November 22, 2018 @10:41AM (#18510592)
I can appreciate that. Amp's keybindings are fairly close to Vim's, so it's not like you lose the muscle memory you've built over the years.

Amp's additional features are really geared towards project-based development, so ubiquity isn't as much of a concern; it's not meant for editing sporadic config files on your server. Vim is still a great fit for that, at least until someone gets Amp adopted into the main Ubuntu server repositories. ;)

Re:Amp – A complete text editor for the terminal by craftyguy on Thursday November 22, 2018 @10:06AM (#18510355)
> Unlike Vim, Amp doesn't provide split panes, and support isn't planned

That's a pretty big missing feature that is included in vanilla vim...

Re:Amp – A complete text editor for the terminal by wasted_intel on Thursday November 22, 2018 @10:44AM (#18510607)
100% deferring to tmux, there. It just adds so many great features, I think it'd be a mistake to re-implement them in Amp. Paired with the fact that Amp is cheap on memory, and has native clipboard integration, this isn't as necessary as you might think; you can still move content between panes! :)
Re:Amp – A complete text editor for the terminal by em-bee on Thursday November 22, 2018 @11:27AM (#18510896)
with split panes in vim i can have the same file open at two different places. can't do that with split panes in tmux.

greetings, eMBee.

Re:Amp – A complete text editor for the terminal by wasted_intel on Thursday November 22, 2018 @11:50AM (#18511034)
Ah, you're right; thanks for clarifying!
Re:Amp – A complete text editor for the terminal by em-bee on Saturday November 24, 2018 @05:26AM (#18521382)
also, i developed a plugin for vim that compiles code for me and sends the output to a second buffer.

sure i can make that work with tmux. codewise it would even be easier, but only if i can trust the user to put all the pieces together for themselves.

if i want to build an end-user friendly package, the whole thing suddenly becomes a lot more complex:

it's no longer enough to say: load this into vim and you are done, but i need to check that tmux is not only available but that the editor is running inside it as well. and i have to prepare that users will ask me to make this work with screen or any other tmux alternative.

greetings, eMBee.

Re:Amp – A complete text editor for the terminal by wasted_intel on Saturday November 24, 2018 @09:02PM (#18525005)
It's possible to run a command in another tmux pane; I forget the specific syntax but I've tested this in the past and it works. The only thing the editor needs is a task runner (this is a planned feature for Amp); the task that's run is prefixed with the tmux command that triggers it in another pane.

The only thing that's bespoke to tmux is knowing which pane to target; you'd need to collect that from the user on the first run, or allow the value to be configured.

Re:Amp – A complete text editor for the terminal by em-bee on Saturday November 24, 2018 @11:10PM (#18525423)
i would split the current pane by default, and allow the user to define the whole tmux command used to splitting. (that way they can even replace tmux with something else that works instead.
Re:Amp – A complete text editor for the terminal by MaxBarraclough on Thursday November 22, 2018 @10:10AM (#18510381)
Could make do with tmux panes I suppose, but I agree, if you're going to go head to head with Vim that's a big omission.
Re:Amp – A complete text editor for the terminal by fouc on Thursday November 22, 2018 @10:36AM (#18510560)
Why not just rely on tmux panes?
Re:Amp – A complete text editor for the terminal by MaxBarraclough on Thursday November 22, 2018 @11:54AM (#18511052)
It'd prevent me using the Vim clipboard ('registers') between files. That's bad enough. It'd also prevent me using Vim macros to easily shuttle data between files.

I may also want to ctrl-z Vim to run a few quick commands before resuming Vim with fg. Using tmux panes, I'd only get a small window to run those few commands, which doesn't reflect my intent. (Yes, I could use another tmux window for this, but I like this way.)

I suspect it would also mean more keystrokes.

Re:Amp – A complete text editor for the terminal by wasted_intel on Thursday November 22, 2018 @01:06PM (#18511453)
Amp has native clipboard integration, so content will carry between different instances. Configuring the register => clipboard was something I personally disliked when configuring Vim.

Amp also supports suspending (hit "z" in normal mode) as I use that workflow all the time. As for the small window issue, you can "zoom" a tmux panel with <leader>-z. I get that this is less than ideal if you're used to the suspend action collapsing all panes by default (and expanding them on resume). Workflows are tricky; to each their own, I guess! :)

Re:Amp – A complete text editor for the terminal by jolmg on Thursday November 22, 2018 @01:49PM (#18511757)
> Amp has native clipboard integration, so content will carry between different instances

By "native" does that mean an X-server's clipboard? So when you're running it on a machine that has no X-server running (a typical server), there is no clipboard?

Re:Amp – A complete text editor for the terminal by wasted_intel on Thursday November 22, 2018 @02:05PM (#18511843)
Amp has an internal clipboard that it synchronizes to an external/native equivalent, if available. You'd still be able to copy/paste within a single Amp process, but you would lose the ability to do the same between separate processes.
Re:Amp – A complete text editor for the terminal by jolmg on Thursday November 22, 2018 @03:41PM (#18512411)
Right, so in the context of this discussion, tmux panes are not a good substitute for vim windows, since you wouldn't be able to copy-paste between them unless what you were copying fit in a single pane-full.
Re:Amp – A complete text editor for the terminal by wasted_intel on Thursday November 22, 2018 @03:49PM (#18512460)
Yes, that's correct. :)

In that scenario, I would compromise by opening both files in the same Amp process and switch between them, but that's not the same as seeing both at the same time.

Re:Amp – A complete text editor for the terminal by Narishma on Thursday November 22, 2018 @10:51AM (#18510653)
Not everybody uses tmux for one.
Re:Amp – A complete text editor for the terminal by wasted_intel on Thursday November 22, 2018 @08:02AM (#18509732)
Author of amp here and I couldn't have explained this any better.
Re:Amp – A complete text editor for the terminal by superflyguy on Thursday November 22, 2018 @02:00PM (#18511809)
Even if you were someone for whom the page is clear, you might still be confused by why someone who would need to take a not insignificant amount of time getting their development machine installed and configured correctly but would balk at having to type - just once at any point during the lifetime of their laptop - a single git clone to pull down their config.

Neovim (https://neovim.io/) makes a thing about how it's got "strong defaults" but there's got to be the least compelling reason to use it.

Newcomers to vim are generally encouraged to use it as-is and make their own config changes as and when they need to, and experienced users will have config which gets enhanced to meet whatever circumstances they're confronted with, but none of this requires a completely different editor.

Re:Amp – A complete text editor for the terminal by wasted_intel on Friday November 23, 2018 @01:37PM (#18518129)
There are quite a few areas where Amp diverges from Vim; minimal configuration is just one of those. It's inspired by Vim, but it's not a clone. Yes, it's modal, and yes it's a TUI app, but there's much more to these editors than that.

That said, I think it's pretty clear one of the first things I need to add to the website is an answer to "why would I use this instead of Vim"?

Re:Amp – A complete text editor for the terminal by fouc on Thursday November 22, 2018 @10:35AM (#18510549)
Finally.. the irssi of editors.

The popular irc clients (terminal-based) like ircII used to require a lot of configuration and setup to get going. Eventually irssi appeared, with sane out of the box defaults, including a dash of color.

I always thought we needed something similar for text editors.

Re:Amp – A complete text editor for the terminal by wiz21c on Thursday November 22, 2018 @08:55AM (#18509994)
As an emacs user, I have a medium sized .emacs config file. Moving from one emacs to another just imply reinstalling 2 or 3 packages and copying my emacs file. That's no hard work.

And whenever I need to use somene else's emacs, it's even simpler : there's no emacs in the real world :-) (neither vim :-)) I mean those are "niche" editors, not used in huge parts of the IT world. So worrying about their ecosystem is a bit, well, exagerated, imho.

Re:Amp – A complete text editor for the terminal by dragonwriter on Friday November 23, 2018 @02:43PM (#18518488)
> I thought it was pretty clear actually: it works out of the box with no configuration (batteries included).

Vim works out of the box (heck, even old-school vi did.) Amp seems to provide more out of the box, but also explicitly states plans a runtime and plug-in support for extensibility, so apparently it still recognizes that complete out of the box is an unattainable goal given diversity (and conflict) of user needs.

Re:Amp – A complete text editor for the terminal by Cyphase on Thursday November 22, 2018 @04:04AM (#18508806)
I think one of the main reasons it exists is that it's written in Rust. One clue is that the TLD is .rs, plus there's been a lot of "a <type-of-program> written in Rust" lately. Which is fine; it's just an observation. I myself am going to be getting into Rust soon, hopefully.
Re:Amp – A complete text editor for the terminal by wasted_intel on Thursday November 22, 2018 @08:18AM (#18509807)
Yes, this is definitely one reason. At the time, I was interested in working on Vim, but it's hard to make changes to a C codebase and be confident you won't introduce segfaults or subtle memory safety issues.

Rust's "hack without fear" mantra definitely applied here. :)

Re:Amp – A complete text editor for the terminal by monotypical on Thursday November 22, 2018 @06:45AM (#18509408)
being written in rust might make it more appealing to develop, but it doesn't give any benefit to the user and I can't see it being a reason for someone to use this over vim
Re:Amp – A complete text editor for the terminal by DC-3 on Thursday November 22, 2018 @07:44AM (#18509650)
Rust programs tend to be more stable, more efficient, and more highly parallelized than equivalents written in other languages by developers of the same quality.
Re:Amp – A complete text editor for the terminal by __Joker on Thursday November 22, 2018 @07:54AM (#18509690)
Again, I am not sure when is the last time vim crashed on my *nix set up. Not trying to sound unreasonable but in this argument of VIM/amp it might not be relevant.
Re:Amp – A complete text editor for the terminal by gdfasfklshg4 on Thursday November 22, 2018 @08:05AM (#18509746)
It depends upon plugins. My Vim is quite prone to crashing but I'm fairly sure it is one of my plugins.
Re:Amp – A complete text editor for the terminal by petepete on Thursday November 22, 2018 @09:13AM (#18510065)
Yeah, more than likely. I'm down to just a handful of plugins and don't recall it crashing in the last couple of years, and I use it a lot.
Re:Amp – A complete text editor for the terminal by z3phyr on Thursday November 22, 2018 @09:46AM (#18510251)
False advertisement is false. Please refrain from such statements as it actually hurts the language more.
Re:Amp – A complete text editor for the terminal by gpm on Thursday November 22, 2018 @10:38AM (#18510574)
I think that that statement is true, the "tend to" and "same quality" are very important qualifiers though.
Re:Amp – A complete text editor for the terminal by tendencydriven on Thursday November 22, 2018 @05:31AM (#18509154)
I think it's a lot easier for someone to learn a new language, or learn the benefits of a new language, by recreating something which already exists.
Re:Amp – A complete text editor for the terminal by ranza on Thursday November 22, 2018 @06:37AM (#18509377)
I usually go for irc bots when trying to learn a new language. I already know the api and the thought process which makes it easier.
Re:Amp – A complete text editor for the terminal by danellis on Thursday November 22, 2018 @07:40AM (#18509630)
> there's been a lot of "a <type-of-program> written in Rust" lately

It's the new Go.

Re:Amp – A complete text editor for the terminal by patrickmcnamara on Thursday November 22, 2018 @05:21AM (#18509113)
I do wish there were more modal, terminal-based text editors that weren't so similar to Vim.

Kakoune is Vim-like, and now this.

Re:Amp – A complete text editor for the terminal by Koshkin on Thursday November 22, 2018 @08:29AM (#18509860)
> modal

Bill Joy: “One of the good things about EMACS, though, is its programmability and the modelessness. Those are two ideas which never occurred to me.”

“People don't know that vi was written for a world that doesn't exist anymore.”

Re:Amp – A complete text editor for the terminal by e17a on Friday November 23, 2018 @08:05AM (#18516146)
Oh, I so disagree. Modal editing is not about the modes.

In a text editor, user input either writes text to the file or does something else. Every text editor let you write to files so aside from aesthetics, it's the everything else that makes each different. If keystrokes for writing are not separated from keystrokes for everything else, everything else is confined to awkward ctrl- and alt- key combos. That's why it's a good idea to put them in different 'modes' so you can perform other actions comfortably. You don't need more modes than 2. Actually, in vim, you could see command mode and the visual modes as extensions of the normal node. Modes are really just a metaphor.

Re:Amp – A complete text editor for the terminal by ehsankia on Thursday November 22, 2018 @06:32AM (#18509354)
I on the other hand would like to see other non-modal editors. Vim is already the best and most customizable modal editor, but does anyone know a good non-modal editor beyond basic nano?
Re:Amp – A complete text editor for the terminal by travellingprog on Thursday November 22, 2018 @08:11AM (#18509774)
I've been using Joe's Own Editor the past couple of years when I want to do basic view/editing in terminal (I use Sublime Text for development). Really like it because it provides syntax highlighting for a ton of file types, let's me get around with arrow keys/mouse, and gives me an easy way to look up keyboard commands I may have forgotten.

https://joe-editor.sourceforge.io

You can install it with your OS's package management system, and there's a Windows installer on the site.

I did adjust some of the default settings, which are configured and well documented in a .joerc file.

Re:Amp – A complete text editor for the terminal by gnodar on Thursday November 22, 2018 @06:57AM (#18509461)
Re:Amp – A complete text editor for the terminal by rerx on Thursday November 22, 2018 @06:57AM (#18509463)
> Vim is already the best and most customizable modal editor

Weird statement. "Best" is up to debate, but "most customizable" is definitely Emacs.

I cannot really imagine a really good non-modal programmer's editor. Surely it should behave differently when editing Python compared to editing HTML?

Re:Amp – A complete text editor for the terminal by lake99 on Thursday November 22, 2018 @07:17AM (#18509539)
You're using the emacs definition of major modes. "Modal editor" has a different meaning. Vim has three modes [1]. Emacs is not considered a modal editor, but some of its features are similar to Vim's last-line mode.

[1] https://alvinalexander.com/linux/vim-vi-mode-editor-command-...

Re:Amp – A complete text editor for the terminal by rerx on Thursday November 22, 2018 @08:41AM (#18509914)
Run Emacs in Evil mode or similar and you get modal editing inside a special editor mode. If anything, Emacs is an extra-modal editor. :)
Re:Amp – A complete text editor for the terminal by v_lisivka on Thursday November 22, 2018 @08:19AM (#18509811)
Emacs is IDE, like Eclipse or Idea. It contains text editor, of course, but it much more than just text editor. It's not fair to compare say GEdit and Eclipse in terms of configurability, because GEdit is text editor, while Eclipse is IDE.
Re:Amp – A complete text editor for the terminal by v_lisivka on Thursday November 22, 2018 @07:49AM (#18509672)
mcedit (part of mc) in gnome-terminal currently the best non-modal editor, AFAIK, especially when you like to use mc to navigate file system.
Re:Amp – A complete text editor for the terminal by tonypace on Thursday November 22, 2018 @10:36AM (#18510558)
What an unfortunate name. All search results are for the Minecraft editor.

It's also fairly obtuse for non-experts. A champion non-modal editor would have a learning curve as shallow as nano but more depth that could reveal itself over time.

Re:Amp – A complete text editor for the terminal by hvis on Thursday November 22, 2018 @12:02PM (#18511101)
It predates Minecraft by about a decade, I think.
Re:Amp – A complete text editor for the terminal by jhasse on Thursday November 22, 2018 @07:24AM (#18509570)
Do you know about micro? https://github.com/zyedidia/micro
Re:Amp – A complete text editor for the terminal by jgtrosh on Thursday November 22, 2018 @05:57AM (#18509229)
It is indeed quite amazing how modal editing is usually defined by vi, which does so in very specific ways, when there are alternatives (like kakoune) which really show there's a whole spectrum of possible implementations of that idea. I wish there was a modal editor with the same scope as nano which would help introducing that concept to newcomers without aiming to maximize productivity / expressiveness.
Re:Amp – A complete text editor for the terminal by otikik on Thursday November 22, 2018 @06:22AM (#18509332)
Well, nano is modal. If you press CAPS LOCK you enter "uppercase mode" :)
Re:Amp – A complete text editor for the terminal by cbkeller on Thursday November 22, 2018 @02:42AM (#18508510)
Sounds like navigation might be different, but the linked page is a bit cryptic:

> Fast, precise cursor movement without repetitive keystrokes or fancy expressions. Look where you'd like to move, and type the token. That's it.

Digging a bit more, I found this [1] (in addition to the normal h,j,k,l, etc.):

> Jump Mode

> Press f to switch to jump mode. Elements on-screen will be prefixed with a two character jump token. Type the characters to jump to the associated element.

> For files with syntax support, you can jump to class, method, and function definitions using symbol mode. Hit Enter in normal mode to use the symbol finder, which works identically to open mode

[1] https://github.com/jmacdonald/amp/blob/master/documentation/...

Re:Amp – A complete text editor for the terminal by nerdponx on Thursday November 22, 2018 @03:18AM (#18508618)
This is similar to the vim-sneak plugin for Vim: https://github.com/justinmk/vim-sneak

It's very useful.

Re:Amp – A complete text editor for the terminal by tom_mellior on Thursday November 22, 2018 @08:00AM (#18509723)
Looks similar to the Emacs Ace Jump mode too: https://www.emacswiki.org/emacs/AceJump