5 ms·
Honestly, 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 br
by Kwantuum 7y ago
Honestly, 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.