When we enter the world of computing, there are so many packages, options and paths to follow that it is normal to feel a little lost. For example, when we are making HTTP requests, which way should we go? In this post, I will cover the Axios libra...
Markdown supported · ⌘↵ to post
Very interesting article, my friend and I just were just debating about that recently and as I can see we made the right decision to go with axios ;)
Great article.
I've used both for various projects. Your insights confirm a lot of the things that I've been thinking about.
I think you are comparing two different things here. Axios is a library while Fetch is a native function on modern browsers. It will always be performant to use native functions but a library will always be easier to use due to its abstractions.
I think it would be better if you will be comparing Axios vs another library that abstracts HTTP Calls, or comparing Fetch vs XHTTP.
Good story though.
I can say for a fact that it's finally good to know the reasons behind using one over another. In my case, I just went with using Fetch because Axios seemed really hard for me to grasp.
Interesting article Luísa Ribeiro Bezerra.
Thank you so much for this article, it is exactly what I needed. I am definitely copying you, and trying Axios. An excellent review for beginners :)
Julio Polo
Transform Coffee on un debugable code
Great article Luisa, my only concern about Axios is that some time ago I read that it wasn't being maintained which could be problematic. But it's a cool and tested library.