loading...

Unpopular opinions

belhassen07 profile image Belhassen Chelbi ・1 min read

I have never used Redux, even after using React for 2+ years.

What's your unpopular opinion or something you?

Discussion

pic
Editor guide
Collapse
harri_etty profile image
Harriet

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.

Collapse
jessekphillips profile image
Jesse Phillips

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

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.

Collapse
jmfayard profile image
Jean-Michel Fayard 🇫🇷🇩🇪🇬🇧🇪🇸🇨🇴

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 :)

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

Right it's not a waste of time, it's fun

Thread Thread
ludamillion profile image
Luke Inglis

And I'm sorry but it would be delusional to think that vim gives IDE benefits similar to JetBrains IntelliJ IDEA :)

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.

Thread Thread
jmfayard profile image
Jean-Michel Fayard 🇫🇷🇩🇪🇬🇧🇪🇸🇨🇴

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

Thread Thread
jessekphillips profile image
Jesse Phillips

I think you missed that I wasn't specifically talking about vim, but emulators and new IDE which provide vim's mode based editing.

Thread Thread
ludamillion profile image
Luke Inglis

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.

Thread Thread
jmfayard profile image
Jean-Michel Fayard 🇫🇷🇩🇪🇬🇧🇪🇸🇨🇴

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

(from Jesse) I think you missed that I wasn't specifically talking about vim, but emulators and new IDE which provide vim's mode based editing.

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

I don’t tend to work in languages with tons of tooling though so maybe that accounts for it.

Ah maybe that's why. Try out doing refactoring with Kotlin in JetBrains IDEA Community Edition

Thread Thread
ludamillion profile image
Luke Inglis

When I did C++ and Java in school I definitely appreciated having more tooling around things.

Collapse
demianbrecht profile image
Collapse
louy2 profile image
Yufan Lou

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.

Collapse
ludamillion profile image
Luke Inglis

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.

Collapse
austindd profile image
Austin

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.

Collapse
Sloan, the sloth mascot
Comment deleted
Collapse
ludamillion profile image
Luke Inglis

VIM users seem to install a ton of plugins to make it similar to a regular editor, which always seems like extra steps for a similar experience.

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.

Collapse
ben profile image
Ben Halpern

What is your IDE of choice?

Collapse
harri_etty profile image
Harriet

Only used JetBrains products, so - JetBrains.

Collapse
jenc profile image
jen chan

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

Collapse
ben profile image
Ben Halpern

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.

Collapse
faraazahmad profile image
Syed Faraaz Ahmad

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

Collapse
deciduously profile image
Ben Lovy

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.

Thread Thread
belhassen07 profile image
Belhassen Chelbi Author

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

Collapse
thesigitprayoga profile image
Sigit Prayoga

For me, it is PHP who I love to hate. But again, many developers and organizations have achieved more using PHP.

Collapse
jessekphillips profile image
Jesse Phillips

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.

Collapse
developarvin profile image
Arthur Vincent Simon

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

Collapse
cullophid profile image
Andreas Møller

Inelegant software is usually elegant software adopted for real world use

Collapse
mattwaler profile image
Matt Waler

cough Svelte vs. React right now cough

Collapse
craignicol profile image
craignicol

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.

Collapse
andyrosenberg profile image
AndyRosenberg

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.

Collapse
tomekbuszewski profile image
Tomek Buszewski

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".

Collapse
scottishross profile image
Ross Henderson

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".

Collapse
mattwaler profile image
Matt Waler

WORD.

Collapse
cullophid profile image
Andreas Møller

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

Collapse
lampewebdev profile image
Michael "lampe" Lazarski
  • 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.

Collapse
chrispardy profile image
chris-pardy

My unpopular opinion: Hateing Redux is so often listed as an unpopular opinion amongst React Developers that its become popular.

Collapse
mattwaler profile image
Matt Waler

I use to hate Redux until I started using Easy Peasy!

Collapse
belhassen07 profile image
Belhassen Chelbi Author

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

Collapse
developarvin profile image
Arthur Vincent Simon

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,

Collapse
jdforsythe profile image
Jeremy Forsythe

You might like Gitlab Flow

Collapse
developarvin profile image
Arthur Vincent Simon

Yes, I think this is approximately what I was thinking of.

Collapse
bjorngrunde profile image
Björn Grunde

Javascript is overrated and has an overly complex eco-system. It belongs in the browser.

Collapse
tails128 profile image
Tails128

