voxpelli,
@voxpelli@mastodon.social avatar

Seems like every larger open source project will have its moment of small-core vs big-core discussions.

Should the core only contain the bare minimum of essential parts and leave the rest to the ecosystem or should the core be plug and play?

One solution I prefer as a solution to both is by creating distributions that bundle the small core with a default set of modules from the ecosystem. Then one can decide to start of with a distribution or with the small core itself.

voxpelli,
@voxpelli@mastodon.social avatar

Plurality vs mono-culture
Competitive advantage through flexibility and adaptability vs through domination

voxpelli,
@voxpelli@mastodon.social avatar

Embracing the ecosystem or sherlocking it https://thehustle.co/news/sherlocking-explained

dominik,
@dominik@nona.social avatar

@voxpelli yeah, I quite like how is doing that. They have a pretty minimal default installation and a "webapp" bundle that adds basically all the bells and whistles (sometimes a bit too many, but it's not hard to remove the unneeded stuff)

voxpelli,
@voxpelli@mastodon.social avatar

@dominik Yeah, Drupal somewhat did that back in the days when I was using it as well

Meanwhile, all JS-runtimes are now having and arms race on who can add the most features to core – and I’m missing the small lean Nodejs of old – now it’s trying to out-feature both Deno and Bun

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • kavyap
  • InstantRegret
  • ethstaker
  • DreamBathrooms
  • mdbf
  • magazineikmin
  • thenastyranch
  • Youngstown
  • tacticalgear
  • slotface
  • Durango
  • khanakhh
  • rosin
  • everett
  • Leos
  • vwfavf
  • normalnudes
  • osvaldo12
  • cubers
  • GTA5RPClips
  • cisconetworking
  • ngwrru68w68
  • anitta
  • provamag3
  • tester
  • modclub
  • megavids
  • JUstTest
  • All magazines