3 ms·
Of course it really is frameworks all the way down. Unless maybe you're building systems by laying out your own transitors. The trick is to understand the str
by aquark 12y ago
Of course it really is frameworks all the way down. Unless maybe you're building systems by laying out your own transitors.
The trick is to understand the strengths and weaknesses of any given framework and match those with the constraints of your project.
- Zelphyr 12y agoI disagree that its frameworks all the way down. There is a distinction between frameworks and libraries. React, Angular, et al are frameworks in the truest sense of the word. Things like jQuery and Underscore on down to stdio.h are libraries. You can pick and choose from what they contain but they're not so tightly coupled that they get in your way. They're a tool belt with tools that do one thing and do it really well. Frameworks are like having a tool belt with a hammer that also has a saw on the end but in order to use the saw you have to grab the screwdriver even if you're not actually using it.
- saraid216 12y agoI'm curious which part of React you consider the hammer and which part you consider the screwdriver.
- wickchuck 12y agoI would argue that React is closer to a library than a framework. It's a small library with some useful functions for making web components. It helps by removing a bunch of boilerplate code that you would have to re-write with each new app. The thing that it doesn't do is hold you hand and tell you exactly the way things should be done as some of the other frameworks do.
- mercer 12y agoThanks for pointing out the distinction. I forget about that sometimes. That said, React is a "A Javascript Library for Building User Interfaces." And to me me it does feel more like a library than a framework.
- modarts 12y agoReact is a library, plain and simple. It has literally no opinions on even basic stuff like routing, or how to manage application data. It takes your data as an input and by some mechanism lays out a visual representation of it defined by your components render methods, being sure to update the visual representation as the data changes. The rest are implementation details.
- rimantas 12y agoThe thing is, for the web you should not need frameworks at all. A couple of libs maybe, but what we are seeing now is getting ridiculous.