Mine is that the useState hook is an actual plague on the entire React ecosystem. Regardless of your opinions of React, if you wanna use something then use it right.
The entire modern web tech stack should be thrown in a dumpster, ignited with gasoline, and blown up with a nuke for good measure.
-
C++ is an awful language overall.
-
Linus is just some guy with good programming skills and not an authority over anything tech.
-
There aren’t any good text editors in the wild. VSCode is awful apart from extension support. Kate is close to being perfect but lack of extensions are pulling it back. Vim, Helix, Emacs, NeoVim are all flex toys.nvm just tried zed with AI disabled -
AI bad
-
Getters and setters are ridiculous
A good programmer doesn’t need the internet.
Cool, but I need to get the documentation from somewhere. I’m not about to code absolutely everything from scratch like I’m writing TempleOS in HolyC.
I remember having a professor passing around a bootleg CD of, iirc, Java documentation because he knew not everyone had access at home. He was great!
That’s amazing! These days you can download most languages documentation to Kiwix. I have Zig, C++, C, HTML, Python, and probably a few others along with whatever is in 2024 Wikipedia. It’s really more documentation than you could possibly need to make most things.
Linters are terrible.
Style/formatting linters, anyway, particularly when it comes to whitespace. The goal of formatting code with whitespace is to optimize for human readability. A linter based on a set of rules is not human and thus cannot judge human readability. There is really no formatting rule you can write that will not someday have exceptions on a large-enough codebase.
Contributors should be responsible for submitting readable code, and ensuring that is what reviews are for.
I’ll go a step further: formatting for human-readability is the job of the reader, not the writer. Hardcoded line breaks, spacing, etc. are never going to be a good solution because the idea is wrong from the start. This is a display issue, not a logic issue. It needs to be solved at the display end.
Use a syntax-aware editor that formats code the way you like it. Save it any goddamn way that is syntactically valid. Anyone else who opens it will see it any way the like in their own syntax-aware editor.
“But my editor doesn’t do logical formatting!” Yes, because the entire world has been insane for several decades, and shitty editors are normalized. If the world had realized this 30 years ago, there wouldn’t be a code editor in existence today that didn’t do this properly. Demand better and better will be normalized.
Use a syntax-aware editor that formats code the way you like it. Save it any goddamn way that is syntactically valid. Anyone else who opens it will see it any way the like in their own syntax-aware editor.
So every MR restyles the code to fit your style? How are you going to review the code?
Every problem in computer science can be solved by adding another layer of indirection.
Whatever is displaying the MR formats it. The server saves a normalized copy.
Like crlf/lf. But for all formatting.
Like crlf/lf. But for all formatting.
Sure. Toooootally the same thing. Now the server will have to save a copy of your formatting preferences, checkout the project at point t-1, checkout the project at t, format it, create a diff, and present that to you. Now when you leave a comment on line x, it might be line y for another person.
Or make it worse, someone introduces malicious code with UTF-8, or switches around parameters, or adds pragma comments that fundamentally change your code, but your formatter happily fixes that for you in the preview so you are oblivious.
Or you’re hosting this server and someone makes a change that completely reformats the entire codebase, but you see absolutely nothing of it because the preview diff only shows “relevant” changes.
All fine by you👌
Paragraph 1 is all client side viewer, moot
Pragmas aren’t formatting; strawman
Paragraph 3 is literally the problem being solved
Sure, put your head in the sand. Your solution is perfect and can never be abused, Sir. You’re always right, Sir.
SharePoint, Teams, OneDrive, Entra ID and M/O365 aren’t “stupid”. Your problems and complaints are the result of user error (although, to your credit, Microsoft in no way makes their intended use obvious or intuitive).
Don’t take that as an endorsement of them or Microsoft. On a consumer level, you should actively avoid them all. I’m referring to people who have to use them at work and complain about intended behavior being “stupid” or “pointless”. If you learn enough about how it works, you realize it either makes sense or is simply a limit of “the cloud”.
