4
yourdog
1y

Every fucking project is a steaming pile of legacy dogshit even before it's finished. For Christ's sake stop inventing those new motherfucking JS frameworks and my-framework-is-better-than-yours made up bullshit arguments. I'm sick of it!

Comments
  • 2
    but... what if my framework IS better than yours, solely by not being JS?
  • 1
    frameworks can only get you so far, until they become the bottleneck for further development. Past that point, you spend far more time dancing around the framework / raping it in unspeakable ways / supporting this Frankenstein than doing actually profitable development.

    I'm confident that some frameworks over time should dissolve in the application, starting with the day you dive into its source code trying to reverse-engineer some functionality so you could override it
  • 0
    What I hate the most:
    "This solution is not explicit enough. Let’s add a monstrously verbose layer above it so that it’s readable and we can understand what’s going on"
  • 0
    Nah! The framework you think is good n stable today would not be stable unless it was invented X years ago and tried out by curious devs

    just add a conservative framework policy within your company. Let everyone else keep cowboyin
Add Comment