191–200 of 202 posts
This model - storing markdown files in a git(hub) repo and editing them on Github is getting more and more popular. It would be great to see Github add a more rich markdown/frontmatter editor to their interface to accomodate this.
Like Codespaces ( https://github.com/features/codespaces )?
It is going to be the 5th iteration of CMS/wiki software. Hopefully this is the right one. 1. Netscape DevEdge 2. MediaWiki 3. Deki Wiki (renamed to MindTouch, closed source since 2013) 4. Kuma 5. Yari There's a nice history here: https://developer.mozilla.org/en-US/docs/MDN_at_ten/History_...
And the problem is that each time the software changes, attributions are lost. I used to be active contributor to MDN with thousands of contributions. Countless hours of volunteer work. When the platform changed and my attributions were lost, I stopped contributing. I had no street cred anymore. I was angry. The switch to GitHub means the same problem once again. Nice way to alienate your community, MDN. Good luck wi…
I mean Mozilla earns hundreds of millions a year and pays its CEO several millions a year, they could have well afforded to not violate your rights by spending a few dev days on writing a proper importer scripts.
So, they say that the system is evolving, but from these parts of the article I would argue that the ease of contributing (which is the important part) is taking a massive hit: > "you will no longer be able to click Edit on a page, make and save a change, and have it show up nearly immediately on the page. You’ll also no longer be able to do your edits in a WYSIWYG editor." > "you won’t have a WYSIWYG to instantly se…
I _wish_ MDN had a user-friendly contribution process. My experience has been _far_ from that. I very much welcome these changes. In late 2017, I spent upwards of 80+ hours standardizing 80 different MDN docs pages so they used the same best-practices layout as other more popular docs pages on the MDN.[1] Of the 85 pages I updated to have better formatting, over 18 were reverted by random contributors within 2 days w…
Earlier quoted context omitted.
Those are unpaid volunteers. If Mozilla robs them attribution for work (and yes this is work), then what's left? Specially now that they fired every single paid worker.
> Those are unpaid volunteers. If Mozilla robs them attribution for work (and yes this is work), then what's left? Warm fuzzy feelings? The knowledge that people read your article thousands of times every day? Honestly, while I agree that it’s a bit sad to lose the attribution, I find it hard to be sympathetic with people who get salty over losing internet points.
It’s a knowledge base. It’s well designed documentation. Something that many folks in IT lack at times. Showing people you can properly document knowledge in a collaborative way helps you get hired.
Earlier quoted context omitted.
Those are unpaid volunteers. If Mozilla robs them attribution for work (and yes this is work), then what's left? Specially now that they fired every single paid worker.
Mozilla never promised them any pay in the first place
Earlier quoted context omitted.
I assume they could've put it on their resume and gotten something from that. Now it's just baseless claims.
If your potential employer is so skeptical of you that they don’t trust you when you tell them you wrote certain articles on MDN, they’re not likely to hire you in the first place.
Earlier quoted context omitted.
Because HN commenters always feel like they know better and like to talk down on any changes even when they have no context for why the decision was made.
Or, you know, because it’s a legitimate concern that readers on HN value higher than the MDN maintainers.
Earlier quoted context omitted.
Fun fact: I have an open source repo with millions of downloads, tens of thousands of active users, and, for at least a year, a prominently displayed donate button. How much in donations do you think it took in over its lifetime? Hint: it's less than $200. Donations don't really work.
> for at least a year, a prominently displayed donate button. Just to be sure, are you referring to the "BuyMeCoffee" button on the GitHub page for the extension ( https://github.com/VSCodeVim/Vim )?
Earlier quoted context omitted.
If you've chosen to use a web browser that's forked from an old version of Firefox and isn't aiming for compatibility with modern Web Platform Tests, you're going to encounter a lot of obstacles. The fact that you can't see the server-side code generating the failing client-side code, which you can see, seems like the least of them.
What does creating a PR even need in terms of functionality? It's effectively nothing more than a big HTML form with some inputs, something that's been around and working perfectly fine in browsers for decades . The other comment here about how it's like complaining it does not work in IE6 is really pertinent: Yes it damn well should, because I should not need the latest technology just to do something that would've…