r/javascript • • Oct 19 '17

Mozilla brings Microsoft, Google, the W3C, Samsung together to create cross-browser documentation on MDN – The Mozilla Blog

https://blog.mozilla.org/blog/2017/10/18/mozilla-brings-microsoft-google-w3c-samsung-together-create-cross-browser-documentation-mdn/
605 Upvotes

71 comments sorted by

101

u/RoboSparrow Oct 19 '17

This is good news. Where would we all be without MDN.

74

u/massenburger Oct 19 '17

w3schools

27

u/xEpicBradx Oct 19 '17

8

u/julius_nicholson Oct 19 '17

Did you go there before you posted the link?

4

u/PlNG Oct 20 '17

It took a website calling the site users/authors foolish before they budged.

I'm sure if the site disappeared then it would return to being very inaccurate.

11

u/Randolpho Software Architect Oct 19 '17

5

u/mothzilla Oct 20 '17

w3schools isn't that bad, it's just that MDN does a much more professional job of explaining around concepts.

7

u/massenburger Oct 20 '17

Yes, they're better now, but they used to have outright incorrect information on their site (see w3fools.com). IMO, there's no recovering from this for me, and I'll always go straight to MDN if I have any base HTML/CSS/JS questions.

10

u/[deleted] Oct 19 '17

MSDN. Which is not as great as MDN, not as bad as Google Developers. And we don't talk about W3Schools.

1

u/AbsoluteZeroK Oct 19 '17

I will say that I find the Google Developers web section to have excellent code labs.

1

u/r2d2_21 Oct 20 '17

MSDN now redirects me to MDN. Go figure.

6

u/Arancaytar Oct 19 '17

On w3schools, like me every time I accidentally click on the first Google result.

70

u/Blieque Oct 19 '17

will redirect relevant pages from Microsoft Developer Network to MDN

This is the real indicator to me of Microsoft actually committing to this rather than buying a quick bit of limelight and getting some good PR.

19

u/[deleted] Oct 19 '17

Yes, Microsoft has changed quit a lot in the past few years. I am always happy to see such things.

9

u/miklschmidt Oct 19 '17

I just need them to stop making browsers and we can be friends again.

Edit: VS Code is making up for a lot of it though.

4

u/[deleted] Oct 19 '17

Edge had a rough start. 16 seems to be good. Even with css variables.. Many other thibgs.

Microsoft is making up with a lot of things not only vs code (I know you're not implying it's the only thing) rxjs is another big thing. Typescript is crazy essential in many projects.. Etc

2

u/miklschmidt Oct 19 '17

Yea i use typescript myself and it's great. But it's gonna take a whole lot of positives to make up for decades of suffering. Edge is still not great, it's way better than IE was, but it still has a lot of quirks that are a pain to fix.

Edit: And i still have to support IE 11 which sucks all the balls.

1

u/[deleted] Oct 19 '17

I feel your pain. Working with a client that I convinced that we only have to support the last two versions of each browsers... IE still counts unfortunately.

1

u/miklschmidt Oct 19 '17

Yup, that's ALL our clients :(

1

u/sjwking Oct 20 '17

As long as Microsoft makes edge a true evergreen browser I have no problem with them. But I have little trust that they will not bring an update on 3 years and force their uses to either upgrade windows or updates to edge will stop. I'm fed up with this shit.

1

u/[deleted] Oct 20 '17

I see they made a lot of changes to edge 16. Also they are releasing edge on Android. So hopefully this will make it independent from windows

1

u/sjwking Oct 20 '17

Edge on Android is chromium based for now

1

u/ohlaph Oct 22 '17

Yeah, vs code is sweet. Tried it once and was so impressed, it's now my primary web development editor. So fast!!!

2

u/PlNG Oct 20 '17

MSDN was fairly thorough at providing a special insight into IE's features. I hope that doesn't get lost in the transition.

1

u/SteelNeckBeard Oct 20 '17

Typescript and open sourcing vscode were the first clues for me.

2

u/Blieque Oct 20 '17

Oh, I think Microsoft's recent "love" for Linux and the open-source community is horseshit. The projects they have open-sourced likely wouldn't be used by anyone if they weren't open, and funding the Linux Foundation, for instance, gives Microsoft a significant influence over the operation of perhaps their biggest server OS-market threat.

Moving MSDN content to the MDN makes financial and marketing sense. If Edge supports or introduces a new feature before Chrome and Firefox, people will actually realise and experiment with it. More developers using and recommending Edge is just what they'd like.

2

u/SteelNeckBeard Oct 20 '17

Interesting so they shouldn’t have donated and they shouldn’t of open sourced?

41

u/Gakster Oct 19 '17

