3 ms·
> Unless they spend most of their code fighting the framework to accomplish their actual task. Which happens rather often I think this is just confirmation bia
by sangnoir 10y ago
> Unless they spend most of their code fighting the framework to accomplish their actual task. Which happens rather often
I think this is just confirmation bias - you won't notice all the times you are not fighting the framework, but you do when you are.
> Not to mention that learning a new framework is not fundamentally different from learning some person's approach to doing things
Only if "some person" is real fastidious with documentation, StackOverflow answers and tutorials. You aonly have to learn Laravel[1], but catching up with Greg/Peter/Jane/Paula's framework at every new job will get old fast.
> Remember Struts, anyone? PHP Nuke? Would you rather maintain something that used either of those over something that was written in vanilla Java/PHP?
Those projects were fantastic for their time. Let me put it this way - I would rather maintain something that used those projects and not some custom solution written by a nameless developer in the same era. At least PHP Nuke had (I'm hoping) a clear migration path to PHP v4 and v5 and you won't have to do it manually.
1. Or any other framework
- deleted 10y ago[deleted]
- throwaway729 10y ago> Let me put it this way - I would rather maintain something that used those projects and not some custom solution written by a nameless developer in the same era I wrote a very large PHP application around that era. You are absolutely correct. Even I have a hard time maintaining that code.