|
|
|
|
|
by aikah
4109 days ago
|
|
> a deep understanding of the framework itself will become necessary and it will stop saving you time This is true for any 3rd party code you're going to use.If you don't know the difference between jQuery the DOM and how to go from one to the other within jQuery you're going to do a lot of mistakes as DOM apis evolve fast while jQuery features don't. > I tend to avoid frameworks that attempt to push developers into coding "the framework's way" What makes you think your way is better? and when you end up working with several devs , are going to meet every morning to talk about what's the good way to do things for every aspect of the project ? using a third party frameworks helps , people only have to agree on what 3rd party code they are going to use. And libraries are not black boxes. Reading 10 000 lines of code shouldn't considered a burden or one should reconsider career choices. |
|