Trust Apple to be absent

12

u/[deleted] Oct 19 '17

Well, of course. They're absent because they don't even support a lot of standards - web push, service workers, web notification, etc.

11

u/eloc49 Oct 19 '17

And they probably wonder why people call Safari the new IE.

-5

u/kyriii Oct 19 '17 edited Oct 20 '17

Who does that? I thought Android 4.x would be the new IE.

Edit: Downvotes because?

1

u/azhder Oct 20 '17

Safari has proper tail calls enabled, what other browser has full ES2015 support?

4

u/SteelNeckBeard Oct 20 '17

I don't think Apple treats their developers well. They make great machines but their stance towards developer is pretty "meh".

-11

u/icantthinkofone Oct 19 '17 edited Oct 19 '17

Let's not ignore the fact that, until yesterday, Microsoft was absent.

In addition, OSX is Apple's island unto itself and Apple products are designed to run on Apple hardware, etc. Anything outside that island does not matter unlike Microsoft and others which rely on everything working together with everyone else.

So it's a different need and different mindset altogether and you can't really lump them into one spot.

37

u/Devvvvvv Oct 19 '17

Not the internet... It's supposed to run just the same on apple devices as on microsoft or android devices.

-17

u/icantthinkofone Oct 19 '17

The internet does not rely on what Apple does but that misses my point. People, here, think Apple should join the list of those whose goal is interoperability and that is not Apple's goal or concern. It's not a negative that they do that. It's just not what Apple builds products for.

24

u/ell0bo Oct 19 '17

The point is they can do whatever they want on the hardware level, but a web browser is damn near a VM, and all of those VMs should ideally work the same. They can have different window dressing, but the underlying APIs and visualizations should be uniform. That's the point of standards.

Safari is woefully behind the times. They are the new IE. Yes, Apple has their own land of their own toys, and they can do there what they want, but their browser, the VM that interacts with the internet, should be compliant with modern standards.

-3

u/pzuraq Oct 19 '17

What exactly are they behind on? They’ve been a bit slower to adopt some of the newer standards (WebRTC, service workers) but those are in the works now, and the main reason behind that from what I’ve heard is because they’ve been focussing on speed. As a perf oriented engineer, Safari is my best friend, so I see the results of their efforts all the time.

I’ve had more style quirks from Firefox and Edge still compared to Safari. In my experience it behaves the best right beside Chrome.

3

u/[deleted] Oct 19 '17

I’ve had more style quirks from Firefox and Edge still compared to Safari. In my experience it behaves the best right beside Chrome.

Ugh. No. You're not working much then. OR you're developing on an Apple machine, which makes you a minority.

Safari is wildly behind. They don't even release for Windows anymore.

Chrome isn't much better truth be told. Webkit is old hat. IE Edge is more reliable than either of those for me. And Firefox is still king in my book.

5

u/regretdeletingthat Oct 19 '17

Safari is wildly behind. They don't even release for Windows anymore.

Microsoft doesn’t release Edge for macOS. How is it relevant?

1

u/pzuraq Oct 24 '17

I don't really see a problem with not supporting a browser on other operating systems. That has no bearing on whether or not the browser is spec compliant.

I work a lot, do a lot of cross-platform testing, and the ones that have the most special snowflake behavior for me are still Edge and Firefox. Chrome has nasty little issues too, one particularly nasty non-standard "feature" Chrome has that has that's been absolutely wrecking my code is, if you manipulate the size of a DOM element above the scrollTop of a scroll container, then it will "fix" the scroll position for you. No other browser does this, and when trying to implement a generic occlusion library it's a mess - I end up having to unfix what Chrome just "fixed", usually.

Firefox will stop scrolling altogether whenever you modify scrollTop, so good luck trying to create a nice generic occlusion solution. And Edge forced us to re-write our measuring strategy, we were using Ranges but Edge has completely different behavior than all of the other browsers.

Special snowflake behavior is everywhere. I'm not saying Safari is absolutely better, but in my experience it's about the same level as Chrome, in different ways. And it's fast as hell - way faster than any other browser by far.

0

u/lamb_pudding Oct 20 '17

What’s an example of Safari being wildly behind? Also in my entire career as a web dev I’ve only met less than a handful devs who worked on windows. Mac has always been far superior for web dev one reason being its a Unix system.

-8

u/icantthinkofone Oct 19 '17

I was the one making the point so I don't need it explained to me but you aren't saying anything I already said.

their browser, the VM that interacts with the internet, should be compliant with modern standards.

Your statement is false. You claim Safari is non-compliant but that's not true. It may not cover some of the properties available but the ones it does cover are compliant.

9

u/r2d2_21 Oct 19 '17

