Twitter | Search | |
Nicole Sullivan
This is going to sound like a silly question, but bear with me... ;) Why do people decide to use frameworks? I know my answers, I'd love to know yours.
Reply Retweet Like More
Tim Evko 🇺🇸 Oct 10
Replying to @stubbornella
to keep the team from killing each other!
Reply Retweet Like
Tim Caswell Oct 10
Replying to @stubbornella
I don't. I personally find the cost of learning the framework's ins and outs, limitations, costs, and abstraction leaks to typically not be worth what it gives. Then again, my apps tend to be very small, but boundary pushing prototypes.
Reply Retweet Like
Jonah Oct 10
Replying to @stubbornella
Avoiding bikeshedding. Often any consistent approach is better than the setup cost of repeating all those decisions and remove the bottleneck on getting those patterns in place for a team.
Reply Retweet Like
Deandong Merryleigh Oct 10
Replying to @stubbornella
I know many backend devs who wont use JS frameworks but will use Bootstrap I know many front end devs who do the reverse Could it be they don't want to learn? Also silly question do we consider libraries and frameworks as one and the same?
Reply Retweet Like
B.J. May Oct 10
Replying to @stubbornella
I use them for the same reason that I buy ingredients rather than growing/raising all of my own food. Smarter people than me have solved many of the problems already. I don't want to grow wheat, bake bread, milk cows, and churn butter. I just want to make toast.
Reply Retweet Like
Nicole Sullivan Oct 10
Replying to @bjmay
this is the best answer
Reply Retweet Like
Nicole Sullivan Oct 10
Replying to @deanleigh
that last question... so hard to answer. One clue? It's very hard to say if something is a framework or a library with certainty.
Reply Retweet Like
Nicole Sullivan Oct 10
Replying to @Zalambar
this is so important. yes!
Reply Retweet Like
Nicole Sullivan Oct 10
Replying to @creationix
how many people on your team? what skill levels?
Reply Retweet Like
Nicole Sullivan Oct 10
Replying to @Tevko
ooooh, how so?
Reply Retweet Like
Yousuf Shaikh Oct 10
Replying to @stubbornella
I don't use a framework is a framework too
Reply Retweet Like
Nicole Sullivan Oct 10
Replying to @uXuf
hehe. yeah.
Reply Retweet Like
Chris Coyier Oct 10
Replying to @stubbornella
Sometimes I just wanna be told what to do.
Reply Retweet Like
Nicole Sullivan Oct 10
Replying to @chriscoyier
AMEN. ;)
Reply Retweet Like
Chris Silvermαn Oct 10
Replying to @stubbornella
Also the issue of building everything in Framework X, and then a year from now it's out of favor and what do we do about that. 2nd rule of Fight Club: if I have to use a framework, I'd prefer to build it myself.
Reply Retweet Like
Ryan Florence Oct 10
Replying to @stubbornella
I write too many bugs without them.
Reply Retweet Like
Chris Dickinson Oct 10
Replying to @stubbornella
I rely on frameworks to solve problems that are adjacent to, but distinct from, the problem I'm trying to solve at hand. "How do I structure my codebase?" / "How do I test?" / "Inject mocks?" / "Respond consistently to users?" are all things I want a FW to answer.
Reply Retweet Like
Nicole Sullivan Oct 10
Replying to @ryanflorence
It me ✋🏻
Reply Retweet Like
Greg Bildson Oct 10
Cognitive load
Reply Retweet Like