What is the most meaningless, silly, un-important programming-related opinion that you'll just continue to defend?
We're all familiar with Tabs vs. Spaces...
But what are some other pointless fights that you're always willing to fight about?
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (67)
Anyone who writes more efficient code than me is pretentious.
πππ
WordPress is an over-complicated and out-dated framework that shouldn't be used for anything more complex than a plain-text blog.
π± I'm not going to discuss but gonna tell you're not 100% correct. βπ½
What a wholesome community π€
I don't agree it's overcomplicated but it definitely should be used only for the blogs and small shops in my opinion. For everything bigger it quickly becomes a disaster.
BloodPress
That sounds so metal π€
CSS-in-JS is a mess, framework or not.
What makes
styled-componentsgarbage?Because anything you can do in
styled-componentsyou can also do in plain CSS stylesheets + JS, using proper class names. You can even pass props and conditionally apply different class names.Yes, the same goal can be achieved with plain CSS stylesheets + JS, but I don't see why that makes styled-components garbage. I suppose it comes down to preference for minor improvements with one option for styling over another.
It's trying to solve a problem that doesn't actually exist.
But seriously. use spaces.
indent with tabs align with spaces dmitryfrank.com/articles/indent_wi...
Tabs and spaces?
Have you learned nothing from American "politics" or Twitter?
Compromise is weakness AND WEAKNESS IS DEATH!
Just make your IDE to use space characters when you press tab. Done, everybody wins
I get the argument for spaces and all, but as someone who has vision problems 2-space indention makes my life way more difficult. I mean I'm not against adjusting my own workspace to accommodate the rest of them team since I'm the only person who has several vision impairments, but I'm honestly still not convinced the difference justifies the extra work.
The heading of this article is petty opinions, so there is no justification.
You may think Tabs vs. Spaces is a petty opinion, until you realize that using tabs makes a world of difference for visually impaired people.
Why we should default to Tabs instead of Spaces for an 'accessible first' environment
Alexander Sandberg γ» Jul 12 '19 γ» 3 min read
Never thought of this. I have a little bit of trouble with my eyesight and use very large font sizes (22+). Interested to try this π
Any language is more suitable to a task than Javascript.
(It's only partially objective. I have technical reasons for my hatred of Javascript, but I try to accept that it has uses. I'd just sooner change careers than use Javascript in any measurable amount.)
I am of the personal opinion that JS is hot garbage.
I think that's the consensus.
I mean Javascript is the only language that's so bad that both Google and Microsoft had to create other languages that transpile to it (with Dart and Typescript) to avoid writing javascript.
OTOH, JavaScript may be the closest to Lisp an Algol descendant gets.
But developers who use spaces make more money.
stackoverflow.blog/2017/06/15/deve...
The creator of Python said if he had to go back in time he would have made 2 space mandatory to stop this space vs tabs wars.
Guido van Rossum prefers tabs [1].
I think putting any kind of semantics in things you cannot print is a big mistake. This includes newlines like used in JavaScript.
lol
We do not need so many programming languages. We do not need so many frameworks.
How many times are we going to "re-implement" the same function to read a file in memory or to send a HTTP message over the wire or to display a button with text that does something on click? π
Maybe no individual needs all these options, but not everyone will agree on which style of language/framework is the best. It's a matter of taste, so I think it's great that we have many to choose from.
I agree there's value in having so much R&D going on from multiple communities, but the question is "What is your pettiest programming related opinion" so I thought this qualified.
I believe WASI has the potential to change things down the line. We can all keep the languages we want, but at least we can stop writing basic functionality like "write a synchronous HTTP/2 server". So many replicated man hours in that.
Also, imagine how better in quality and in regards to security vulnerabilities if most languages were built on the same building blocks.
There's also the counter argument of centralizing vulnerabilities but hey, I didn't think this through :D
swtichstatements have no real use case that could not be implemented using other simpler features of the language.I will die on this hill with you. Back to back, mini gun aiming down the hill, mowing down anything that comes our way except food delivery.
have you ever had a legit use case for
switch?I mean I think in finite lists they can have some application. Think like cardinal directions(Noth, East, South, West), basically TRUE Enums, absolutely finite ones. They can be useful sometimes in those cases. You could in theory use a strategy pattern or something even then, and be a more robust solution but it could be seen as over-engineering. If you MUST use one or have a case like above, I always like to throw an exception in the default case. If it shouldn't occur and does, I for sure want to know about it, and I don't want something weak like it being logged. I want it to be a mini-crisis.
Following that logic, there is no use case for a for loop.
But really, can you give me a legit use case?
I cannot think of one single thing that is not a bad pattern
switch(true)or could not be solved with an if and early return.Switch cases are syntactic sugar for writing repetitive
ifandelse ifstatements, not a language feature. Just like the for loop, you could write a while loop that does exactly the same thing.Unit testing is overrated and should focus more on integration and E2E tests :D
Naming coventions,
Readability of switch -case,
Curly style, egyptian or line separated,
Number of arguments in function signature
My biggest pet peeve is when people say that X was superior to Y, be it vim vs. emacs, interpreted vs. compiled language, strong vs. weak typing, etc.
There's a problem for every solution, just don't try to make it fit by brute force.
"Bitcoin" is an uncountable noun. So is "bitcoin." So is "code," in the context of computer programming. No more of this "I wrote you some codes." No, no, no.
And I will die on that hill.
P.S. Slack Threads respect each others' time, these programming languages should be called programming notations, not programming languages, and hey this, over here, is a configuration language, not a programming language, Dvorak is better, they're capitalized as ReDiS and CEntOS, metaphors about the name of the Python programming language should involve more flying circuses than snakes, plural of status is status (from the Latin genitive neutral declension), DevOps is not a job title and DevSecOps is not a thing, and for some reason I can't stand multi-line comment syntax even when someone has made an effort to use it right. On a slightly more practical note come on man for the love of whatever God you hold dear use footnotes instead of endnotes in your publications. Some of us neither should nor can be arsed.
Wow, I'm a petty person.
Mac os and widows stink for programming they are way to locked down and aren't widely used in production environments. In my opinion linux of bsd should be used for everything except apple apps (all of them), windows apps, and situation where Visual Studio is required.