I relate to this so much! Devs love to hate on Rails so much. I just can't imagine a better tool to make something with ease in a small amount of time

This is true and I'm part of the problem. I've been thinking about all the suboptimal systems I've learning over the years and how it could be good to move to something more clear or consistent.

• Vim - spacemacs.org/
• bash - fishshell.com/
• git - github.com/frostming/legit/blob/ma...

I'm not known to conform to how things are done or avoid new things. But like so many before me I have learned these old systems and we can't move past because we have so much knowledge and documentation in the old.

If someone chooses a different system, I'm not there to help, I will fall back to the system I know. I also can't make a good recommendation on what to move to.

However I am also not left behind. Docker is heavily reliant on the concepts of the past. It didn't take much for me to handle because I know bash and the supporting concepts of git.

Yup, support is really very important that it almost trumps everything else.

Inelegant software is usually elegant software adopted for real world use

I'm not hating though, I really understand where it fits. Still I did like lifting state up.

Actually there's a gap year where I didn't code either aand Redux was super popular back then that it was required for react jobs, well, still now but much less. And I didn't use other state management libraries either.

React ships with context and reducer support built in, so I guess you could say that. There's also MobX which is quite common, but most projects can stick with the state management options built into React.

What is your IDE of choice?

That seems like a very popular opinion except among those that have learned vim.

Now I'll switch to links to respond to your comments.

still quicker than learning all the keybindings

Mastering Vim grammar

Igor Irianto ・ Mar 6 ・ 6 min read

#vim #neovim #editor #grammar

IDE which catches 80% of my mistakes for me and offers all sorts of other features to boot.

visualstudiomagazine.com/articles/...

onivim.io/

I have not found learning vim a waste and still get IDE benefits.

[deleted]

I was made to learn vim and all I needed to know was: I for insert, e for end, x for delete and :wq for "write quit"

It's useful but I wouldn't trouble myself to remember more

I have probs spent well less than 1 day in total working in vim, in my dev career.

Honestly it only really takes a day or two to learn most of what you need to know to be productive in Vim. One of the great things about Vim is that it doesn't actually have that many important keybindings but the ones it has can be composited in many ways.

Not that I'm trying to convert anyone but I think the 'learning cliff' meme is inaccurate and scares people off that might otherwise benefit from learning Vim.

Of course I use it partly because it was easier for me to know VIm and be able to edit stuff up on a glorified mainframe when I was in school than to constantly be pushing code up and down.

Vim is one of those skills that's nice to have, but not necessary to be productive. The high upfront learning curve is not as high as you might think, and it does provide some tools to eliminate a lot of redundancy and inefficiency with typing, but it's usually not a force multiplier.

IMO, it really comes down to one question: do you find significant value in decreasing the time it takes to transform your thoughts into text on the screen? If so, then you should learn/use Vim. If not, then it may not be worth it for you.

I should add that I use the Vim key bindings for VS Code. So really I get the best of both worlds. I highly recommend that approach.

Vim at its core is a language for describing editing actions. The language goes all the way back to the first editor of UNIX, ed. The history of the tools and the language goes like: ed -> em -> ex -> vi -> vim. You can save repetitive editing actions as macros or scripts, and use them as you will.

A tailored IDE is usually the best for a particular language: .NET VB and C# work best in Visual Studio; Java and Kotlin in IntelliJ IDEA; Objective-C and Swift in Xcode. They are feature-rich, configurable, and user-friendly. People have invested in making them good tools for those languages. Similarly, many people have invested in making vim a good tool for C and shell script, which it grew up with, and other languages which do not have IDEs of their own. Vim provides a fall back semantic when the semantic analysis tool of the programming language is down or non-existent.

Frankly, I think it's silly for a language to force programmers to even think about indentation, because of how it affects its interpretation.

That's probably what I hated most about Python, back when I still used it.

Just let us use braces / brackets / do-end / some kind of clear indicator, and let an auto-formatter figure out the rest!

Thankfully, modern languages seem to come with a formatter built-in - refmt on ReasonML, for example.

It's also a much harder language to learn though. This matters in language adoption. If you read the story about why Go was designed like it is you will find details about Google trying to manage complexity and reduce bugs rate and improve complication time in massive C++ code bases with developers of all levels of skills

You might like Gitlab Flow

I think I can guess why you're saying this, but mind elaborating?

I repeat this regularly at work. We have a developer who (in PL/SQL) wrote a parameter as "parameter := null" instead of "parameter default null", and the reason was that "I'm not a typist".

I would say it's almost always better to repeat code.

I tend to agree. It's nice to have "class" syntax if classes are what you actually want... But a lot of old-school devs saw that and said, "Oh, I guess we can do real OOP in JS now..." And JS is just fundamentally not object-oriented in the way that C# or Java are. It's silly to force that paradigm on a language that does so much more...

That is a very popular opinion.