I have never used Redux, even after using React for 2+ years.
What's your unpopular opinion or something you?
For further actions, you may consider blocking this person and/or reporting abuse
I have never used Redux, even after using React for 2+ years.
What's your unpopular opinion or something you?
For further actions, you may consider blocking this person and/or reporting abuse
Abto Software -
Alex Roor -
Jayamurugavel G -
sharathchandark -
Top comments (65)
It's a waste of time to learn vim.
here's my reasoning.
Yes it's a bit annoying if you have to edit something on the fly on a server without a GUI - but fumbling around in vim for this small amount of time is still quicker than learning all the keybindings. and why are you vimming around on the server anyway? isn't that a red flag in the first place?
I have probs spent well less than 1 day in total working in vim, in my dev career.
whereas I spend 8 hours a day in an IDE which catches 80% of my mistakes for me and offers all sorts of other features to boot.
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.
Mastering Vim grammar
Igor Irianto ・ Mar 6 ・ 6 min read
visualstudiomagazine.com/articles/...
onivim.io/
I have not found learning vim a waste and still get IDE benefits.
I have learned vim enough to write part of the translated manual in french.
And I'm sorry but it would be delusional to think that vim gives IDE benefits similar to JetBrains IntelliJ IDEA :)
Right it's not a waste of time, it's fun
With the right plugins you can get most of the way there. I'll take 95% of the way there for free than 100% of the way for $150/year.
vim+plugins doesn't do 95% of a modern ide
and $150/year is like one or two hour of work for your employer, I'm pretty sure that he shouldn't care
I think you missed that I wasn't specifically talking about vim, but emulators and new IDE which provide vim's mode based editing.
Obviously I don’t have hard numbers but I’m curious what you are sure that Vim can’t do that a full fledged IDE can’t.
I’m honestly wondering because I haven’t run into much at all that I can’t cover in Vim. I don’t tend to work in languages with tons of tooling though so maybe that accounts for it.
And not everyone is luck enough to have an employee who will shell out for arbitrary licenses.
True, and that's why there is a space for both
onivim.io/ is not released yet so why would I compare with mature IDEs?
Using a modern IDE with vim's mode based editing is fine if that's something you like
Ah maybe that's why. Try out doing refactoring with Kotlin in JetBrains IDEA Community Edition
Are you feeling overwhelmed? Refactor your assumptions
Jean-Michel Fayard 🇫🇷🇩🇪🇬🇧🇪🇸🇨🇴 ・ Jan 7 ・ 5 min read
When I did C++ and Java in school I definitely appreciated having more tooling around things.
Shameless plug: dev.to/demianbrecht/you-will-pry-v...
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.
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.
I only need to install 2/3 plugins to get a similar experience to my VSCode setup. If you remove themes from both I actually have almost the exact same number of plugins/extensions installed in both VSCode and Vim. The number of plugins you actually 'need' to add to get common behaviors between the two is small.
VSCode is great and there is still stuff I can do there that doesn't have a parallel in Vim but for 90+% of my daily work I can get the same things done faster in Vim than I can in VSCode.
What is your IDE of choice?
Only used JetBrains products, so - JetBrains.
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
Inelegant software which has a huge following and a big ecosystem is often better than objectively cleaner, better software.
The reverse is also true if the pendulum swings too far in the other direction.
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
I'm just starting to use rails and I'm a little bit mad at myself for not doing so earlier. At least at the very outset it's hard to understand why I'd use anything else, everything just works.
I'm mad that I didn't learn it earlier too. But actually, even now I didn't, commited to django, which is kinda of a similar mindset behind the two of them. Love DHH too haha
For me, it is PHP who I love to hate. But again, many developers and organizations have achieved more using PHP.
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.
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
More JavaScript Frameworks, more text editors, more language options are a good thing.
Yes, 99% of code will still be written in the most popular 5, but the next thing to break the top 5 will remix a bunch of great ideas from whatever that 1% is written in.
Microframeworks and/or libraries that cover the bare minimum of wrapping request-handling are better than massively abstracted, monolithic frameworks. You can build the same structure without the extra bloat.
It's better to write dirty, understandable code than highly abstract and incomprehensible one.
Also, sometimes it's better to repeat some code rather than refactoring a days work just for the sake of "cleanness".
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.
That we teach to much technical/frameworks/lib stuff and don't teach enough how to think about code and how to abstract things in a general way.
People hating on language X. Nobody is forcing you to use Language X.
Google, Facebook, Netflix, and all the big tech companies are highly overrated as an employer.
My unpopular opinion: Hateing Redux is so often listed as an unpopular opinion amongst React Developers that its become popular.
I'm not hating though, I really understand where it fits. Still I did like lifting state up.
In Gitflow, I think the develop branch is a waste of time.
It's better to have discrete release branches and a single master branch.
This way you can just deploy what branch you need to the dev/staging environment rather than having to merge to develop,
You might like Gitlab Flow
Yes, I think this is approximately what I was thinking of.
Javascript is overrated and has an overly complex eco-system. It belongs in the browser.
(actually planning to write an article on this, if I ever overcome my self-hate/shyness/etc)
Meetings are not something you should avoid or which you should hate, stupid meetings are.
A kick-off meeting is useful, a planning meeting is useful, a retrospective meeting is useful... they are literally there to explain to you how to do stuff, to help the company strategize and/or to help your company make a comfortable environment for you.
Other meetings are to be avoided/hated (and I am looking at you 3-hours long meeting on "definitions")
But the only image you give as a hater for all the meetings independently on what they are about is a very not-professional one.