What a best alternative for FlowRouter now after lost arunoda and kadira?

[cyclops]

@dirkgently

This is esp true in JS where there’s something new every week. The goal of open source is to encourage contributions or fix bugs yourself, otherwise you’re just using the product like a blackbox.

I disagree with this. It’s only true for big team or expert people. Someone like me and my team with lower level that switched to meteor recently can’t fix FlowRouter, Meteor, Meteoric, MUP or … . And It’s not possible for many of us.

@maxhodges

But, yeah, in the case of meteoric124/meteoric, a package with only 22 stars, there is more risk when there is only a small number of active users.

At that time meteoric124/meteoric was the only active fork of meteoric/meteoric (nikw version) man and we haven’t any other choice in Blaze world. I think history going to repeat and now FlowRouter going to shrink to many fork then stars and active users split to some groups and it’s possible to dead project after some times.

@maxhodges

Rather than re-write your UI three times, how about if you just hire someone to patch the package which you depend on? Wouldn’t that be cheaper? There are dozens and dozens of Meteor devs on WeWorkMeteor. If your team doesn’t have the experience to maintain that package, wouldn’t it be more cost-effective to pay someone for a few hours of their time to help you out, rather than re-develop your entire UI using a new framework?

My situation a little hard to explain man. I told a little later to you. We can’t transfer money from my country so we can’t use tools like WeWorkMeteor and hire someone for these type of tasks and here we need the most robust stack for developing.

Maybe still FlowRouter is the best choice for you but for me and my company until now in this topic I prefer to switch to React and React-Router based on @awatson1978 advise.

But I’m still waiting some days maybe someone can introduce a better solution in Blaze world.