he/him 
For the last few years I’ve been strongly swaying from “monolith tools” to “plugin everything”. I don’t think either approach is actually sustainable. Likely need something that’s a mix. Not sure what it would look like though.
-
Similarly, I'd like to see more officially endorsed "stacks" or "layers" of plugins/tools as a common, well-supported and featureful starting point, but keep a small core and ejection pathways for when people outgrow the official setup.
Yeah I think I agree. What’s hard is defining the point that a use case has “outgrown”. Ideally a tool should be able to scale.
-
-
Yeah, I'm not sure if I still believe the benefit of minimalism cleanly outweighs the downsides of diluted effort and quality in userland. Userland works well for experimentation, but not so much for reliable, solid tooling. Something in-between is needed.
-
I think the monorepo pattern helps a lot here but projects could probably further leverage their influence and organising power to make a userland subset feel like core?
End of conversation
New conversation -
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.