(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.

Collapse
ogaston profile image
Omar Gaston Chalas

Classes are the worst thing has ever happened to Javascript

Collapse
austindd profile image
Austin

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...

Collapse
cullophid profile image
Andreas Møller

That is a very popular opinion.

Collapse
patarapolw profile image
Pacharapol Withayasakpunt

I dislike Golang.

  • go mod vendor doesn't work properly.
  • Godoc doesn't support Markdown, but VSCode renders comments in Markdown, not plain text, anyway.

I can never understand why Golang become popular, when Rust is so much better for developer experience...

Collapse
rhymes profile image
rhymes

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

Collapse
scrabill profile image
Shannon Crabill

The tabs/spaces debate is stupid.

(Althought I think in Phyton, whitespace matters so yeah, do tabs)

Collapse
harigopal profile image
Hari Gopal

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.

Collapse
rhymes profile image
rhymes

Keep in mind that Python hails from 1991 (actually 1989 but the first public version is 1991). I think it stood well the test of times :D

Though I can see why someone wouldn't like indentation to be syntax, but it's not that different from having gofmt indent all files the same way. It's also one less tool you have to worry about :)

Collapse
petedermott profile image
Pete Dermott

Mmmm... I just use Black with Python and it standardises everything.

Personally I find some simple indentation rules preferable to the million different ways to position brackets and braces.

Collapse
juankortiz profile image
juankOrtiz

Still refusing to replace PHP with Node.js (I'm using Laravel, but still...)

Collapse
bendman profile image
Ben Duncan

Most testing of UI components is a waste of time, especially snapshot testing.

Frontend developers should run their code in a browser to see what they built. Any teams I've been on that used automated tests for UI components inevitably have developers who get overconfident in the tests and don't even check their code in a browser, breaking things.

For a test to be valuable it should either be written before the target code, written before fixing a bug, or written for either a project or team so large that people might break things in different parts of the codebase. I haven't seen many exceptions.

Collapse
mike_hasarms profile image
Mike Healy

Didn't alternatives to Redux start to become common about 2 years ago anyway?

Collapse
bendman profile image
Ben Duncan

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.

Collapse
belhassen07 profile image
Belhassen Chelbi Author

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.

Collapse
austindd profile image
Austin

I'm going to throw in a suggestion for ReasonML on this one. TS and Flow are great for many reasons, but ReasonML is just 100% better in every way. Compiles to JS and native, and has solid web frameworks in the ecosystem. Can't really go wrong.

Collapse
rhymes profile image
rhymes

JavaScript tooling is too complicated but I'm not even sure it's an "unpopular opinion" anymore, even tools developers are aware of that and are working every day to make it simpler (or to hide complexity away with easier abstractions)

Collapse
avalander profile image
Avalander

Javascript has become worse in the past couple of iterations.

Collapse
thecodingalpaca profile image
Carlos Trapet

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

Collapse
harigopal profile image
Hari Gopal

Working with GraphQL, using a strongly typed language (ReasonML) was something of a revelatory (positive) experience for me.

Mind expanding on why you think "you probably don't need GraphQL"?

Collapse
mattwaler profile image
Matt Waler

I think he means that in most cases, except for massive apps/webapps like Facebook and Airbnb, you most likely don't need all the flexibility and overhead of GraphQL over simple REST endpoints for your data.

austindd profile image
Austin

Absolutely! This has been true for me as a TypeScript developer.

Collapse
mattwaler profile image
Matt Waler

In most cases, it feels like GraphQL and Typescript a ton of overhead and technical debt that raise the skill floor for contributors.

Collapse
bendman profile image
Ben Duncan

Is that assuming the strong-typed language compiles to Javascript? What about the cases where the target is a browser?

Collapse
cullophid profile image
Andreas Møller

Code coverage is a terrible metric, and unit tests are usually a waste of time

Collapse
cullophid profile image
Andreas Møller

"Good" code is not elegant or clean, and it's never DRY.

Collapse
cullophid profile image
Andreas Møller

100%, unfortunately that language isn't ready yet.

Collapse
harri_etty profile image
Harriet

Hahahaha agreed!

Collapse
miguelthedev profile image
Miguel Sanchez

It's NOT okay to be soft.

I'm actually publishing a post about it tomorrow. Stay tuned.

Collapse
aleksandrhovhannisyan profile image
Aleksandr Hovhannisyan

GraphQL sucks.

GraphQL sucks 99% more with TypeScript.

You know what sucks more than that?

Migrating code written in Redux + TypeScript to GraphQL.