News for hackers. Stuff that matters.
Re:From SVG to Canvas – A new way of building interactions by dirkc on Wednesday June 07, 2023 @03:55AM (#36224135)
I've also seen the other side where the argument is:

"we should be doing things correctly from the start"

2 years later:

"the maintenance of custom doesn't deliver business value and makes recruitment and on-boarding increasingly difficult. We should rewrite in $framework since it's well known, maintained and flexible enough to do whatever they need"

...

Re:From SVG to Canvas – A new way of building interactions by sanitycheck on Wednesday June 07, 2023 @04:27AM (#36224343)
There have been a few occasions where this has led to (literally) years of extra maintenance work for me, as I patiently wait for a team of devs to replace my custom app with v2 using $wellKnownFramework. Sometimes that v2 is eventually abandoned and I'm contracted to build v3.
Re:From SVG to Canvas – A new way of building interactions by marcus_holmes on Wednesday June 07, 2023 @05:07AM (#36224568)
Also seen this where the $wellKnownFramework is dumped before v2 is completed, and the whole thing is rewritten in $newHotFramework for no other reason than the dev team wanted to work in $newHotFramework.

There are lots of anti-patterns around this ;)