2 ms·
The blame may not entirely be on the framework, but it is certainly on their documentation. If something goes wrong, a developer should know which resources to
by adyus 13y ago
The blame may not entirely be on the framework, but it is certainly on their documentation.
If something goes wrong, a developer should know which resources to use to solve the problem. Abstracting away the lower level stuff should not be synonymous to keeping it completely hidden and inaccessible.
A good example is the AngularJS source code, which is commented enough for anyone to make sense of it after a read-through.