Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MDN Plus

hacks.mozilla.org

Post reply on HN
Print view View original

201–210 of 322 posts

Re: MDN Plus

#201

Post by zamadatix »

akvadrako wrote: post #149
999900000999 wrote: post #145

Why does everything need to be a subscription. Sell me a product, like a JavaScript book or some merch. Or just put up the donation link. I do want to give y'all money, but a recurring subscription is too much.

Yeah, automatic subscriptions are terrible. What if you stop using it for a few months or years? Do you un and re subscribe each time? You'll need a spreadsheet to keep track of all these things. A lifetime subscription for a few hundred bucks seems like it would make more sense. Or paying per use, like a cent per page. Easier for accounting and for peace of mind.

Love those lifetime subscriptions, or ones that at least let you do more than 1 year up front but not on auto-renew.

Re: MDN Plus

#202

Post by bluedays »

dend wrote: post #63

This is an interesting take on documentation - mainly because I fail to see the value proposition in paying for the functionality provided. Speaking from my own experience: - Notifications. I am not sure that I've ever needed to know when a doc is updated, because if there is anything radical coming on the market (or in a spec proposal), there are other avenues to find out about it. - Collections. That is already a f…

Think of it as an easy way to donate to Mozilla

Re: MDN Plus

#203

Post by selectnull »

jefftk wrote: 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!

I will. As soon as they allow me to pay, because I do not plan to move to US or Canada.

> Today, MDN Plus is available in the US and Canada. In the coming months, we will expand to other countries including France, Germany, Italy, Spain, Belgium, Austria, the Netherlands, Ireland, United Kingdom, Switzerland, Malaysia, New Zealand and Singapore.

Re: MDN Plus

#204

Post by mminer237 »

chatmasta wrote: post #195

Fundamentally, maintaining MDN is costly because of the rate of instability in rapidly changing browser APIs. Those APIs change quickly and inconsistently because they’re managed by a centralized cabal of a few corporations with a combined multiple trillions of dollars in market cap. And yet, somehow it’s Mozilla, the browser vendor with the least money, that ends up saddling the cost for MDN. Why is this? In general…

If W3C or WHATWG try to "tax" Google, Apple, or Microsoft to participate, they will lose all significance the next day as big tech starts their own exclusive group to define web standards. They completely control all influential browsers. Whoever makes the implementations gets to choose the standards.

Unlike governments, standards committees have zero enforcement power.

Re: MDN Plus

#205

Post by mminer237 »

dend wrote: post #63

This is an interesting take on documentation - mainly because I fail to see the value proposition in paying for the functionality provided. Speaking from my own experience: - Notifications. I am not sure that I've ever needed to know when a doc is updated, because if there is anything radical coming on the market (or in a spec proposal), there are other avenues to find out about it. - Collections. That is already a f…

Notifications for new web standards/implementations is actually something I wanted this morning, but I just went to https://caniuse.com and added its news page to my RSS reader.

Re: MDN Plus

#206

Post by chrisseaton »

chatmasta wrote: post #195

Fundamentally, maintaining MDN is costly because of the rate of instability in rapidly changing browser APIs. Those APIs change quickly and inconsistently because they’re managed by a centralized cabal of a few corporations with a combined multiple trillions of dollars in market cap. And yet, somehow it’s Mozilla, the browser vendor with the least money, that ends up saddling the cost for MDN. Why is this? In general…

The standards organisations don’t have any authority to do that, and why should they? Who’s mandate would they be operating under?

Re: MDN Plus

#207

Post by spicybright »

chatmasta wrote: post #195

Fundamentally, maintaining MDN is costly because of the rate of instability in rapidly changing browser APIs. Those APIs change quickly and inconsistently because they’re managed by a centralized cabal of a few corporations with a combined multiple trillions of dollars in market cap. And yet, somehow it’s Mozilla, the browser vendor with the least money, that ends up saddling the cost for MDN. Why is this? In general…

I would love to see a solution like that. Or even if we could reliably tie a corporation to pay a fixed amount if they use free software would be nice.

Re: MDN Plus

#208

Post by acdha »

bluedays wrote: post #202
dend wrote: post #63

This is an interesting take on documentation - mainly because I fail to see the value proposition in paying for the functionality provided. Speaking from my own experience: - Notifications. I am not sure that I've ever needed to know when a doc is updated, because if there is anything radical coming on the market (or in a spec proposal), there are other avenues to find out about it. - Collections. That is already a f…

Think of it as an easy way to donate to Mozilla

Or, better, for your employer to do so. It’s really hard to get permission to donate money at many large organizations but if the CIO kicks in $20k/year for support, training, etc. the accounting department won’t even blink.

Re: MDN Plus

#210

Post by wahnfrieden »

spicybright wrote: post #207
chatmasta wrote: post #195

Fundamentally, maintaining MDN is costly because of the rate of instability in rapidly changing browser APIs. Those APIs change quickly and inconsistently because they’re managed by a centralized cabal of a few corporations with a combined multiple trillions of dollars in market cap. And yet, somehow it’s Mozilla, the browser vendor with the least money, that ends up saddling the cost for MDN. Why is this? In general…

I would love to see a solution like that. Or even if we could reliably tie a corporation to pay a fixed amount if they use free software would be nice.

You won’t find a satisfactory solution to this under the economic model they operate within
Post reply on HN