|
|
|
|
|
by danpalmer
2909 days ago
|
|
Not wanting to open a can of worms, and I haven't read any of the React source, but if the source isn't that useful I'd suggest the answer might be to make the code easier to understand. Developers often need to dive into the code they are using for more detailed analysis of undocumented edge cases, tracking down bugs in their own code, etc, and having an understandable framework or library is fairly critical for that. Django does a lot of complex/clever stuff under the hood, but the source is still readable, and in most cases fairly easy to understand. This is just my 2 cents though. |
|
I believe Django's "functionality/(API surface)" quotient is still much lower than React's, which means it's easier to make the source useful to a newcomer.