My serial killer trait is that I use vi instead of vim cause I’m too lazy to type the extra character. Tho if for some reason, vi tab completed to vim, I’d probably use vim
I’d need to run vi at least 5 times to have a net gain in saving keystrokes. I’m typically in effemerial systems created by the users of our env, so rarely am I going to gain those strokes back
But also, why am I trying to apply logic to this? I’ll often cat a file before editing it. This shit is just illogical idiosyncrasies I’ve picked up over the years. I’m probably creating posthoc justifications for insane things I do cause it’s hard to override muscle memory
There are different levels of effemeriality. The simplest example I use daily would be an autoscaling group in AWS. Especially if you use Spot Instances to save money, thi gs may scale in and out whenever.
So if a development team creates a new autoscaling group and I need to get into an instance to test something, unless I add stuff to their IaC, I’m stuck with their configuration. I need to assume that every time I ssh into one of those instances, it’s a brand new instance. But it’d be a big challenge for me to go to their repo and make a PR to alias a command whenever an instance in that resource is created
Stuff can be even more temporary if it’s something like an ECS task which creates a container with a read only filesystem only when a task is needed to be done. But I don’t want to get too deep in the weeds (or deeper than I already have)
terraform workspace will at least stick around for a while so you might be in and out of the same system multiple times.
I’m in DevOps so I’m in a lot of effemerial systems so in practice, I will run into systems where profile hasn’t been set up. Tho I do like the idea of making sure all systems properly have that aliased cause it’d be serial killer vibes to spend hours of time to make sure that I can save a keystroke.
Tho it’d never make it through PR. Also, wild require explaining to my coworkers that I do this
I’ll have to check tomarrow if RHEL and UBI do this.
Did some quick googling and looks like cent has that alias by default but doesn’t do it when root. Which would explain why I do get inconsistent results with vi. I never thought about it in detail besides just knowing that there are some visual changes. Thanks for the info, I’ll be noticing this now that I know!
My serial killer trait is that I use vi instead of vim cause I’m too lazy to type the extra character. Tho if for some reason, vi tab completed to vim, I’d probably use vim
alias v=vim. There, just saved you two keystrokes.
{
vi} = 2 {vim} = 3 {v=vim} = 5I’d need to run vi at least 5 times to have a net gain in saving keystrokes. I’m typically in effemerial systems created by the users of our env, so rarely am I going to gain those strokes back
But also, why am I trying to apply logic to this? I’ll often cat a file before editing it. This shit is just illogical idiosyncrasies I’ve picked up over the years. I’m probably creating posthoc justifications for insane things I do cause it’s hard to override muscle memory
effemerial is new to me
Here’s a link I found that might be good if you are interested in more:
https://cloudnativenow.com/topics/ephemeral-idempotent-and-immutable-infrastructure/
https://guymorton.medium.com/persistent-and-ephemeral-infrastructure-as-code-in-aws-42b33939dcf1
There are different levels of effemeriality. The simplest example I use daily would be an autoscaling group in AWS. Especially if you use Spot Instances to save money, thi gs may scale in and out whenever.
So if a development team creates a new autoscaling group and I need to get into an instance to test something, unless I add stuff to their IaC, I’m stuck with their configuration. I need to assume that every time I ssh into one of those instances, it’s a brand new instance. But it’d be a big challenge for me to go to their repo and make a PR to alias a command whenever an instance in that resource is created
Stuff can be even more temporary if it’s something like an ECS task which creates a container with a read only filesystem only when a task is needed to be done. But I don’t want to get too deep in the weeds (or deeper than I already have)
terraform workspace will at least stick around for a while so you might be in and out of the same system multiple times.
He’s commenting on your misspelling. https://www.merriam-webster.com/dictionary/ephemeral
Shit… I’m an idiot
Nah it’s fine
I use nano.
Nano >> vi/vim, emacs
4 letters < 2 letters.
vi forever.
Simplicity > Complexity
Not if you need any work done.
That’s when you switch to a IDE.
Neovim and emacs are IDEs.
Yes, if you can remember the shortcuts…
M-x IDENano is the best when you just need an editor, you can as well use an IDE instead of vi(m) or Emacs.
Ok but why use nano when micro literally exists
Alias?
Aliases are just bloat! You can do just fine without them. Heck, why not remove the ASCII conversion and read everything in hex or binary?
It’s all about SPEED and efficiency here!
I’m in DevOps so I’m in a lot of effemerial systems so in practice, I will run into systems where profile hasn’t been set up. Tho I do like the idea of making sure all systems properly have that aliased cause it’d be serial killer vibes to spend hours of time to make sure that I can save a keystroke.
Tho it’d never make it through PR. Also, wild require explaining to my coworkers that I do this
Most all distros alias
vitovimalready, so it makes no difference.You use vi because you are lazy.
I used vi because I am too stupid to close it.
We are not the same.
I’ll have to check tomarrow if RHEL and UBI do this.
Did some quick googling and looks like cent has that alias by default but doesn’t do it when root. Which would explain why I do get inconsistent results with vi. I never thought about it in detail besides just knowing that there are some visual changes. Thanks for the info, I’ll be noticing this now that I know!