Live data from Hacker News

A list of discontinued Mozilla products and services

killedbymozilla.com

51–60 of 98 posts

Re: A list of discontinued Mozilla products and services

#53
post #25
post #7

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.

Maybe 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.

Im getting a bit afraid about my use of lockbox indeed... Also for all the people I recommended it tot :s

Re: A list of discontinued Mozilla products and services

#56
post #7

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.

To 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.

>> 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"

Re: A list of discontinued Mozilla products and services

#57
post #7

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.

Persona 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.

I 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.

Re: A list of discontinued Mozilla products and services

#58
post #7

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.

Having 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…

Thank 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!

Re: A list of discontinued Mozilla products and services

#59
Killing projects isn't bad. I've worked places that simply could not kill off their zombie projects. It was hell. None of these killed projects evokes any kind of wistfulness, nostalgia, or resentment in me. (Edit: Except Persona. Agreeing with another reply.)

Certainly nothing like when Autodesk killed Generic CADD.

What Google, Microsoft, Autodesk, others do is altogether different. The projects they snuff are often economically important to their customers and partners. That's sabotage.

Re: A list of discontinued Mozilla products and services

#60
post #41

Earlier quoted context omitted.

To 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.

The 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.

Isn'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.
Post reply on HN