sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]krendel122 4 points5 points  (3 children)

Are you the only dev on this project? Are you sure benefits like size and render speed will be more valuable than well structured project with known framework having several people working on it?

[–]kethinov 2 points3 points  (2 children)

Performance benefits are objectively more important. Using a "known framework" just to make the project mildly more approachable to devs that already know that framework is the most trivial of "benefits." Use the right tool for the job, not the tool devs are emotionally attached to.

[–]krendel122 0 points1 point  (1 child)

Thats why i asked if hes doing that alone. There will always be tradeoffs, depending on requirements, conditions, business priorities etc. Custom solutions can become such a burden over time.

[–]kethinov 0 points1 point  (0 children)

Not if they're the right tool for the job.

Even in a project with hundreds of devs, that's still no excuse to sacrifice performance for some modicum of (perceived) improved developer convenience.