4 ms·

Modular small libraries are great, I tend to cherry pick just a few. Specific frameworks like React are great too. But all these old monolithic frameworks/libr

by frik 12y ago

Modular small libraries are great, I tend to cherry pick just a few. Specific frameworks like React are great too. But all these old monolithic frameworks/libraries, that try to solve everything and there citchen sink, are so 2009-ish. They have its place in the enterprise world. And for performance optimisation you want a more modular approach.

jfaucett 12y ago
I think it has to do with the way the developer approaches the problem, their background, and their preferences. Personally I'm with you, I enjoy a small, isolated, component based approach where each component follows the unix philosophy. I think this lets you write the most performant and resuable code. Also, I think when following this style, it limits the scope of your dependences, which is another big plus. For instance, you might need a library for crypto, but you won't need one for doing your authentication system, and you won't have massive modules for handling auth that would come from a framework getting compiled into your production code. But when you go this route you do have to make a lot of "right" decisions that are made for you when using a framework. Also, I think a lot has to do with deadlines and developer speed, it initially takes a little longer to write good standalone components that are reusable, and just grabbing some framework will help get shit done in the short term, but might have the same detriments as technical debt in the long run.
lukeasrodgers 12y ago
The only js framework I'm aware of that could accurately be described as trying to solve everything and the kitchen sink is ExtJs, which includes a wide widget library, and is very opinionated about how you interact with the DOM. Ember is is not a "kitchen sink" framework, and Backbone is certainly not.
colin_jack 12y ago
Yeah that's my attitude too, Ember scared me away because of the kitchen sink approach and the fact it introduced lots of new abstractions that I hadn't seen proven elsewhere, and that didn't really seem to me to be what I would be expecting from a Web framework. Something like React bothers me far less as it smaller, less imposing, and solves real problems I've seen with other frameworks (for example by pushing clear/consistent/simple communication paths).
gildas 12y ago
> Specific frameworks like React are great too. Except React is a library. The slogan [1] clearly says "A JavaScript library for building user interfaces". [1] http://facebook.github.io/react/ http://facebook.github.io/react/
- dkersten 12y ago
  To me, React is a rendering library. The flux architecture implementations is the "React framework" that people seem to be using.

by frik 12y ago

jfaucett 12y ago

I think it has to do with the way the developer approaches the problem, their background, and their preferences. Personally I'm with you, I enjoy a small, isolated, component based approach where each component follows the unix philosophy. I think this lets you write the most performant and resuable code. Also, I think when following this style, it limits the scope of your dependences, which is another big plus. For instance, you might need a library for crypto, but you won't need one for doing your authentication system, and you won't have massive modules for handling auth that would come from a framework getting compiled into your production code. But when you go this route you do have to make a lot of "right" decisions that are made for you when using a framework. Also, I think a lot has to do with deadlines and developer speed, it initially takes a little longer to write good standalone components that are reusable, and just grabbing some framework will help get shit done in the short term, but might have the same detriments as technical debt in the long run.

lukeasrodgers 12y ago

The only js framework I'm aware of that could accurately be described as trying to solve everything and the kitchen sink is ExtJs, which includes a wide widget library, and is very opinionated about how you interact with the DOM. Ember is is not a "kitchen sink" framework, and Backbone is certainly not.

colin_jack 12y ago

Yeah that's my attitude too, Ember scared me away because of the kitchen sink approach and the fact it introduced lots of new abstractions that I hadn't seen proven elsewhere, and that didn't really seem to me to be what I would be expecting from a Web framework. Something like React bothers me far less as it smaller, less imposing, and solves real problems I've seen with other frameworks (for example by pushing clear/consistent/simple communication paths).

gildas 12y ago

> Specific frameworks like React are great too. Except React is a library. The slogan [1] clearly says "A JavaScript library for building user interfaces". [1] http://facebook.github.io/react/ http://facebook.github.io/react/

dkersten 12y ago
To me, React is a rendering library. The flux architecture implementations is the "React framework" that people seem to be using.