Embrace...
Documenting the Web together
161–170 of 212 posts
Re: Documenting the Web together
#162Embrace...
This time around, it looks like that's where the phrase ends. Until the next CEO perhaps.
Re: Documenting the Web together
#163Earlier quoted context omitted.
What else can you even write instead though
In this case, there could be literally nothing instead. > (Today, we’re excited to share some big news for developers around the world wide web: )We’re committing our resources towards making MDN Web Docs the best place to go for web API reference.
There needs to be an intro or it sounds very weird.
Re: Documenting the Web together
#164Earlier quoted context omitted.
I'm not entirely sure. I believe it has to do with the DRM implementation. While Widewine is the DRM in Chrome and Firefox, Edge uses something different[1]. I've seen people talk about Chrome being able to handle 1080p in ChromeOS. So there seems to be more than just Netflix's choice involved here. Although I bet Microsoft being proactive helped. Definitely unclear. Also I don't see any reason why Netflix wouldn't w…
As far as I understand it, you need tight coupling between the browser and the OS to implement the sort of deep-reaching DRM that Netflix/Hollywood wants for 1080p. That would explain why Edge on Windows and Chrome on ChromeOS can do it. Personally, I see it as a plus that my browser/OS combo does not support this. There have to be horrid security implications that just wait to be unturned.
Indeed: https://www.schneier.com/blog/archives/2007/02/drm_in_window...
Insistence on DRM ironically is causing the opposite effect - wider piracy of DRM-free versions.
Re: Documenting the Web together
#165Why Samsung?
Probably a case of having engulfed the industry so much that just throwing money into the industry will actually pay out for them in the long run.
And it's probably also just nice to be able to bite Google and Microsoft in the butt here. Those do benefit from a healthy web and both very much need the PR of supporting webstandards, but they could also both benefit a lot more from controlling a platform like MDN and then sneaking in pseudo standards here and there. So, Samsung helping out with MDN makes it even harder for one of those to build up their own version.
Lastly, Samsung does ship their Samsung Internet Browser on all of their Galaxy devices, which has got to be a somewhat significant share of daily internet users. Currently, that's Chromium-based, but they could be looking to eventually follow Google and Microsoft in making up webstandards.
They've also already invested into Mozilla's Servo, so maybe they're also just trying to build up a partnership with Mozilla to help to take on those giants.
Re: Documenting the Web together
#166Guess they are going to band together to dethrone W3Schools :-) (only half kidding, that web site has has some serious staying power.) Related, when I was active in standards work (I learned just how badly that stuff was run) I discovered that new people in a standards group that was being formed would be lobbying to be the group Chairperson or Vice Chair. But the people who had been in standards bodies before were a…
W3School is very good to quickly look something up - short and always with a simple example.
MDN is very good for details and in general as reference.
Re: Documenting the Web together
#167Microsoft you are doing all the right thing to win the hearts of developers! Great! Thanks for all wise decisions
Re: Documenting the Web together
#168Déjà vu. Previously ( checks email …almost exactly 5 years ago?! Christ, it was a long time ago), the web powers that be announced they were going to collaborate on a new web docs wiki.[0] I don't think it went anywhere because, well, MDN already existed. I'm glad they finally just surrendered to MDN, even if it was many years late. [0] https://www.w3.org/2012/10/webplatform.html.en
"One of our guiding principles in developing Microsoft Edge is that end users should never have to worry about which sites work in which browsers. This philosophy—”the Web should just work for everyone“—led to our choice to target the “interoperable intersection” of web APIs in our browser engineering."
Many sites already don't work correctly in Edge, IE11 nor Firefox - it's too late, these are minor browsers, used by a smaller fraction of end users. End users on on smartphones use 95% a WebKit originated based browser aka Chrome/Safari. Chrome and Safari are bigger than the rest on desktop.
Sites in 2017 are tested against Chrome and Safari by web developers.
http://gs.statcounter.com/browser-market-share/desktop/world...
http://gs.statcounter.com/browser-market-share/mobile/worldw...
Re: Documenting the Web together
#169Déjà vu. Previously ( checks email …almost exactly 5 years ago?! Christ, it was a long time ago), the web powers that be announced they were going to collaborate on a new web docs wiki.[0] I don't think it went anywhere because, well, MDN already existed. I'm glad they finally just surrendered to MDN, even if it was many years late. [0] https://www.w3.org/2012/10/webplatform.html.en
"One of our guiding principles in developing Microsoft Edge is that end users should never have to worry about which sites work in which browsers. This philosophy—”the Web should just work for everyone“—led to our choice to target the “interoperable intersection” of web APIs in our browser engineering." Many sites already don't work correctly in Edge, IE11 nor Firefox - it's too late, these are minor browsers, used b…
Minor is very relative here, especially with regards to Firefox.
IMO anyone who only tests against Chrome and Safari is seriously wrong. The amount of features not supported by Firefox or Edge are relatively small and so basically everything except for a few special cases should just work everywhere.
Re: Documenting the Web together
#170Déjà vu. Previously ( checks email …almost exactly 5 years ago?! Christ, it was a long time ago), the web powers that be announced they were going to collaborate on a new web docs wiki.[0] I don't think it went anywhere because, well, MDN already existed. I'm glad they finally just surrendered to MDN, even if it was many years late. [0] https://www.w3.org/2012/10/webplatform.html.en
"One of our guiding principles in developing Microsoft Edge is that end users should never have to worry about which sites work in which browsers. This philosophy—”the Web should just work for everyone“—led to our choice to target the “interoperable intersection” of web APIs in our browser engineering." Many sites already don't work correctly in Edge, IE11 nor Firefox - it's too late, these are minor browsers, used b…
lol sure,
from analytics
chrome 38.17%
safari 20.30%
firefox 17.10%
ie 15.56%
edge 7.08%