Profile picture
substack @substack
, 9 tweets, 2 min read Read on Twitter
I feel like a lot of popular frameworks could be completely replaced with better docs about how to build things with platform features and ala-carte libraries.
how it usually shakes down:
"I want to do X."
"Framework Y does X."
"I must learn framework Y to do X."
but there are few resources available for how to do X outside of Y, even when Y is largely superfluous
this documentation problem is compounded by how popular projects can bring in resources to either pay people to work on docs or somebody can otherwise build their career around a big bundle of semi-related features called Y
the downside of this phenomenon is when you have a problem that doesn't quite agree with the assumptions of the core framework, you'll spend a huge amount of time fighting against those assumptions. often many times more effort than writing something from scratch.
and the discourse around "from scratch" is that it's just about always more wasteful, but I haven't found that to be the case. and when you use appropriate decoupled libraries (that you can easily throw away or swap out), it's no more wasteful than using a big framework.
with the upside that you can incrementally refactor the stack as your assumptions change because the components are relatively less coupled. It's a bit of work to set things up this way, but it's not a huge amount of effort or anything.
the main hurdle is convincing other people to take this more modular approach, which is very hard to do. partly because something with slick marketing and lots of usage is considered "safe" even if you know from experience you're going to encounter huge maintainence burdens later
plus the paternalism of the framing in technology marketing about "teams" along with the desire to hire around commodity skills and not wanting to spend any time on training
because this is such a pervasive phenomenon, building things from scratch (+ala-carte modules) is a less common skill, which shapes perceptions and makes the status quo stick. but I don't think it's an intrinsically more or less difficult approach, just different.
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to substack
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member and get exclusive features!

Premium member ($3.00/month or $30.00/year)

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!