Their announcement said that Mozilla is killing off a lot of development on "internal tools." I thought that meant things like Bugzilla or MDN. No reason to sla

Their announcement said that Mozilla is killing off a lot of development on "internal tools." I thought that meant things like Bugzilla or MDN. No reason to slave away on MDN when others have so much resources. But I had no idea they'd kill something so core to their future browser development. I strongly disagree with this decision. They might as well kill gecko too, if there's no exciting future anymore. Samsung had invested in the past, so hopefully they or someone else will pick up where Mozilla left off. I do think that Mozilla should slowly try to reduce the amount of unique processes that they have. Part of what made servo so successful is that they did all the development on GitHub. Mozilla should have a top level corporate policy to transition away from all their nonstandard internal tools. Get rid of Mach, Bugzilla, Mercurial, etc. They should use GitLab or GitHub, switch to cmake, and some standard third party build service, and be done with it. Their productivity would increase, their community contributions would increase, and their overhead would decrease. But they should not have cut their DevTools, and should have actually beefed up the developer-friendliness. Compete with Electron. Compete with PhantomJS. Improve the experience of Progressive Web Apps on mobile. The focus on new products makes sense. I think Lockwise, Monitor, and their VPN service were all good efforts. Firefox Sync should ideally expand more into a whole suite of integrated services stop their zero-knowledge privacy-first architecture. Storage, backups, OwnCloud integration, etc. Maybe they should even acquire OwnCloud or NextCloud.