Post
Had a bit of a look back again at discussion around the #Rails leadership problem, and it seems clear that the Rails Core team is 100% on board the DHH train - there seems to be no dissent at all.
So I guess asking them to take action is pointless, and a complete fork is the only way. I wonder if there are many ex-Rails core people out there who would be willing to step back in to help get a community fork off the ground...
@Floppy Kind of wondering if it would be easier to move to another technology ecosystem than to make a large scale fork of Rails. It's so integrated to the dependencies that it wouldn't be enough to fork Rails itself, as many of the 3rd party dependencies would also need to be forked.
I remember reading a good blog post about it a few months ago, where the overall conclusion was that it was less painful to switch programming languages than to distance away from Rails inside of the Ruby ecosystem.
@autiomaa yeah, that would be hard, and moving away slowly to something like Hanami is probably what I'll personally end up doing, but god, it's such a shame, and such a vast amount of work.
@Floppy Yeah. It's a mess to migrate from one ecosystem to another in any case.
People are having second thoughts on a lot of frameworks, even after shorter amounts of years, and it's often a painful process to (incrementally) rewrite things to something else. Often the key question is whether the time investment is worth it, no matter how bad things are with one framework.
A space for Bonfire maintainers and contributors to communicate
