Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

your last note that adds not-invented-here abominations… if chasing endless frameworks of the month is bad, and building stuff in house is bad, then what do you propose to avoid making this mess?


I would propose that if you want to change frameworks, actually complete the migration from one technology to the other.

My problem is having all of them existing at once.


Skip a couple framework versions and indeed entire frameworks. Maybe go a couple years before you "upgrade" to something else. It is entirely possible you could go as much as 5 or 10 years on something. You'll still have to evaluate and potentially mitigate some CVE's. But that could actually be less work and less aggravating.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: