But spend has to be justified. There needs to be a paid version with at least one functional change for a business to be able to sponsor it.
We can bullshit all day to finance about it being a "business need" for... I don't know, dark mode, or for the table to list IE6, or a breakdown by country, or something that most users won't miss. But it has to be present, so we can make the case. It can't be a donation, it can't be optional, and we need to get something out of it. That's the only way to get businesses to pay for open source.
Give everyone free access to MDN for X articles per month, New York Times style. Then sell a MDN Pro subscription with unlimited access and exclusives for $39/mo/user or $399/year. There's tons of examples in the cloud space of this working, like Linux Academy's online training or A Cloud Guru etc. that are making millions per year.
Just for reference, a MSDN subscription is $5,999 the first year and $2,569 for a renewal (but does come with a ton of stuff)... None of this 50-100 dollars per year or you're just setting yourself up for failure from the start.
Perhaps a similar approach could work for MDN.
I believe it HAS to be kept free for the general public, no matter what.
Of course, as other commenters have been pointed out, it's hard to sell companies on paying something they "have" for free. Which is why companies will shell out big money for the O'Reilly Learning Platform or MSDN ($500/year/seat for the former!) but not even think about spending money on a community resource.
In fact, Microsoft now calls MSDN subs Visual Studio subscriptions, to emphasize that the main reason to buy one is to get premium VS features and personalized developer support.
The people providing the service should get paid. Who bears the cost in the end, and whose credit card gets billed, are just implementation details. Choices for employers and employees to make among themselves. The provider doesn't care. The provider gets paid.
Employees will like to read that employers should pay, because they don't want to pay. Nobody likes to pay, including employers. But in the end, employers pay employees for value delivered. If that value includes the benefit of a service that costs money, it's part of value delivered.
Maybe the employee pays and the employer reimburses. Maybe the employer pays and the employee's pay, benefits, or expenses allowance gets docked accordingly. Maybe the employee and the employer split the cost somehow. Maybe the employee bears the cost entirely, so employees who can do without the service have financial incentive to do so.
It's not up to the provider to figure this out or negotiate it. If diners want to argue about who pays how much of the tab, the restaurant still gets paid. If tenants want to argue about who pays how much of the rent, the landlord still gets paid. In the USA, auto mechanics usually own their own tools, while in Germany, garages usually provide them. Either way, the toolmakers get paid. They don't wait to get paid until employee and employer figure it all out.
Basically the statement you made that employees are paid based on value delivered is not really accurate in most cases.
(But then I live in a country where unions are normal, so I can't speak to how it would be perceived elsewhere.)
https://visualstudio.microsoft.com/vs/benefits/#training?cat... - you can see that the learning materials you get for subscribing all come from third-party partners, from whom you could buy the same things separately.
>Their employers, big or small, should be the ones paying for it.
Your argument is counter intuitive, if it is truly a reference, then surely the developers themselves should pay for it.
A company hires a developer with the expectation that they know their field (including the standards etc.). It is the developers' own concern if they (understandably) need a reference to help them execute what they were hired for.
If the developer is hired as an employee, then in general I'd say no. It's the employer's responsibility to provide the tools and resources the developer needs to perform the job effectively -- whether that's hardware, software, documentation, or working environment.
Just like lawyers and LexisNexis and similar tools.
Of course, we all know that asking startups to actually fund open source (whether code, documentation, or learning resources) is like pulling teeth. I'd say maybe the collapse of some larger open source project(s) could convince companies to start actually giving a shit about whether or not the maintainers of the technology their entire businesses rely on have enough money to continue developing said technology, but it's more likely the companies would just say "well, let's put 10 engineers on this problem for a month to replace this dead open source technology with something new and shiny" and not recognize how much more they've had to spend. Or, y'know, they'll go with paid support of a Microsoft product or something.