3 ms·
"We actually ended up building our own tooling to get closer to 70%. It processed maany millions of lines of python code, automatically kept track of which thin
by ClumsyPilot 5y ago
"We actually ended up building our own tooling to get closer to 70%. It processed maany millions of lines of python code, automatically kept track of which things would be best to rewrite/finish migrating first (because it would unblock other things), and continuously tried to auto-migrate any non-migrated changed code in a loop to maximize automation. The engineer cost of moving was enormous."
This was definately an opportunity for commercial software, i am not sure why companies worth hundreds of billions can't sort this out and expect a small nonprofit to provide this.
- DannyBee 5y agoFWIW - i don't disagree, and I don't expect anything in the end, it's open source. People can do what thy want. I was more pointing out the opinion given of how the user community sucked is very broken. What the "larger user" (however you want to frame it) community would have preferred (IMHO) is much better migration tooling, even if it came at a cost of improvements. The dev community chose to spend time on improvements instead. That's their choice, but it doesn't make the community wrong to be upset about it.