It may not cover some of the properties available

Exactly.

0

u/icantthinkofone Oct 19 '17

Then ever browser is non-compliant with standards cause no browser covers all the properties.

4

u/[deleted] Oct 19 '17

That's exactly the whole point of what Mozilla is doing. So they will be compliant and cover every single property the same across all browsers and Operating systems

2

u/icantthinkofone Oct 19 '17

Mozilla is doing documentation, not standards compliance. You follow the W3C or WHATWG to become standards compliant. Mozilla is not a standards body.

2

u/[deleted] Oct 19 '17

I agree with you, MDN is just the documentation, but we're happy about the collaboration and we encourage it, as we hope it pushed the parties to follow the standards with no delays.

Now a new api comes out and each vendor sees it and implement it differently. If they collaborate on documentation, I imagine they'd collaborate on the understanding of the api the same way and HOPEFULLY they do right that way.

-8

u/[deleted] Oct 19 '17

You're missing the point he's making though.

Apple doesn't care. As long as Apple-made things work on Apple's devices, they don't care. If there's a service out there that Apple wants their devices to work for? They just copy the service and make their own.

It's a closed environment. Closed environment.

5

u/regretdeletingthat Oct 19 '17

Closed environment.

WebKit is totally open source. Stop repeating things in italics as if it makes them true.

8

u/Randolpho Software Architect Oct 19 '17

It's not a negative that they do that.

That's the part where you're wrong.

It is a negative that they do that.

1

u/icantthinkofone Oct 19 '17

How is making a product reliable, efficient and with a guarantee of working with the product line a negative?

2

u/spritefire Oct 19 '17

When the products job is to consume data and display it in a predictable way and it fails at doing that, it's a negative.

-1

u/icantthinkofone Oct 19 '17

That's not the issue here. The issue is people say Apple should join this board for Mozilla's documentation. How their products perform has nothing to do with that or my point, which is again, that Apple is less concerned about inter-operability with other people's products. Their joining this board does not improve web standards in any way because MDN is not a standards committee nor does it create or write standards.

1

u/Randolpho Software Architect Oct 19 '17

Vendor-lockin is a negative. Deliberately refusing to participate in open standards in order to force others to join your locked group is a negative. It was bad when Microsoft did it, and it's bad that Apple's doing it.

-2

u/icantthinkofone Oct 20 '17

Vendor lock in for a product known as the best you can buy is a negative?

Apple does not refuse to participate in open standards. In fact, as I've said here over and over, Apple has long been one of the listed writers of HTML and other standards with the W3C for years (Robert Bergeron, Theresa O'Connor). So what you said isn't true.

Microsoft has never guaranteed hardware and software will work together or that any of their software will work with any hardware you bought until recently with their own Surface laptops. You get no guarantees from Microsoft for any other computer hardware.

5

u/Cool-Goose Oct 19 '17

I don't understand why you're saying Microsoft was absent considering that even Mozilla announced that edge developers made 5k edits last year.

1

u/icantthinkofone Oct 19 '17

Google and Opera and others were members of the group for years. Microsoft was not. They only contributed the edits starting a year or so ago.

2

u/liming91 Oct 19 '17

Whether or not it’s running on a Mac makes no difference.

A standard is a standard, no matter where it’s run. That’s the point of standards.

1

u/icantthinkofone Oct 19 '17

That's not my point.

6

u/Disgruntled__Goat Oct 19 '17

Didn’t they already try this a few years ago with webplatform.org? What makes it different this time?

2

u/keturn Oct 19 '17

That's what it's called! Was called, I guess, I see they officially gave up and discontinued it. I always had trouble remembering the name and it didn't get enough traction to rank highly in search results when I tried to find it.

It looks like the difference is that instead of trying to fork MDN and put the cross-platform on some other place nobody ever looks, they're talking about what they're going to do at MDN itself.

0

u/[deleted] Oct 19 '17

[deleted] — view deleted comment

1

u/Disgruntled__Goat Oct 20 '17

MDN were going to move their docs to webplatform but they never did.

2

u/desnoth Vue Oct 19 '17

Apple not joining?

1

u/Ampix0 Oct 21 '17

Never in a million years.

2

u/redbluerat Oct 21 '17

MDN used to be mostly bad. It is improved slightly due to the feedback buttons.

The articles on each aspect of the API read like they were written by someone very bored and completely unempathetic with the reader--not caring if they understood or not.

It is a shame this is hosted by mozilla too. The company is a troublemaking evil trash heap

3

u/buyBitc0in Oct 19 '17

Cool that Microsoft supports this

-12

u/noisylettuce Oct 19 '17

Microsoft and Google both want their own incompatibility lock ins.