Try and use your imagination.
Imagine a developer who has lived in the world of frameworks, and lived in the world of building systems from libraries.
Now imagine they weigh up the pros and cons of both and have decided that they prefer not to use frameworks.
Those are NOT devs in the first place!
A developer SHOULD understand the implication at the "vanilla", library and framework level in the first place.
If you took most JAVA, C, C#, PHP,...developers today and told them to code in machine language, they would be like sheep watching tv.
There is a reason we have higher programming languages. Likewise, there are reasons we have libraries. See where am going with this?
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Try and use your imagination.
Imagine a developer who has lived in the world of frameworks, and lived in the world of building systems from libraries.
Now imagine they weigh up the pros and cons of both and have decided that they prefer not to use frameworks.
Those are NOT devs in the first place!
A developer SHOULD understand the implication at the "vanilla", library and framework level in the first place.
If you took most JAVA, C, C#, PHP,...developers today and told them to code in machine language, they would be like sheep watching tv.
There is a reason we have higher programming languages. Likewise, there are reasons we have libraries. See where am going with this?