Highland.js vs axios: What are the differences?

# Introduction
Here, we will discuss the key differences between Highland.js and axios.

1. **Concurrency Handling**: Highland.js provides built-in support for handling concurrency through its streams, making it easier to manage asynchronous operations. On the other hand, axios does not have native support for concurrency handling, requiring manual implementation or the use of additional libraries.
2. **Functional Programming**: Highland.js is a functional programming library that allows users to build complex pipelines for data processing through functional composition. In contrast, axios is primarily a library for making HTTP requests and does not offer the same level of support for functional programming paradigms.
3. **Error Handling**: Highland.js emphasizes handling errors within streams by providing methods like `errors` and `stopOnError`, allowing developers to manage errors more efficiently. Meanwhile, axios provides basic error handling through promise rejection but may require additional code for more advanced error management.
4. **Browser Support**: axios is primarily designed for browser environments, providing features like automatic JSON parsing and support for progress events. Conversely, Highland.js is more focused on server-side applications and may not have the same level of browser compatibility.
5. **Stream Processing**: Highland.js is centered around the concept of streams and offers extensive support for processing and transforming data in a stream-based manner. In contrast, axios is focused on making HTTP requests and handling responses in a more traditional request-response paradigm.
6. **Library Size**: Highland.js is a lightweight library with minimal dependencies, making it suitable for projects where minimizing package size is important. On the other hand, axios has a larger footprint due to its comprehensive feature set and compatibility with various environments.

In Summary, Highland.js and axios differ in terms of concurrency handling, functional programming support, error handling, browser compatibility, stream processing, and library size.