I think "react is not a framework" is basically a sleight of hand.
-
-
Replying to @wycats
I think putting React in the same category as Ember is not fair to both.
1 reply 0 retweets 1 like -
Replying to @samerbuna
I think putting React is the same category as Backbone is not fair to React. React has a lot of frameworky elements (like taking complete control over scheduling) and it's better for it. Hiding that just to put React in the "library" category is just confusing.
1 reply 1 retweet 0 likes -
Replying to @wycats
Fair point, but React lacks a lot of the frameworky elements as well. Maybe we need a new category for it.
1 reply 0 retweets 0 likes -
Replying to @samerbuna
I guess I think the categorization does more harm than good. Focus on use cases: Ember is squarely targeted at apps (and therefore has a lot more for apps built in), while React is less opinionated about use case but requires you to build up your use case yourself.
1 reply 0 retweets 0 likes -
Replying to @wycats @samerbuna
Neither of those are "better" the way your blog post implies. If someone's building something that's firmly "an app", it's misleading to tell someone they should work up to app themselves just to learn it. But maybe their use case justifies it anyway.
1 reply 0 retweets 0 likes -
Replying to @wycats @samerbuna
I'm not saying "use the best tool for the job" abstractly. I'm saying a use-case based analysis is better than categorizing tools into "framework" or "not a framework" and then broadly advising *all* developers to "not learn a framework" as your post did.
1 reply 0 retweets 0 likes -
Replying to @wycats
I didn't mean to say a library is better than a framework but rather learning how to use a framework is a big commitment that needs a reason (job, project). I learned Ember when I needed to use it. I think understanding small libraries is a better time investment career-wise.
1 reply 0 retweets 1 like -
Replying to @samerbuna @wycats
Thanks for the feedback. I modified the article to remove the "React bias". The point I wanted the article to highlight is: learn freaking js itself first and how to run it correctly before wasting your time getting confused about a big framework.
1 reply 0 retweets 1 like -
Replying to @samerbuna
Thanks for listening :) I appreciated this conversation.
1 reply 0 retweets 1 like
I think you're exactly right that ppl should learn frameworks for concrete reasons, and that people can learn frameworks on the job when it comes up. There's way too much adoption confusion around "where will I get an <X> programmer". Answer: hire a JS programmer and teach them
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.