Live data from Hacker News

MDN Plus

hacks.mozilla.org

31–40 of 322 posts

Re: MDN Plus

#31
post #19

What a cash grab Firefox devs should quit this sinking ship ASAP, fork the browser and setup some sort of developer funds like blender/krita/gimp/godot and many other I'll be happy to donate directly to the firefox team without having to go through this mafia

https://donate.mozilla.org/en-GB/

I don't think money is the issue with $500M coming from Google per year.

Re: MDN Plus

#32
post #3

Everyone who's been saying "I wish they would just charge money for this", here's your chance to put your money where your mouth is!

Are they going to rehire all the dedicated editors and staff they laid off? Or is this really just charging money for all their now open source contributed content...

This is a “what about … “ response.

The only important thing is if they are going to invest in new staff in the future. The old staff almost certainly have new jobs in new companies.

Let’s not move the goal posts. Having reason to invest in enhancing documentation, and creating a viable revenue stream by doing so is a good thing, even if decisions in the past are regrettable.

Re: MDN Plus

#33
post #19

What a cash grab Firefox devs should quit this sinking ship ASAP, fork the browser and setup some sort of developer funds like blender/krita/gimp/godot and many other I'll be happy to donate directly to the firefox team without having to go through this mafia

https://donate.mozilla.org/en-GB/

This doesn't go to the Firefox team. It supports the Mozilla Foundation, but Firefox development is funded by the Mozilla Corporation.

Re: MDN Plus

#34

Collections seems completely redundant when we have the ability to use favorites/bookmarks within our browser. Unless i'm missing something that makes collections significantly different/better.

Unrelated blog post: For a web app I recently designed a "favoriting/bookmarking" system that was requested by several people.

Only like two to three people used it for a while, before they left for other jobs.

Now no one uses it.

Re: MDN Plus

#35
post #13

I suppose offline access is nice. I think I'd rather pay for the ability to just download the whole site in some officially supported way. Priming a PWA baked into browser storage is a little roundabout. I want it to be grepable.

There used to be a tool I used that just downloaded all the files of a site locally that the browser requested. Would that be enough here or are you imagining something like it also points all the links to be local and goes and saves future pages as well?

Httrack?

Re: MDN Plus

#36

Earlier quoted context omitted.

Are they going to rehire all the dedicated editors and staff they laid off? Or is this really just charging money for all their now open source contributed content...

This is a “what about … “ response. The only important thing is if they are going to invest in new staff in the future. The old staff almost certainly have new jobs in new companies. Let’s not move the goal posts. Having reason to invest in enhancing documentation, and creating a viable revenue stream by doing so is a good thing, even if decisions in the past are regrettable.

No the "we'll pay for it!" comments were in the context of the staff being let go and departments spun down. We meant, we'll pay to keep this high quality content going.

No one said, sure yeah fire all those folks, flail around for a year, convince people to just give free content for funsies, then we'll slap a price tag on it so the exec bonuses can keep getting higher.

We'd pay for the old Mozilla that cared about a high quality web. That Mozilla appears to be long dead.

Re: MDN Plus

#37
I'm curious how often people are needing offline access to documentation for web development.

Re: MDN Plus

#38
post #13

I suppose offline access is nice. I think I'd rather pay for the ability to just download the whole site in some officially supported way. Priming a PWA baked into browser storage is a little roundabout. I want it to be grepable.

You can grab the full repo with the content here: https://github.com/mdn/content

Re: MDN Plus

#39
post #14

Am I an outlier or does their head of product not really appear to have a bead on what developers actually want?

This actually is a very good product.

Pain points it addresses: 1. Notify when something changes 2. No clear and customizable learning path

Business outcomes: 1. Generate revenue keeping privacy intact

It seems to me this is a good solution. No need to make it about their head of product.

Re: MDN Plus

#40
post #3

Everyone who's been saying "I wish they would just charge money for this", here's your chance to put your money where your mouth is!

Are they going to rehire all the dedicated editors and staff they laid off? Or is this really just charging money for all their now open source contributed content...

Neither. As the article specifically mentions, they will not be charging for the existing open content, or any future changes or additions to it. Why you would try to suggest they might do this is beyond me.

They will be selling additional "premium features" at launch time, as described in this article, and plan to sell specifically created additional content, like in-depth articles, in the longer run, as described in previous articles.

Maybe this will enable them to hire back some of the people they let go (assuming these people are willing). But the main goal is to put mdn on a level of funding where little or no funding from mozilla is required anymore.

Post reply on HN