3 ms·
> I use Phoenix only on projects where its real-time capabilities will be the protagonist. As a web user (not dev) I would say real-time (as in super fast?) sh
by bboygravity 4y ago
> I use Phoenix only on projects where its real-time capabilities will be the protagonist.
As a web user (not dev) I would say real-time (as in super fast?) should always be the protagonist?
To me that's the most important factor that makes the difference between nice and shtty website.
- spapas82 4y agoNot really. Real time is not the same as super-fast. You can be real time but super slow or super fast using traditional request/response web apps. When I mentioned real-time I was talking about apps that need to use web sockets to have fast client-server communication. There aren't many apps where this is required (or worth it).
- traverseda 4y agoReal time like a chat app, or a video game or something. Not just a fast site. Seems like most "real-time" sites are slower as they have a harder time taking advantage of caching and the like, or use a lot of slow client-side javascript that inevitably works poorly. Basically if you need the server to be able to change the data a user is currently looking at, collaborative multi-user stuff mostly. Liveview could be great if you're building google docs, but you could probably build youtube using just a more traditional framework like django.
- mixmastamyk 4y agoBeen looking at CRDTs lately for this, sounds like Elixir would be a good fit. Although what I've seen before has used C++ or Rust? to compile to wasm for the graphics part of the front end. Do all these technologies work together well?
- AlchemistCamp 4y agoPhoenix has used CDRTs going back to version 1.2 when Phoenix Presence was introduced. Here's a podcast about it (2016): https://changelog.com/podcast/208 https://changelog.com/podcast/208