phoenix_live_view VS Socket.io

Then there are stack-specific libraries: StimulusReflex for Rails, Phoenix LiveView, Laravel Livewire, Unicorn and Tetra for Django, Blazor for .NET, … and the list goes on.

I came across this pretty interesting library on Hacker News that tries to implement LiveView on the JVM. Link to GitHub.

Hi everyone, I just launched Podsee(https://pods.ee) for podcast listeners, lovers. You can search and listen to podcasts at Podsee. What makes it different is that you can get the AI transcript for an episode.

It started as a side project after I resigned my job one year ago. As a programmer, I love Elixir (http://elixir-lang.org/) and Phoenix LiveView(https://github.com/phoenixframework/phoenix_live_view), and want to make a product with it. So I build Podsee.

I'm planning to add more AI features to it, like summarize the episode audio, episode to comics, etc.

I'd love to invite you all to try out the product and would appreciate hearing your feedback! Thanks!

"HTML over the wire" generally refers to tech like [0] Liveview, [1] Hotwire, [2] LiveView, [3] Blazor, etc. They aren't about about ditching JS and more about not writing your HTML in JS (and yes, SSR).

[0] https://github.com/phoenixframework/phoenix_live_view

* https://github.com/phoenixframework/phoenix_live_view

Some of the 1.7 stuff has an alert banner that pops up when the connection is broken. I think that could really help.

However I haven't put that in our app as I have seen other issues of flakey connection reconnect issues, and I would hate to make any of those more visible with a flashing notice.

- https://github.com/phoenixframework/phoenix_live_view/issues...

HEEx template language was created, an extension to EEx

Also to your point, the latest LiveView release moved some helper utilities around and you need to add "import Phoenix.Component" in places. I could be wrong but I think the latest live code gen still isn't setting up correct imports. More info here: https://github.com/phoenixframework/phoenix_live_view/blob/master/CHANGELOG.md

If you need any kind of interactivity on the frontend, but are more comfortable with the backend, I would suggest looking at Phoenix LiveView [0] or a similar server-rendered HTML technology for your language of your choice [1].

In short, these solutions take JavaScript out of the mix entirely and basically let you deal with a single logical "app", rather than a separate frontend & backend.

[0] https://github.com/phoenixframework/phoenix_live_view

It uses JS though, as it is required to open a WS connection and change content without refreshing the page, but that looks like it is abstracted from the user. https://github.com/phoenixframework/phoenix_live_view/tree/master/priv/static

Before diving into this tutorial, if you find microservices mysterious, check out my previous article for a detailed explanation. In this hands-on tutorial, we'll build a real-time chat server using Node.js, Socket.io, RabbitMQ, and Docker. Get ready for a practical journey into the world of microservices! Let's begin.

Socket.io Docs

Now we will be implementing socket logic using socket.io for building websockets. This library provides an abstraction layer on top of WebSockets, simplifying the process of creating real-time applications. For better maintainability, it is recommended to create a separate file for socket calls. To do this, navigate to the src folder, create a folder named services, and inside it, create a file named socket.ts under the services folder.

Hi I made a chat app using socket.io it worked fine locally but when i deployed the app on render.com socket is not working properly i have to refresh the page to see new messages please help...

No, not a library. More like, the frontend and backend just happen to need the same version to be compatible (socket.io is a good example, moment.js was the most basic I could think of).

For apps that require real-time communication, Socket.IO can be a valuable addition. It enables bidirectional, event-based communication between the server and client, making it an ideal choice for implementing real-time chat features.

Community stats: Socket.IO has a community with 59.2k stars and 10.2k forks on GitHub.

Socket.IO is a NodeJS framework built on top of WebSockets that enables realtime client-server communication. Socket.IO is event-driven and compatible with older browsers and environments.

I'm glad to announce the version 0.7.0 of my library socketioxide! It is a socket.io server implementation working as a tower layer/service. Therefore it integrates with any hyper based http framework like salvo, axum, warp or hyper itself.

Check the quickstart of Socket.io. Support Socket.io on GitHub ⭐