4 ms·
I think he was pretty clear that the "magic" in frameworks is not something you can easily understand, therefore have to guess how it really works. He doesn't l
by szundi 2y ago
I think he was pretty clear that the "magic" in frameworks is not something you can easily understand, therefore have to guess how it really works. He doesn't like that.
- jemmyw 2y agoYou don't need to guess. You can actually read the code! Not saying that you should straight away when learning, but later, when you're familiar with your framework, I think reading through the codebase and understanding it is good practice.
- cj 2y agoYou can read the code, but it’s complex and convoluted. He referenced Backbone as a comparison point. If you compare Backbone’s source code to React’s source code, you’ll get what he means. Basically, libraries like Backbone are small and simple enough that you can literally read the source code and fully understand how it works. Compare that to React, where the source code is an order of magnitude larger and very difficult to fully grasp the inner workings. The simplicity and ability to easily understand the source code obviously comes with tradeoffs (e.g. with Backbone, to use it to build a reasonably complex app, you basically have to build your own framework on top of it, compared to React which has more abstractions and therefore is more plug and play.
- jemmyw 2y agoIt's complex but not that convoluted.
- spion 2y agoIIRC reading the React source code became quite a feat around the time fibers were introduced.