3 ms·
I agree! The MDN docs are from my experience the best browser frontend reference available. This site however covers a different need: guide/howto oriented do
by dgb23 7y ago
I agree!
The MDN docs are from my experience the best browser frontend reference available.
This site however covers a different need: guide/howto oriented documentation, which is often what you want.
> Doing & Learning things in plain JS we can learn fundamentals.
To this I have to add that I often do write plain JS supported by only a few, small libraries such as is.js, axios, json-schema and so on. This is regarding small to medium sized projects and/or features.
This can easily save time, setup and mental energy, as long as one follows a consistent, simple structure. And on top of that, the fewer dependencies you have, the less friction.
But it also means that one has to have a bit of a deeper knowledge of the available frameworks and tools, which can manage complexity with growing features, because you add them incrementally and only when needed and so on.
- Kwantuum 7y agoHonestly, while axios is nice to have on the server side, the websocket API in the browser is very simple to use. Which IMO is a consistent theme with modern browser APIs.
- girvo 7y agoAgreed: on our current front end project at work I’m having a lot of fun teaching the team the amazing browser APIs that subsume the need for a lot of the third party dependencies we used to reach for
- orange8 7y agoHow do you deal with IE 11?
- IggleSniggle 7y agoMany of us do not need to deal with IE. I haven't even needed to deal with mobile in years. Depends on requirements and use case.
- orange8 7y agoAgreed. But the reason I asked because I am assuming they are making changes to a long-standing project that previously relied on third-party libraries (for browser compat?). I'm interested in that specific situation, not all projects in general.
- girvo 7y agoIn this project, simple: we don't have to. Despite being a decade old application, it was entirely AJAX-driven and front-end focused even back in 2010, and IE support was dropped entirely a few years ago by the business. Works in Edge just fine, as to be expected
- orange8 7y agoMakes sense. I think the two options are just dropping IE support entirely or using (usually third-party) polyfills.
- duxup 7y agoMDN is great as if you're reading the manual with all the details and etc. But like a lot of raw manuals sometimes you read it and wonder "Wait.. why would I want to do this again? Does this even do the thing I started looking for?" Some of their examples have actually evolved to be a bit more akin to more usage based rather than raw specs. I do appreciate the other sites that are more "You want to..." as a complement to MDN and such.