Omg I cannot explain how much better this looks, another HUGE win for elixir, great video Daniel, keep up the amazing work! As a brazilian I must say... Salveeeeee 😂
Hey Daniel, could you make a video exploring this theme in general? not only in liveview? I would like to know your opinion about the CSR tools outside the JS ecossystem, the majority of well stabilished frameworks have their own (Laravel: Livewire, Phoenix: LiveView, Ruby On Rails: Hotwire etc). Do you think these are really a option for developers or, because of the enterprises we will still need to use the classic SPA with back-end APIs? I'm kinda reluctant about using Livewire in my projects, principally because in Laravel, when you create a component, you have 2 different files, one for front-end and rendering the generalist data, and other for the script that the component needs to use. It works at all, but... Seriously? 2 files? all JS frameworks and libs have it mixed in 1 specific file, common, this 2 file thing just increses complexity in code (wich in general tends to be gigantic). Anyway, I thin this was more a rant then a request kkkkk But please, I think these "philosophical" are really interesting.
So do you create your frontends exclusively with LiveView only? Would also like to know what about React? Do you not use it at all anymore? Or do you create your frontend in React and backend in Phoenix?
At work I use Phoenix on the backend and React on the frontend. But on my side projects I like to go full Elixir + Phoenix + LiveView, because it simplifies my tech stack a lot
@@DanielBergholz Also, please consider making a video on how does one go about landing a professional dev role in the Elixir-Phoenix (+React) tech stack! Thanks!
if one reacted to every complain... For one there would be no backward compatibility. I would rather deal with 'ugly' code and have stable environment I can rely on and easily update it in say 5 years than develop software that requires a whole team of people dedicated to tracking changes and maintenance/upgrades. And, this could only work for SaaS kind of applications. If you sell you product for real (Your customers run it on site), you can forget about it. Then you have software notorious for being out of date and full of security bugs that never get patched.
man, 2025 I'm gonna learn it the only reason I dont do it now is because I have too much on my plate i already know some lua and a little bit of elixir, what is missing for a full brazilian stack?
Omg I cannot explain how much better this looks, another HUGE win for elixir, great video Daniel, keep up the amazing work!
As a brazilian I must say... Salveeeeee 😂
@@Redyf tamo junto 👊
pls a komprehensive video about the hanges🙏
Hey Daniel, could you make a video exploring this theme in general? not only in liveview? I would like to know your opinion about the CSR tools outside the JS ecossystem, the majority of well stabilished frameworks have their own (Laravel: Livewire, Phoenix: LiveView, Ruby On Rails: Hotwire etc). Do you think these are really a option for developers or, because of the enterprises we will still need to use the classic SPA with back-end APIs?
I'm kinda reluctant about using Livewire in my projects, principally because in Laravel, when you create a component, you have 2 different files, one for front-end and rendering the generalist data, and other for the script that the component needs to use. It works at all, but... Seriously? 2 files? all JS frameworks and libs have it mixed in 1 specific file, common, this 2 file thing just increses complexity in code (wich in general tends to be gigantic).
Anyway, I thin this was more a rant then a request kkkkk But please, I think these "philosophical" are really interesting.
So do you create your frontends exclusively with LiveView only?
Would also like to know what about React? Do you not use it at all anymore?
Or do you create your frontend in React and backend in Phoenix?
At work I use Phoenix on the backend and React on the frontend. But on my side projects I like to go full Elixir + Phoenix + LiveView, because it simplifies my tech stack a lot
@@DanielBergholz Also, please consider making a video on how does one go about landing a professional dev role in the Elixir-Phoenix (+React) tech stack! Thanks!
if one reacted to every complain... For one there would be no backward compatibility. I would rather deal with 'ugly' code and have stable environment I can rely on and easily update it in say 5 years than develop software that requires a whole team of people dedicated to tracking changes and maintenance/upgrades. And, this could only work for SaaS kind of applications. If you sell you product for real (Your customers run it on site), you can forget about it. Then you have software notorious for being out of date and full of security bugs that never get patched.
Historically speaking, Elixir has been fantastic at listening to feedback from the community, and keeping backward compatibility
YEEEEEEEEX!
man, 2025 I'm gonna learn it
the only reason I dont do it now is because I have too much on my plate
i already know some lua and a little bit of elixir, what is missing for a full brazilian stack?
@@esquilo_atomico you’re only missing the Portugol programming language 👌
Holy HEEX!
the whole language syntax is ugly. what is