6 ms·
Some of these are a bit spurious. I mean, Venkman was replaced by Firebug, which was much better. MXR was similarly replaced by DXR. Unlike Google, which look
by toyg 6y ago
Some of these are a bit spurious. I mean, Venkman was replaced by Firebug, which was much better. MXR was similarly replaced by DXR.
Unlike Google, which look much more arbitrary in their shutdowns, Mozilla typically kill projects that are already on their last leg, or replace them with something objectively better.
- deleted 6y ago[deleted]
- pletnes 6y agoMaybe that’s true, but this is why I never use any mozilla features to store important data such as passwords - suddenly the project is on the last leg, and shortly thereafter the last leg is cut off life support.
- toyg 6y agoI honestly don't know what important data you might have been storing or how, but passwords are definitely one thing that is still synchronized between all your FF instances.
- pletnes 6y agoI know it’s there now. But when will it end? Same argument goes for Send and other services.
- toyg 6y agoProfile sync is so deeply tied into the browser that ripping it out to abandon it would likely be more costly than just keeping those servers running forever, I think. As long as FF lives, it will keep that sync going. Any new "external" feature is another matter, of course.
- teekert 6y agoIm getting a bit afraid about my use of lockbox indeed... Also for all the people I recommended it tot :s
- healsdata 6y agoTo be fair, I think that logic applies to some of the items on Google's list too. Like Google Nexus? They changed the name and scope of their phone line. AngularJS? They took the framework in a different direction.
- OJFord 6y agoThe targeting of the Nexus line was completely different to Pixel though, they could easily have co-existed. And there was a gap between them. I've never worked for Google, but I assume 'kill Nexus' and 'launch Pixel' were independent decisions, the latter unforeseen at the time of the former.
- devrand 6y agoIsn't the Pixel "a" line similar to the old Nexus line? Granted there was a decent gap in time since it didn't exist until the 3rd generation Pixel.
- syshum 6y ago>> Like Google Nexus? No, they 100% killed Nexus.... Pixel line is in no way, in any shape or form a successor to Nexus. Nexus was a reasonably priced unlocked reference phone targeted to Power Users Pixel is an iPhone Competitor targeted to Carriers to be featured as an iPhone Alternative Completely different markets, focus and goals >>AngularJS? They took the framework in a different direction. Again no, Angular is TypeScript, AngularJS is Javascript, these are not the same thing, and it is far from "a different direction"
- vlang1dot0 6y ago>> Nexus was a reasonably priced unlocked reference phone targeted to Power Users Nexus One: $530 Nexus S: $530 Galaxy Nexus: $200 with standard 2 year contract (basically the same as any flagship phone at that time) Nexus 4: $300 Nexus 5: $350 Nexus 6: $650 Nexus 6p: $500 Nexus 5x: $379 Arguably Nexus 4 & 5 were the odd ones out with their relatively low pricing. The others (excluding the 5x) were pretty much on part with flagship phone prices at launch time.
- jcranmer 6y agoHaving personal experience of some of these projects, some of their inclusion is definitely moderately unwarranted. Take Sunbird. The source tree is organized as a set of backend modules, with various products including as many of them as they need and then throwing up the main frontend window on top (although SeaMonkey really has diverged its UI in quite a few places). Sunbird was the standalone calendar app, but it was decided that the calendar maintenance team was too small to maintain a standalone calendar and instead shifted their UI focus to only supporting SeaMonkey/Thunderbird integration (aka the Lightning extension). No code that actually did anything was removed--I was the one to actually hg rm it here: https://hg.mozilla.org/comm-central/rev/f2e605ee5475 https://hg.mozilla.org/comm-central/rev/f2e605ee5475 As you mention, MXR was phased out in favor of DXR, which is itself being phased out in favor of searchfox. (I too worked on DXR, back in 2011). Prior to MXR, there was LXR (as in, lxr.mozilla.org), but I'm not sure it's worth mentioning as a separate project since it's basically an unmaintained fork of the LXR project. While we're on the topic, there's a lot of "missing" webspaces here. Bonsai was a webtool to display atomic CVS commits, Tinderbox was the UI for seeing if the tree was broken (on fire) or not (this later gets supplanted by TBPL (tinderbox/pushlog), itself rewritten to not be a pile of hacks as treeherder), and there's definitely a buildbot clone/fork/I don't know floating about somewhere in the mix. There's various versions of things like the addons website or support websites that I can't even enumerate off the top of my head as well. Some of these (like old addons stuff) was completely in-house, while others (like pastebin and etherpad) are hosted versions, potentially with some modifications, of other projects. None of these are listed, but do they even deserve to be listed? It's not consumer-facing, and I'm sure even many Mozilla developers would struggle to realize some of this stuff existed.
- avery42 6y agoThank you for the feedback, I'm really glad to get some insight from someone who worked on some of these projects! Thanks for the info about Sunbird, I had the understanding that some code was shared, but wasn't sure how much. I'll update it's description at some point. You bring up good points about stuff like forks, internal tooling, and hosted versions. Up until now I haven't included forks and hosted versions that didn't make significant changes (which is why I included MXR and not the LXR instance). I'd like to include internal tools where possible, but I think the main obstacle is finding sufficient info. I think where this differs from Killed by Google is that Mozilla has had less consumer services that were discontinued while they had an active user base. I'm happy to include old experiments, internal tools, etc., I really enjoy digging these things up. Thank you again, I'll take a look at some of the services you mentioned!
- stickfigure 6y agoPersona stands out here as a huge opportunity lost. It offered a future with a fully decentralized, federated authentication scheme, based on open protocols. Yes, they made some mistakes and adoption was poor. But it worked well and the underlying protocols are something the internet still desperately needs.
- gilrain 6y agoI was all in on Persona for side projects, and would have started using it professionally... was extremely disappointed they gave up on it. It was excellent to use.
- i80and 6y agoI dabbled in Persona for personal things. It was DELIGHTFUL, and while I understand the rationales for why it was canned, I still harbor some sour grapes.
- pavon 6y agoAgree. What really frustrated me about Persona, was that the way they portrayed the project was that it was not yet ready for production adoption[1]. And then they cancel it because people weren't using it. I know I played around with a proof of concept implementation internally, but never deployed it publicly, which was a decision based primarily on their own messaging. [1] EG the JS implementation and the dependency on persona.org were both temporary stop-gaps to enable fast-prototyping and use in other browsers, but would be replaced with a "real" implementation in the browser that supported multiple providers before broad roll-out.
- stickfigure 6y agoI used it for my company at the time as part of a dual-auth system (Facebook / Persona). We were even featured as an example on the Persona dev website. The service worked great, even for my technically-not-literate audience. And it was reliable (we sold event tickets).
- rhn_mk1 6y agoWhy is it not continued as a community project?