I'm sorry but that's not what liveview is. You need to do more research before posting an informational video. LiveView is a newer concept where the server will send DOM patches to the client over WebSocket to update elements of the page without the entire page reloading and no need for JavaScript to call an API to get data and update the DOM. The development advantage of LiveView is that the developer doesn't need to write any JS code at all to make their page interactive, it's all done in elixir with HEEx templated that are smart enough to know what small portion of html changed and needs to be replaced on yhe client. It's more similar to HTMX than anything. Live updates to the page while developing is a much older feature that most frameworks support, even outside the Elixir world. Most JS frameworks do that too, it's nothing special.
Also in Phoenix you can simulate SPA's pagination, you dont need to have two states, one in the server an another in the client, Idk, but I think liveviews are some powerful
@@AxelRizo-py4tb there are probably 100s of JS frameworks out there now to do this, and I would recommend using them with LiveView. LiveView is intended to make things easier, as you said, to have state managed entirely on the server and not on the client at all. If you want to use a JS framework, then you can make an elixir API backend for http request from the front-end. But I really recommend giving LiveView a shot! It's very fast to have all development done in one language on the server side. I recommend using Tailwind CSS to style your webpage since you won't have access to a UI framework that might come out of the box with something like Next. I made a project recently in Elixir, Phoenix LiveView, HTML and Tailwind CSS. It was great having such a simple tech stack that was so powerful and made it quick for me to develop my app.
@@legendragsNo the opposite xD Elixir is only useful for distributed systems but so is Rust and Go too. There is literally no reason to use elixir over the other ones. Elixir is even way slower, the other ones are more general purpose and so on. The syntax of elixir is cryptic too, so I dont see a big adoption for it
@@ITSecNEO only a sociopath would use rust instead of elixir for a crud web server, and it is way better than some alternatives like django if you're looking for performance.
@@MalachiRails liveview renders HTML that updates dynamically over WebSockets. Only the block of HTML that needs updates will be replaced with new. Making it look like a SPA.
Bro your content is quite good but can you start making some real youtube courses teaching some concepts from ruby on rails or the Phoenix framework instead of creating these bite sized videos. Still love your content though but we need some good courses.
Phoenix is pretty good. But being only 2x faster than Express is not something I like. (That means it is slower than Fastify) And Fastify is not a fast framework, I can easily make a faster one. The thing that I care first is performance, because it affects the app once you start scaling up (That's why I hate middlewares and I don't want people to implement that). And we can't just say that hardwares are 'fast' so our program is fast enough.
@@anasssanba-k5h That's just me I will choose a framework if it has decent performance (5x Express). I don't really care about DX cuz that thing doesn't really matter for end users (But I do for my framework). I care about performance because I don't want to have scaling issues and performance problems mainly. I know it will not be the first problem but I will always treat it like it's the first problem.
I'm sorry but that's not what liveview is. You need to do more research before posting an informational video.
LiveView is a newer concept where the server will send DOM patches to the client over WebSocket to update elements of the page without the entire page reloading and no need for JavaScript to call an API to get data and update the DOM. The development advantage of LiveView is that the developer doesn't need to write any JS code at all to make their page interactive, it's all done in elixir with HEEx templated that are smart enough to know what small portion of html changed and needs to be replaced on yhe client. It's more similar to HTMX than anything.
Live updates to the page while developing is a much older feature that most frameworks support, even outside the Elixir world. Most JS frameworks do that too, it's nothing special.
Also in Phoenix you can simulate SPA's pagination, you dont need to have two states, one in the server an another in the client, Idk, but I think liveviews are some powerful
And also, can you name the js framework that can do updated via websockets, pls, i dont know any, Next use http request, isnt?
I came for this comment
@@AxelRizo-py4tb there are probably 100s of JS frameworks out there now to do this, and I would recommend using them with LiveView. LiveView is intended to make things easier, as you said, to have state managed entirely on the server and not on the client at all. If you want to use a JS framework, then you can make an elixir API backend for http request from the front-end.
But I really recommend giving LiveView a shot! It's very fast to have all development done in one language on the server side. I recommend using Tailwind CSS to style your webpage since you won't have access to a UI framework that might come out of the box with something like Next. I made a project recently in Elixir, Phoenix LiveView, HTML and Tailwind CSS. It was great having such a simple tech stack that was so powerful and made it quick for me to develop my app.
who the fuck is "everyone"?
smart people
@@legendragsNo the opposite xD Elixir is only useful for distributed systems but so is Rust and Go too. There is literally no reason to use elixir over the other ones. Elixir is even way slower, the other ones are more general purpose and so on. The syntax of elixir is cryptic too, so I dont see a big adoption for it
@@ITSecNEO only a sociopath would use rust instead of elixir for a crud web server, and it is way better than some alternatives like django if you're looking for performance.
everyone is a curios cats who click on this clickbait title
If its everyone then is isaac newton too?
Can phoenix split the project in apps like Django does?
That's not what liveview mean. You described Hot reload.
What is live view
@@MalachiRails liveview renders HTML that updates dynamically over WebSockets. Only the block of HTML that needs updates will be replaced with new. Making it look like a SPA.
Bro your content is quite good but can you start making some real youtube courses teaching some concepts from ruby on rails or the Phoenix framework instead of creating these bite sized videos. Still love your content though but we need some good courses.
I will try my best
Mmm yeah.. everyone
Lol
solid vid
Thx
Stupid ad with nothing but marketing slogans.
He's literally uttering bs from chat gpt
Phoenix is pretty good.
But being only 2x faster than Express is not something I like. (That means it is slower than Fastify)
And Fastify is not a fast framework, I can easily make a faster one.
The thing that I care first is performance, because it affects the app once you start scaling up (That's why I hate middlewares and I don't want people to implement that).
And we can't just say that hardwares are 'fast' so our program is fast enough.
Phoenix is faster than any JavaScript framework out there
this is just bs , unless you put it into action
@@anasssanba-k5h That's just me
I will choose a framework if it has decent performance (5x Express).
I don't really care about DX cuz that thing doesn't really matter for end users (But I do for my framework).
I care about performance because I don't want to have scaling issues and performance problems mainly. I know it will not be the first problem but I will always treat it like it's the first problem.
i would use rust if performance is what i care about.
@@hxxzxtf i don't care about rust
I use Zig