Browser Makers Launch New Project For Writing Documentation For Web APIs (zdnet.com) 13
A coalition of tech companies announced today the launch of Open Web Docs, a new initiative to help write documentation for Web APIs, JavaScript, and other web tooling and platforms. From a report: The new project does not view itself as a replacement for MDN Web Docs, a website hosted by Mozilla, where all browser makers agreed to move the official Web API documentation back in October 2017, and stop developing their own, often diverging, documentation sites. Instead, in a press release and FAQ today, the Open Web Docs team said their role is to fund, coordinate, and contribute to MDN Docs going forward. The new initiative comes after Mozilla laid off 250 employees last summer, including many of its MDN Web Docs staff. Open Web Docs comes to fill this void and provide the labor force needed to continue updating the MDN Web Docs portal.
"all browser makers" (Score:3)
You mean Google?
I understand. Those poor poor guys certainly can't afford to host such a site! ;)
Re: (Score:2)
Apple, Google, Mozilla and Microsoft? But yeah, your comment still applies to all of them.
Re: (Score:2)
I thought microsoft had given up and started using chromium?
Re: (Score:2)
You could also say that Google has given up and forked Blink from WebKit.
Re: (Score:2)
By that metric there are dozens, maybe hundreds of browser makers. But realistically most of them follow the upstream changes if only a couple, and chromium is the biggest at the moment.
I eat Perl code for breakfast (Score:1)
Yesterday I this problem and I was like %strace -e trace=File-F =p 4875 | grep fopen|perl -nle '$_=~s/\[\"[.*]\"\]/\1/G'|xargs find / = exec touch {}\;
and the problem was gone.
Re:I eat Perl code for breakfast (Score:4, Funny)
Today I was reading %strace -e trace=File-F =p 4875 | grep fopen|perl -nle '$_=~s/\[\"[.*]\"\]/\1/G'|xargs find / = exec touch {}\; and my brain was gone.
Re: (Score:2)
That's about it. Printer line noise like that is surprisingly easy to write, but damn near impossible to read. When you see something like that in production, you can safely assume the developer's brain has gone missing.
whatâ(TM)s wrong with gRPC? (Score:2)