Earlier quoted context omitted.
You're sharing accounts on servers or logging in directly as root? Either one sounds like a recipe for disaster.
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.
Amp – A complete text editor for the terminal
151–160 of 174 posts
Re: Amp – A complete text editor for the terminal
#152Earlier quoted context omitted.
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 o…
> 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
#153Earlier quoted context omitted.
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.
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
#154Earlier quoted context omitted.
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
Also see: Ruby on Rails
Re: Amp – A complete text editor for the terminal
#155Maybe choose another name? I mean: Good luck trying to out-SEO Google re-using their own term[1] :) [1] https://www.ampproject.org/
Re: Amp – A complete text editor for the terminal
#156Earlier quoted context omitted.
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 o…
> 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
#157Earlier quoted context omitted.
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.
> 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.”
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
#158Earlier quoted context omitted.
>> 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…
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 sta…
Re: Amp – A complete text editor for the terminal
#159Micro is nice too https://github.com/zyedidia/micro (been using it daily for a few months now).
I recently discovered this too. I'd been using nano as my default terminal text editor for years, but micro is a nice upgrade - I especially like the undo feature, the syntax highlighting, and the mouse support.
What do you mean? The persistent undo?
Re: Amp – A complete text editor for the terminal
#160Earlier quoted context omitted.
You are probably right. Which is my point. Vim movement commands remain unintuitive to me, even after using the thing for years.
It’s extremely intuitive to me. It’s more like muscle memory than logical thinking, I think you might be thinking too analytically.