liveviews VS axios

If you want to try the liveview approach but not ready to work with Elixir / Erlang / Beam runtime, you can use liveview in 17 popular languages (Java / C# / Javascript / Typescript / PHP / Python, e.t.c.).

https://github.com/liveviews/liveviews

Below are introduction directly quoted from this list:

> This is a list of libraries for creating web applications that handle user interaction with the DOM on the server. These libraries take a different approach from older server-driven browser UIs that simulated a desktop GUI toolkit. They do not lock the developer into working with predefined components; most operate at the level of HTML (DOM) rather than GUI widgets.

> The list strives to be complete rather than awesome. You may see libraries that are not maintained or ready for production.

This approach allows you to handle business logics on the server, and update the screen in browser from the server as well.

[1] https://github.com/liveviews/liveviews

That's a conflation. I'm certain for at least some, the choice is more about using a single language than avoiding JS. I'm sure there are people using htmx who use a JS backend. There are at least 5 LiveView clones for JS for instance: https://github.com/liveviews/liveviews#javascripttypescript

Nuxt, Next, SvelteKit, Phoenix(Elixr), Blazor, and various liveview-likes are popular full stack frameworks. So, although many devs are becoming specialized, there certainly still are full stack developers with demand enough to strongly support several frameworks.

The list is seeking a maintainer. https://github.com/liveviews/liveviews/issues/23

> "different" platform with it's own unique patterns and quirks

Everything OP listed was a criticism directed at LiveView, the 'Live App' functionality, not Phoenix, the web framework. Live Apps are not exclusive to Phoenix either, as there are now imitators for every other web framework now, which at least speaks to its broader appeal amongst developers. So the criticism could be leveled towards the far less mature 'Live App' libraries on PHP/Python/JS/C# and so on and on:

https://github.com/liveviews/liveviews

However there are two ways you can do this server side: 1. Use a tool similar to live view: https://github.com/dbohdan/liveviews

Typically, there are various ways to choose an HTTP client, and for this example, I've chosen axios.

axios: To fetch data from the Strapi CMS API and also to fetch responses from our Express server.

Note, you can use any library for HTTP requests like axios. This example uses the http and node-fetch libraries available on npm.

Interact with other APIs over an encrypted channel. For example, you can use Axios with Node.js.

For this article, I will be using the TypeScript Starter template as shown in the screenshot above. This comes with Nodejs, Cheerio, Axios

Axios is suitable for a wide range of web development projects, from simple single-page applications (SPAs) to complex, large-scale enterprise software.

Axios for streamlined API interactions, facilitating seamless data fetching.

Axios is a popular HTTP client library for Node.js that provides a more user-friendly and feature-rich way to make HTTP requests. Axios simplifies error handling and supports features like automatic JSON parsing and request/response interceptors, making it a great choice for many HTTP request scenarios.

For this tutorial, we’re going to scan the file for malware using Verisys Antivirus API, and so we’ll add a package to make it easier to make external HTTP requests. Popular choices include Axios and node-fetch - for this article, we’ll use node-fetch

In the dynamic realm of JavaScript and front-end development, selecting the appropriate tool for HTTP requests is critical. Axios and Fetch stand out as two leading contenders, each offering distinct features and benefits. This article delves into their differences and practical applications, providing a comprehensive comparison.