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.
OOP dogma isn’t just bad, it’s actively harmful. OOP leads to unnecessary boilerplate. Any boilerplate that is not absolutely necessary is noise and bad. Full stop.
Private (Getters/setters): Strictly not a necessity in any sense of the word.
Short functions everywhere.
Short files everywhere.
I prefer to see the steps of execution that are actually happening in the real world on hardware. Not an ivory tower of code that happens to execute.
React is a plague.
useStateand all the otherusehooks.If you are getting paid for engineering software, your labour should be licenced in an appropriate jurisdiction, and you should be liable to losing said licence if you do shit job.
systemd does a lot of things very right and a mayor reason that linux is in a way better place than 15 years ago. 27 unmaintained tools are not better than one that is professionally developed.
Systemd solves a very important problem that was defined extremely well.
It also solves it badly, and solved a whole lot of other badly defined problems that it shouldn’t.
This is my argument. Do init. Don’t pull in literally everything else because you think you know better, like system logging.
systemd has me in two places. Like, on one side, it’s just SO much better and easier than the rest - at least to me, someone who doesn’t work in IT and just wants his stuff to work. On the other, init freedom is essential, and we need the alternatives to stay alive.
APIs generally don’t need many alternatives, only implementations do. There’s no reason devs should be trying to provide init files in multiple formats. If the systemd team actually did something bad, then people could just make a different implementation of systemd without requiring a different format for init files. Arguing for more init systems is like saying we need more APIs to compete with both Wayland and X11, instead of just talking about implementations of those protocols.
If there are spelling mistakes in your codebase, that’s a huge smell
A good programmer doesn’t need the internet.
if you’re making a user-facing program, you should always design with the possibility that it will be run on some truly dogshit hardware and you should make sure that they still have a good experience. good computer hardware is a luxury on the world scale, even before the rampocalypse
related, but the answer to the question “who still uses {x} these days?” is almost always way, wayyyy more people than you think
Me when I got my commercial NAS with 7 years of support, I was thinking: “who even keeps hardware for this long?”
Me, 7 years later: “What do you mean EOL?!”
I certainly learned to care for and appreciate the hardware these years.
There’s about 0.2% of people still using internet explorer, per one market share site I found.
Which works out to potentially millions of people.
I do my web development on a 2005 era windows XP machine without the unofficial SP4 because if it will run there (without silverlight) I know for damn sure it will run well on anything made today.
That’s so why a lot of artists I know of when mixing, like to test their songs on stock/sub-par monitors. Not everyone has reference quality equipment and you want to make sure your song works just as well thumping with the windows down as with your hi-fi system.
I agree. Designing based on “Who uses x anymore?” Just reinforces the ever-increasing cost of computing.
Functional is better than object orientated programming
There’s nothing in Functional Programming that stops you from writing in an Object Oriented idiom…
Could you define what you mean by functional and ooo in practice, because to many people in pracitce functionsl is a garbage monad wrapper over anything with unreadable, undebugable code whose only purpose is to hide if else statements… and it doesn’t even do that; while ooo is java factory of factoties mixed with aspect programming and 20 levels of inheritance.
Not Op but…
OO languages have classes with inheritance based polymorphism. I don’t see struts + methods as enough to qualify.
Functional languages have functions which can take functions as arguments and function composition as first class features.
100% agreed, though I’m in the “neither is ideal” camp. My favorite language, by a long way at this point is Rust.
It’s not functional, but borrows a lot of functional idioms while avoiding the pain points functional language usually hit in exchange for losing the purity of functional languages.
The billionaire tech bros are making money hand over fist without the need for advertisers subsidizing them, and interrupting users all over the world. Little secret…the users know products exist and will go out and seek those products when it is necessary to do so. This activity leads to learning about more products through the ancient art of “browsing”.
Advertising is education with misinformation
Java Is actually good for what it does, maintain long term systems that only need updating every once in a while
That putting more and more cutting edge technology in our daily computing, that can only be manufactured by a few multi-trillion-dollar-fabs, is a good thing. Not in a politically unstable world like we currently have. And this will not get better the next 50 years, with climate change. Our computing is good enough, we should focus on making it more accessible.
Unlimited growth baybayyyyyyy! If you stand still, you lose! Other gross capitalist talking points!
PHP sucks and every attempt at defending it is pathetic.
I get warm and fuzzy feelings that people here are not even talking about it. Perhaps I should follow that trend.
PHP is the best web language, not because it’s a good language, but because the other are worst
I am with you all the way. For a high level programming language it’s incredible how close to C it is at times AND how many footguns the entire language has.
And you always hear the “a poor craftsman blames his tools” analogy when someone says PHP bad. But PHP is a hammer that’ll blow your arm clean off when you hit a nail at a slightly off angle.
There is no defending it, and it should have been replaced with better languages several times over.Ok I need to stop myself now I can rant about this language for hours
A hammer with a claw on both sides - respect the double claw lmao
Sometimes we have to use them, but Java and C# sucks hard as languages.
I actually really like C#, it’s my favourite. But don’t know how much of that is Stockholm syndrome at this point haha. But whenever I’m writing in other languages i always end up missing something i do regularly in c#, especially from it’s latest versions (which i also deeply miss when forced to work on legacy software that is still using shit like version 4 or 5 of C# (ASP.NET 4.8 / .NET standard) whereas I feel like C# really got good and fun to use from C# 8 onwards (I think this was .NET Core 3.0 or .NET 5 - we’re on C#14 now with .NET 10, with 15 on the horizon).
What do you miss?
Not the oc, but honestly just random shit, like:
Linq.
Async and await are both in python or rust, but still via anexternal provider afaik (like Tokio).
Explicit interface implementation (default trait implementation for the Rust fans)?
Nice source generators and what you can fo with them (kinda like aspect programming).
Idk if python or js support pattern matching or proper low level or no GC coding.
I also enjoy my langauges to have an end of statement character like
;instead of the horrible visual mess python is.Type safety of compile and runtime type checks lol. In C# if you say your module requires int parameter, noone will be able to call it passing None/null/string/date.
Linq
AKA - We have Monads at home…
Rust is really missing something like do syntax. It’s half-way there with the semicolon and question marks, but it’s missing an idiom for .map_or_else and to generalize the thing to work with a trait.
useStateworse thanuseEffect? I’m not much of a React expert, but I understand useState. useEffect mostly seems to be an excuse for the most horrific spaghetti code since before the abolition of goto.
