21–30 of 202 posts
Am I the only one put off by the AWS (S3+Lambda) lock-in they seem to be creating for themselves?
It should only take a couple of days to switch those to a different cloud provider. When building a Jamstack website there is only very thin logic in the Lambda itself, and S3 is only used as managed file storage.
So they're hoping that they can replace the people they fired with open source contributors working for free.
If the alternative is to close shop and let it die entirely, I don't have an issue with it It's not like they were extremely profitable and fired people to squeeze an extra buck Laying off people isn't inherently evil
So they're hoping that they can replace the people they fired with open source contributors working for free.
Man these kind of views bother me so much. They’re taking one of the most (if not, most) useful documentation sources for cross platform web development that benefits them very little, and moving it to a system of open contribution so it can live past the company’s financial problems. And this is your first take?
Earlier quoted context omitted.
If the alternative is to close shop and let it die entirely, I don't have an issue with it It's not like they were extremely profitable and fired people to squeeze an extra buck Laying off people isn't inherently evil
I have more of a problem with who they laid off than the fact that they laid people off. I'm probably biased as an engineer, but IMO the people who actually create your products should be the last ones to be laid off, not the first. And if the company is struggling, highly paid execs should take a pay cut before you start laying off lower-paid engineers.
Translations aren't even that expensive, especially relative to the cost of producing the docs in the first place. It hurts me to see MDN so starved of resources that they can't pay for even that small piece.
MDN has been key to so many people's technical education. High-quality web documentation is an essential resource for those looking to elevate themselves into a technical career these days.
Much of the world (20%, according to their own research) is set to lose access to this vital body of knowledge.
So they're hoping that they can replace the people they fired with open source contributors working for free.
If the alternative is to close shop and let it die entirely, I don't have an issue with it It's not like they were extremely profitable and fired people to squeeze an extra buck Laying off people isn't inherently evil
I am a big fan of jamstack. For a lot of my client's use cases it allows me to save them a lot of money and headaches while delivering a better product, especially with a headless CMS like Netlify CMS
I still don't fully grok the term. Is it a loose/blanket term sorta like 'devops' or is it a more literal prescription of actual requirements and practices?
Earlier quoted context omitted.
Man these kind of views bother me so much. They’re taking one of the most (if not, most) useful documentation sources for cross platform web development that benefits them very little, and moving it to a system of open contribution so it can live past the company’s financial problems. And this is your first take?
Granted, it depends on how it turns out. But my first impression is that authoritative reference documents of MDN are going to become cluttered with comments and disagreements.
I change, I publish, it's done. And if my change was wrong, or opinionated, or bad, it's just like that until somebody else catches it and fixes it back.
Earlier quoted context omitted.
Man these kind of views bother me so much. They’re taking one of the most (if not, most) useful documentation sources for cross platform web development that benefits them very little, and moving it to a system of open contribution so it can live past the company’s financial problems. And this is your first take?
As far as I can see, Mozilla have no reason to be losing money other than their own mismanagement.
This is seriously entitled. Mozilla gave us an amazing resource, entirely for free. This attitude isn't right, it's toxic and harmful.
Mozilla is in a spot of difficulty, and instead of taking a resource that is operating entirely at a loss down, they're taking the engineering steps to ensure thez resource can outlive them.
That their mismanagement caused them the difficulty is entirely irrelevant here. It could have happened in a myriad of other ways. We should be praising Mozilla and the MDN tech team for the steps they're taking in making sure the MDN can live on.
Reading between the lines, it seems obvious that Mozilla wishes to stop funding localization. Translations aren't even that expensive, especially relative to the cost of producing the docs in the first place. It hurts me to see MDN so starved of resources that they can't pay for even that small piece. MDN has been key to so many people's technical education. High-quality web documentation is an essential resource for…