Because it doesn’t seem like a useful feature. The only occasion I imagine this could be helpful is with logging to the console to track when the function breaks, but even then - still trivial to replace.

I had tried to use debugger with React so many times and each time I’d drop it soon after. Not useful at all.

Does much better job on the backend though

Good, OOP can suck my balls

To me, there are two classifications of DRY - one I find harmful, the other very useful.

First one resembles mathematical extractions, essentially you never allow a single chunk of code to be written twice and you create massive amounts of global util junk. This also creates some bad tight coupling.

The other is more logical, where you only extract logic in places you want to always change together. Simple and effective.

https://lemmy.world/comment/13098712

dis 'bout you?

That’s your opinion my man

I’m not gonna continue using arguments if all you can respond with is cynicism, apparently I wasn’t wrong about the elitism part

That I do, yes, because that’s a small chunk of code that - when necessary - would have to be completely remade anyways, not just modified.

And then a few more any time you actually want to use it.

And then double it each time you have to decipher the existing one

Just don’t use regex unless there is really no other way, and when you absolutely have to - frankly, that’s one of the ultra rare occasions I recommend using the AI.

Ah yes, spoken like a true elitist asshole

This sounds just extremely dumb to me, as in “do something manually for 2 minutes or spend 2 days automating it”

Also, DRY in 90% of the cases is a sham

I don’t get it, what’s so bad about boilerplate?