That is much better than what i ve to write in vue to reset the form. But what about nested models/arrays? Does this keep the model structure? Seems i should test it from start
I have tried Vue and Flutter as the front end and Laravel API as a backend. It worked but in the long run I think I will not be able to keep up with all those different technologies. So I will go back to just Laravel with Blade. I will give Livewire and alpine.js a try though as an in-between-solution
Hei, very nice examples. I do get the point of livewire and it looks good, but .. imagine you have form with 10 fields, do I understand correctly that livewire would do 10 api calls just for 1 update? So if 100 people update form at the same time it is almost as if 1000 request was done. I can not see the benefit of that. Can you explain that more in detail? Maybe I just do not understand it
I've been wanting to use Livewire since before version 2 came out, but I need to start a new project using just that, and that's not happening until I'm done with the project I'm working on right now. Thanks for the video, as always very informative. -Khalid
too much requests to backend , its good for small projects , but not good idea for the developers who caring about perphormance and laravel structure , with livewire you dont follow laravel structure for requests and controllers
@@YourAwesomePlace Then you lose some goodies like realtime form validations. And what about the fact it recieves a full html of component instead of json responses like react or vue?
my only conern about the livewire is it sends more requests on the server .I know it can be handled by debounce/lazy but again it's sending more request then vue.js
@@nkrumah2000 Then you lose some goodies like realtime form validations. And what about the fact it recieves a full html of component instead of json responses like react or vue? That results in larger response sizes.
My team at work had to choose a new front-end framework last week because we wanted to get rid of jQuery. We picked Livewire over Vue.js because we are all PHPers not really skilled in JS.
I work with livewire, very simple, clean an productive. But... The mess arrive when you want to embed some other library as ckeditor, tinyMCe, select2 etc.. and nested livewire component. As for now for me it doesn't work !!!
@@dogwalkinginc6371 For example, i can not make working leaflet map library as i want. i have a step by step form make with livewire at the first load on the first step all is good the map is created and displayed by leafleft, then if i go forward to the second step then backward on the first step , the map dissapeared and can not be recreated again. I known is not for all a livewire problem. But more generally for me the difficulty is that livewire reload all the dom for the concerned compoment and destroy content generated by other libraries and sometimes not easy to make all the pieces dance together.
@@BernardBAILLY I just watched this screencast(laravel-livewire.com/screencasts/s4-rich-text) and walked through everything and have trix rich editor up and running perfectly. Caleb explains what you need in order to make javascript not conflict w/ Livewire.
Great video! I would like to see you do a Laravel Nova and custom admin templating. For example I always find it difficult to make the admin panel my own with out all the quirks in Nova and the docs can be a be unclear at many key moments leaving you clicking back and forth through the docs trying to find he missing step.
I'm not planning to make reviews or customizations about PAID products, because it would be useful for only small amount of my audience who purchased that product. Nova included.
Povilas Korop ok I can see your point and understand , it was just a suggestion as no one seem to be doing this type of video. I can’t even find it on paid learning coding platforms but Laravel seem to be pulling it a lot still hence why I suggested it. Anyway keep up the good work I enjoying your video content that you are creating. 😎👍🏻
@@markbarton6845 To be honest, I've read quite a lot of similar comments about Nova, that it's hard to customize, so personally, I wouldn't recommend it as a solution. Of course, I'm biased as a QuickAdminPanel creator :)
David Basil sometimes it about time and budget. Nova is very good on small projects. It gives enough out of the box to get you about 90% of the way in not much time at all. For this I found it to be very good. However when you want to be more bespoke about your admin styling the grey areas of the documentation leave you in a guessing game. I put this down to me not understanding aspect of the docs and how to apply them rather than pointing my figure at the package.
Livewire is great, ive not actually used it myself, but i have watched a few introduction videos, and with me not really getting into the front end jscript frameworks, this will make it a lot easier for me to bring the front end into 2020
I'm giving a try on livewire on my new project. I was using vue for reactivity on my website. But when I go through the documentation of livewire I feel like I wont regret using it.
I was skeptical at first (and also annoyed) when I saw that 8 shipped w/ Jetstream/Livewire. But I decided to dig-in and try it, and so far I've been nothing but impressed. It's one thing to shout about theories of its poor performance. it's another to actually use it first hand and judge with facts.
it's just like the ASP .net tech in the olden days, heavily couple the view and backend together, very little flexibility on the frontend, good for people who have zero knowledge on frontend/JS
I think a popular misunderstanding is that Livewire is a potential replacement for Vue. It is not. It delivers reactivity in a beautiful way, yes, but it does not provide for managing loops and DB calls. That still is undertaken within Laravel. A major benefit perhaps?
@@impulserr It is great for reactivity and substituting for Ajax. Go and watch the author of Livewire on his website. Caleb's own video tutorials state that this is not a replacement for Javascript or Vue or JQuery for that matter.
Thank you for this video. If I want to do simple I will go for easy and looks like livewire is easy to implement. But this Vue Livewire jQuery and others stufs depends our needs. I'm using jQuery for little things sometimes. If I want to more complex structer I'm not using jQuery. Because thats really hard to code and manage. If I want to more complex app I will use Vue or similar. Depends our needs I guess.
Livewire is very interested, but i think is not matute enought yet. I was using it in a production project and things where broke when updating livewire versión. Also if your not carefully you may end up with too much ajax requests
Wow as a back-end software developer this really does sound interesting. I can't think of how many times you have to work with javascript to make something reactive. I will definitely do more research, and I am looking forward to more videos about this stuff!
Me too, i was very interested in this new library that stays on the backend and not worry too much about JS. Im in the process of rebuilding a CMS with Livewire and then Inertia.js, just want to see which side is more efficient because both are server side with the only exception that Inertia uses Vue, React or Svelte but only for the views, the rest is all Laravel backend which passes the data to the views. Im planning of releasing both of these CMS'es as public git repositories which some might find useful.
Great comparison, thank you! But there is a fifth way you could test. Basically progressively enhancing the "web" version, using htmx (successor of intercooler) or for an even more impressive "no code needed" option, unpoly : unpoly.com/ Quick howto with unpoly: - Read unpoly.com/form-up-target - For a quick test add unpoly to your project using a CDN unpoly.com/install/cdn - Add some class to the .card that contains the first sample something like - Update the of this sample to be like : And voilà, same reactivity as the other examples without altering your code, and works with and without javascript enabled in the browser. Easy-est to write and maitain. If you want I create a pull request for that on the repository. Unpoly is the unpopular hidden gem you might like to discover. It has been written to make long term, maintainable web applications. I'm not affiliated with it, I'm just a huge fan :-)
I started to use livewire, I think it's a great tool but there are some certain limitations which I am still discovering. Like not being able to store a collection as a public property or to render different views with data. I think and would love to see a video on all these limitations and how to overcome them.
Stay tuned, more changes are coming, the creator of Livewire Caleb will certainly expand this to more possibilities, the v2 already had many improvements, and who knows it may even be part of core Laravel because Taylor also loves this library, and Caleb loves to solve impossible problems, thats what drives him to create these awesome libraries
Psst! Wanna know about something better? Try Phoenix LiveView. LiveWire was actually inspired by it in the first place, and it uses websockets instead of AJAX, so it is a lot faster. But to be fair, if someone already knows PHP/Laravel then stick to LiveView, but if one wants to learn Elixir, a new functional language that powers Phoenix and LiveView, then give it a try. I'm using both frameworks/languages on different projects nowadays. It's faster than Node.js too if you are curious.
Need suggestion. I am not familiar with vue at all. I have used jquery all the time. Now I want to start working in vue or livewire. Which one should I go for?
It's a philosophical question, to be honest. What are you MORE COMFORTABLE with? If you are happy with Vue, you don't need Livewire. But if it feels that Vue is too much work for you, Livewire can make SOME stuff much easier. In my opinion, Livewire is mostly for those back-end developers who haven't really started much with Vue because they don't like JS, and with Livewire they don't need to write JS anymore at all.
@@PovilasKorop And also Vue is a more transferable skill. We can only use Livewire with Laravel but if we work on other frameworks we can still use Vue
It sends way more requests than vue or react. Another downside is that it has to download a full html page in response and then diff the changes while other js frameworks just get json responses. Way more requests and bigger response size. I personally haven't used livewire so I'm not sure if it handles client side validations and routing. It definitely has its place for small projects. But for bigger projects, it abstracts away a lot of necessary control.
In general it looks awesome, but this not good because it handle all js underneath the hood for someone intreseted to write his logic with it's requrement i don't think it would be a good choise otherwise it's really awesome
Yes that "hidden magic" of JavaScript is what also scares me, that's why, in my opinion, Livewire is good for some small components, like this form, but not for something that would potentially require custom logic.
@@josephmakram4342 I also think it can be used for blog or simplistic crud projects but it has a easier learning curve . But I believe we can learn both
First i gave up with nuxt. At first it was wow, vue with ssr. Later i've lost so much time installing plugins, tons of npms... now vue is at the same stage. Small projects but to the end i have hundreds of files and i dont remember what ive done 2 weeks before. Great things of vue die while data transfering back and forth to server. Data transformations, array loopings, mapings etc in order to pass it to new superhandymobilefriendly vue-component. Last days i want videos on livewire. If it is ready to simplify data transfers... the only trouble - while you learn livewire, there will be laravel 9 with supernewawesome verylivewwire and from the very beginning) sorry for emotions. Crying when look my first site with flash buttons written in notepad. Index.txt save as .html. later php. And basic txt editor was enough to build anything....
@@akashthoriya Yes, that collection API resources are part of my course. Also, I'm not sure what can I make a tutorial about, if the documentation is pretty clear on that topic.
imho the vue is more useful because may be some day you will work with javascript + vue, and its very popilar so its a plus for your cv. Also its more easy to person who is more familiar with javascript it self. But if some one is more backed php guy, probably they will stick with jQuery and livewhire
@@Tux0xFF livewire is great for a local project, but for a project with multiple access and a not so great server the ajax request for reactivity is terrible. They want you to use alpine to make things client side and... Well... It's not so good. Plus, livewire is just for laravel, if you someday need to use laravel as API or use another framework it can hit you hard, so it's good to learn and use vue/react/angular nowadays
personally I don't like livewire because it will request all the changes to the server. if your traffic is not very high then it will make sense to use it but if your site is a high traffic site, it will burden the server surely
I don't see reason to use livewire in real app. If you don't know any js then using livewire won't teach you anything, in other hand if you know, there is no reason to use livewire.
Isnt faster than building a SPA? where you have to deal with creating an API, then Auth if its needed. Livewire is reactive. There is also another adapter called Inertia which cuts a lot of bs that involves building an SPA, which is flawed because you have to work so much more , unless it serves mobile, web and other services then its ok, but for a website, a CMS, a CRM where most of the time SEO is important and everyone knows that SPAs built in the classical way have always had that problem, its been years already and the problem remains, there hacky workarounds for it but its just doesnt feel right.
weird to find actual web developers trying to avoid javascript. stop fighting the inevitable. be more efficient livewire is inefficient without learning whats going on behind the scenes and putting in extra work to improve it
Try upload multiple big videos using Livewire, and see how it works No client side preview (BEFORE UPLOAD): createObjectURL + video n canvas element, which is really easy and faster But the fact is Livewire "instantly" upload selected files whenever input files is changing Example case I want to upload a video with size +-200MB, with my smartphone, currently in that moment, my phone connection is not really good So what happen next? i have to "idle" in the upload form / page for few minutes (since my connection is bad) just to see what I have uploaded ($f->temporaryUrl()), this is not a good UX, then, if I want to change the video (Cancel the previous video), then again, I have to wait again for few minutes for simple preview?????? Really??????? Nope nope and nope, just nope I knew they provide JS function for manual upload, but still, nope and thank you, I'm sticking to Laravel n Vue
Thanks for pointing this, I have the feeling that it would be limited or could have some issues because it just looks a "cool" tool that isn't really well-thought. I will save my time from learning it.
@@ivantan222 for small project its good, but in large scale app, no, IT IS NOT My advice is, for long-term website development, you should use something that has wide range community support, so in the future, you don't have to change many things for your future requirement, Vue is already easy to learn, its not gonna hurt to learn it, there are tons of plugins for Vuejs framework
@Gwein Lotusiana Yeah, I agree. Moreover, I often find a project that looks easy at the start, so we might be interested in a simple tool like this Livewire, but when the project goes bigger it will be much more complicated if the tool can't support or becomes the technical barrier.
@@ivantan222 indeed For me, if I ever need to update my features, etc, I don't have to "entirely" change everything, and go through learn process, trial, and error all over again That's why I choose to stick with Vue And another example, for Laravel Eloquent If ur model record is still below 50k - 100k records, it is still good using eloquent But when you reach > 200k records, you should start using Laravel Query Builder 1. stackoverflow.com/questions/58314420/laravel-eloquent-vs-query-builder-pros-and-cons 2. medium.com/@abad.developer/laravel-eloquent-vs-query-builder-why-use-eloquent-to-decrease-performance-5aa17bed358a 3. (PDF) www.google.com/url?sa=t&source=web&rct=j&url=www.diva-portal.org/smash/get/diva2:1014983/FULLTEXT02&ved=2ahUKEwi0vPzvyYjsAhXJAnIKHXKLCVcQFjAOegQIARAB&usg=AOvVaw3Dz7Dk8x6LzIOFbzvp8zhW&cshid=1601183897129
Blade was just enough functionality at the backend. Livewire doesn't have any future, especially with introduction of much simpler and efficient jQuery alternative (Vuejs) for years to come.
Livewire sucks. a developer who locks on one stack will never be better than a developer who learns new things. vue expands consciousness, while livewire looks like a crutch for those who have not mastered vue
You make the assumption that Vue is the best alternative. And then presumably whatever JS framework supersedes Vue in the next few weeks/months will become the new best alternative and so on and so on. Personally I'm still on the fence with Livewire, but I welcome the option to remain within one stack. It's a "jack of all trades" vs "master of one" situation. But a "better developer" to me is one who gets the job done quicker, cleaner and simpler - not just one who knows more ways to skin a cat.
You couldnt be more wrong adminko. Why are you even here in a Laravel channel? Its like someone from the Laravel side comes to a Vue channel and talks shit about why are you using this small library for backend , it is a crutch. Laravel is a whole ecosystem, is a fullstack framework, no other framework achieved what Laravel did, JS is just a helper for Laravel, its a la carte menu to enhance some parts of it, do you think the world revolves around SPAs? Are CMS's, CRMs, ecommerce, and web applications in general all built with Vue or any other JS framework? Each tech stack have its own uses, only hipsters put JS frameworks on everything, even in their salads and their laundry detergent. What happened to the Deno hype? where did the hipsters go?
![From Laravel Blade to Vue.js + API [Live-coding Example]](http://i.ytimg.com/vi/4uVNz9sQn18/mqdefault.jpg)
to clear the variables, there is a method reset. it works like this:
$this->reset(['name', 'email', 'question', 'message']);
You can simply further with just $this->reset();
Thanks, somehow missed that in documentation.
Thank you... this is very useful.
That is much better than what i ve to write in vue to reset the form. But what about nested models/arrays? Does this keep the model structure?
Seems i should test it from start
Great explanation, thank you!
I think Livewire is perfect for simple data entry projects, like a simple one-step form submission.
So we accepted this stack finally.
Btw Livewire is awesome 👏🏻
I have tried Vue and Flutter as the front end and Laravel API as a backend. It worked but in the long run I think I will not be able to keep up with all those different technologies. So I will go back to just Laravel with Blade. I will give Livewire and alpine.js a try though as an in-between-solution
I want full series. Please create awesome tutorials like this one.
This is great news, exactly what I was wishing for a long time, thanks livewire
Hei, very nice examples. I do get the point of livewire and it looks good, but .. imagine you have form with 10 fields, do I understand correctly that livewire would do 10 api calls just for 1 update? So if 100 people update form at the same time it is almost as if 1000 request was done. I can not see the benefit of that. Can you explain that more in detail? Maybe I just do not understand it
There are ways to make fewer API requests, use different events than in this example.
But generally yes, there's a risk of too many API calls.
@@PovilasKorop But this risk also exists when you are using jquery. It always (!) depends on the implementation.
There is a pretty simple way to handle this.
You could use wire:model.defer to keep it at a minimum
I've been wanting to use Livewire since before version 2 came out, but I need to start a new project using just that, and that's not happening until I'm done with the project I'm working on right now. Thanks for the video, as always very informative. -Khalid
what will impact the performance of the application as PWA livewire vs Vue vs jquery?
I will definitely go with livewire
too much requests to backend , its good for small projects , but not good idea for the developers who caring about perphormance and laravel structure , with livewire you dont follow laravel structure for requests and controllers
You can modify how often livewire makes an ajax request to a certain degree
Better use js library bruh
wire:model.defer="name" - it could help you. Just one request on submit
Developers who care about performance don't use laravel in the first place 😁
@@YourAwesomePlace Then you lose some goodies like realtime form validations. And what about the fact it recieves a full html of component instead of json responses like react or vue?
my only conern about the livewire is it sends more requests on the server .I know it can be handled by debounce/lazy but again it's sending more request then vue.js
Though he gave example of GitHub but I don't think GitHub but I don't think it should be a good comparison. Yup http requests for everything almost.
Livewire V2 has new way of binding ( wire:model.defer)
That way you only send the request when you click to submit the form
In cases where you don't need data updates to happen live, Livewire has a .defer modifer that batches data updates with the next network request.
@@nkrumah2000 Then you lose some goodies like realtime form validations. And what about the fact it recieves a full html of component instead of json responses like react or vue? That results in larger response sizes.
@@AhtshamShabir wt about SEO is Livewire SEO friendly?
My team at work had to choose a new front-end framework last week because we wanted to get rid of jQuery. We picked Livewire over Vue.js because we are all PHPers not really skilled in JS.
I work with livewire, very simple, clean an productive. But... The mess arrive when you want to embed some other library as ckeditor, tinyMCe, select2 etc.. and nested livewire component. As for now for me it doesn't work !!!
you can use wire:ignore, that way when livewire parses the page, it wont change the child html/jscript in the div
was that point really worth three exclamation marks?
@@dogwalkinginc6371 For example, i can not make working leaflet map library as i want. i have a step by step form make with livewire at the first load on the first step all is good the map is created and displayed by leafleft, then if i go forward to the second step then backward on the first step , the map dissapeared and can not be recreated again. I known is not for all a livewire problem. But more generally for me the difficulty is that livewire reload all the dom for the concerned compoment and destroy content generated by other libraries and sometimes not easy to make all the pieces dance together.
@@BernardBAILLY I just watched this screencast(laravel-livewire.com/screencasts/s4-rich-text) and walked through everything and have trix rich editor up and running perfectly. Caleb explains what you need in order to make javascript not conflict w/ Livewire.
@@dogwalkinginc6371 reminds me of jQuery days
I don't familiar with Laravel, but is there way to create a custom client-side validator with Livewire?
Great video! I would like to see you do a Laravel Nova and custom admin templating. For example I always find it difficult to make the admin panel my own with out all the quirks in Nova and the docs can be a be unclear at many key moments leaving you clicking back and forth through the docs trying to find he missing step.
I'm not planning to make reviews or customizations about PAID products, because it would be useful for only small amount of my audience who purchased that product. Nova included.
Povilas Korop ok I can see your point and understand , it was just a suggestion as no one seem to be doing this type of video. I can’t even find it on paid learning coding platforms but Laravel seem to be pulling it a lot still hence why I suggested it. Anyway keep up the good work I enjoying your video content that you are creating. 😎👍🏻
@@markbarton6845 To be honest, I've read quite a lot of similar comments about Nova, that it's hard to customize, so personally, I wouldn't recommend it as a solution. Of course, I'm biased as a QuickAdminPanel creator :)
David Basil sometimes it about time and budget. Nova is very good on small projects. It gives enough out of the box to get you about 90% of the way in not much time at all. For this I found it to be very good. However when you want to be more bespoke about your admin styling the grey areas of the documentation leave you in a guessing game. I put this down to me not understanding aspect of the docs and how to apply them rather than pointing my figure at the package.
Livewire is great, ive not actually used it myself, but i have watched a few introduction videos, and with me not really getting into the front end jscript frameworks, this will make it a lot easier for me to bring the front end into 2020
Thanks povilas you have a great following here in italy!!
I've had a few clients from Italy, wonderful people :)
I'm giving a try on livewire on my new project. I was using vue for reactivity on my website. But when I go through the documentation of livewire I feel like I wont regret using it.
I was skeptical at first (and also annoyed) when I saw that 8 shipped w/ Jetstream/Livewire. But I decided to dig-in and try it, and so far I've been nothing but impressed. It's one thing to shout about theories of its poor performance. it's another to actually use it first hand and judge with facts.
Very clear. Very good example. Thank your very much. Use Livewire more easy.
it's just like the ASP .net tech in the olden days, heavily couple the view and backend together, very little flexibility on the frontend, good for people who have zero knowledge on frontend/JS
I thought I was the only one seeing the similarities.
Just abandoned .net altogether during the evolution.
This is amazing. I see great hope for livewire
I think a popular misunderstanding is that Livewire is a potential replacement for Vue. It is not. It delivers reactivity in a beautiful way, yes, but it does not provide for managing loops and DB calls. That still is undertaken within Laravel. A major benefit perhaps?
@vincej151 what exactly do you mean by "managing loops" and "DB calls"?
and also it is replacement for js framework, why would you use livewire and then additionally install js framework? That makes no sense.
@@impulserr It is great for reactivity and substituting for Ajax. Go and watch the author of Livewire on his website. Caleb's own video tutorials state that this is not a replacement for Javascript or Vue or JQuery for that matter.
@@wulfheart5475 if you would like to understand this, start here, it's not hard:
www.w3schools.com/php/php_if_else.asp
@@impulserr Livewire is very good at what ti does, but it does not do everything you need in the front end. You don't need a JS frame work. Just JS.
Your videos are super amazing. You explain stuff pretty well! Thanks a lot for the videos
Glad you think so!
For database propose should i use inertia ou limewired
Thank you for this video. If I want to do simple I will go for easy and looks like livewire is easy to implement. But this Vue Livewire jQuery and others stufs depends our needs. I'm using jQuery for little things sometimes. If I want to more complex structer I'm not using jQuery. Because thats really hard to code and manage. If I want to more complex app I will use Vue or similar. Depends our needs I guess.
Livewire is very interested, but i think is not matute enought yet. I was using it in a production project and things where broke when updating livewire versión. Also if your not carefully you may end up with too much ajax requests
Thanks for a video, but how we can use requests to our custom api methods with livewire?
Каким расширением пользуетесь для автозаполнения полей форм ? Спасибо
addons.mozilla.org/ru/firefox/addon/fake-filler
plis laravel 8 inirtia + vue CRUD and auth role
Yes, it would be good if the author makes a video also about Laravel + Inetria.js.
We want more livewire tutorial.
Wow as a back-end software developer this really does sound interesting. I can't think of how many times you have to work with javascript to make something reactive. I will definitely do more research, and I am looking forward to more videos about this stuff!
Me too, i was very interested in this new library that stays on the backend and not worry too much about JS.
Im in the process of rebuilding a CMS with Livewire and then Inertia.js, just want to see which side is more efficient because both are server side with the only exception that Inertia uses Vue, React or Svelte but only for the views, the rest is all Laravel backend which passes the data to the views. Im planning of releasing both of these CMS'es as public git repositories which some might find useful.
@@Tux0xFF Nice man! I'd be very interested in seeing the results
I have been using Livewire for a long time, and if you use ir with alpinejs you can do everything
Great comparison, thank you!
But there is a fifth way you could test. Basically progressively enhancing the "web" version, using htmx (successor of intercooler) or for an even more impressive "no code needed" option, unpoly : unpoly.com/
Quick howto with unpoly:
- Read unpoly.com/form-up-target
- For a quick test add unpoly to your project using a CDN unpoly.com/install/cdn
- Add some class to the .card that contains the first sample something like
- Update the of this sample to be like :
And voilà, same reactivity as the other examples without altering your code, and works with and without javascript enabled in the browser. Easy-est to write and maitain.
If you want I create a pull request for that on the repository.
Unpoly is the unpopular hidden gem you might like to discover. It has been written to make long term, maintainable web applications. I'm not affiliated with it, I'm just a huge fan :-)
Can livewire be integeated with HOT RELOAD like React JS?
Очень полезное видео. Нам действительно не нужны абстрактные примеры. Реальные примеры наглядно демонстрируют выгоду Livewire для Laravel программиста
I have just learned react. Should I go with react and laravel or learn live wire please suggest me.
Try and learn both, and learn Vue too :) Each tool has its use.
greet video we need more about livewire plz
Liveware is love
Livewire is awsome.
Cool, I need to try it later. Thanks.
thanks for the wonderful explanations, keep doing...
Yay, the very best. more LiveWire please :-)
Thanks for this great information. Amazing way to explained it.
I started to use livewire, I think it's a great tool but there are some certain limitations which I am still discovering. Like not being able to store a collection as a public property or to render different views with data. I think and would love to see a video on all these limitations and how to overcome them.
Stay tuned, more changes are coming, the creator of Livewire Caleb will certainly expand this to more possibilities, the v2 already had many improvements, and who knows it may even be part of core Laravel because Taylor also loves this library, and Caleb loves to solve impossible problems, thats what drives him to create these awesome libraries
I really really like this video, awesome Povilas
thank you
Psst! Wanna know about something better? Try Phoenix LiveView. LiveWire was actually inspired by it in the first place, and it uses websockets instead of AJAX, so it is a lot faster. But to be fair, if someone already knows PHP/Laravel then stick to LiveView, but if one wants to learn Elixir, a new functional language that powers Phoenix and LiveView, then give it a try. I'm using both frameworks/languages on different projects nowadays. It's faster than Node.js too if you are curious.
Need suggestion. I am not familiar with vue at all. I have used jquery all the time. Now I want to start working in vue or livewire. Which one should I go for?
First, try Vue. It will get you better job positions in the future. Just TRY. If you really dislike it, then try to replace it with Livewire.
@@PovilasKorop thanks.
React is best for job purpose
Very good! Thank you
Very nice tutorial sir
i think livewire is very backend developer oriented but not end user oriented, since the performance is gonna be deeply affected
Does that mean if we know vue then livewire is not required? Can you please specify correct use case of livewire in real time application?
livewire is made in my opinion for people who don't like ineract alot with javascript otherwith i think vue will give you more powerfull options
Vue better but Livewire is a bit more simplistic
It's a philosophical question, to be honest. What are you MORE COMFORTABLE with? If you are happy with Vue, you don't need Livewire. But if it feels that Vue is too much work for you, Livewire can make SOME stuff much easier. In my opinion, Livewire is mostly for those back-end developers who haven't really started much with Vue because they don't like JS, and with Livewire they don't need to write JS anymore at all.
@@PovilasKorop And also Vue is a more transferable skill. We can only use Livewire with Laravel but if we work on other frameworks we can still use Vue
@@tanzimibthesam5861 Great point. Livewire is more like a helper for Laravel developers, it's a Laravel package after all.
It sends way more requests than vue or react. Another downside is that it has to download a full html page in response and then diff the changes while other js frameworks just get json responses. Way more requests and bigger response size. I personally haven't used livewire so I'm not sure if it handles client side validations and routing.
It definitely has its place for small projects. But for bigger projects, it abstracts away a lot of necessary control.
thank you for your explanation!
Holy moly ... sign me up!
great explanation, thank sr
спасибо
Awesome tutorial.. thanks a ton !
Awesome love livewire
I use livewire, but sometimes you to use alpine js with livewire.
nice tutorial. thanx sir.
In general it looks awesome, but this not good because it handle all js underneath the hood for someone intreseted to write his logic with it's requrement i don't think it would be a good choise otherwise it's really awesome
Yes that "hidden magic" of JavaScript is what also scares me, that's why, in my opinion, Livewire is good for some small components, like this form, but not for something that would potentially require custom logic.
@@PovilasKorop yes you are right it would be good for small business
@@josephmakram4342 small business and customizations are not the same thing
in most cases in small business there no much customization
@@josephmakram4342 I also think it can be used for blog or simplistic crud projects but it has a easier learning curve . But I believe we can learn both
Thank you!
First i gave up with nuxt. At first it was wow, vue with ssr. Later i've lost so much time installing plugins, tons of npms... now vue is at the same stage. Small projects but to the end i have hundreds of files and i dont remember what ive done 2 weeks before. Great things of vue die while data transfering back and forth to server. Data transformations, array loopings, mapings etc in order to pass it to new superhandymobilefriendly vue-component.
Last days i want videos on livewire. If it is ready to simplify data transfers... the only trouble - while you learn livewire, there will be laravel 9 with supernewawesome verylivewwire and from the very beginning) sorry for emotions.
Crying when look my first site with flash buttons written in notepad. Index.txt save as .html. later php. And basic txt editor was enough to build anything....
Maybe build chat or notifications popups in livewire + pusher + echo on SPA
Really Excelent, Thanks
is so hard for server side to handel 4 request onli for a contact form
it doesnt need to be 4 requests, just one, with the defer option which executes on click submit
Please, next video, how to add jetstream (Inertia + Vue) to live Laravel project upgraded to Laravel 8. :-)
There's no way to ADD jetstream to an existing project, it's not the purpose. Jetstream is a project STARTER, like "laravel new" installer.
@@PovilasKorop I think, its not so easy, but is definitelly possible.
the TALL stack is really powerful
only thing that i really dont like is Tailwind, so i use the BALL stack, which uses Bootstrap
Very nice thanks
Nice
Please create a video about Voyager
Please may u do livewire tutorials maybe on laravel diary
Excellent!
Excelent
Nice.
Please make tutorial for laravel resources API
What exactly is not clear for you there? Actually, I have a separate course on APIs: laraveldaily.teachable.com/p/how-to-create-laravel-api
@@PovilasKorop That's great but I'm talking about this - laravel.com/docs/8.x/eloquent-resources#resource-collections
@@akashthoriya Yes, that collection API resources are part of my course. Also, I'm not sure what can I make a tutorial about, if the documentation is pretty clear on that topic.
Seems to be safe Laravel developer with Livewire as compare to VUE JS
good information, but very rapid. especially that this is a new tech
imho the vue is more useful because may be some day you will work with javascript + vue, and its very popilar so its a plus for your cv. Also its more easy to person who is more familiar with javascript it self. But if some one is more backed php guy, probably they will stick with jQuery and livewhire
with livewire, it's no more Model View Controller **its Model (View + Component)**
sorry livewire. i just marry laravel and vue js
kkkkk
See my comment
You are using Inertia right?
if not, your working too much.
Livewire is the baby of Laravel+Vue
@@Tux0xFF Nested components in Livewire are not reactive like props from a Vue component so... What actually does it mean? It can put off people.
@@Tux0xFF livewire is great for a local project, but for a project with multiple access and a not so great server the ajax request for reactivity is terrible. They want you to use alpine to make things client side and... Well... It's not so good. Plus, livewire is just for laravel, if you someday need to use laravel as API or use another framework it can hit you hard, so it's good to learn and use vue/react/angular nowadays
personally I don't like livewire because it will request all the changes to the server.
if your traffic is not very high then it will make sense to use it
but if your site is a high traffic site, it will burden the server surely
livewire series plz
Best channel
real crack!
Omg this is rlly great 😍😍
I don't see reason to use livewire in real app. If you don't know any js then using livewire won't teach you anything, in other hand if you know, there is no reason to use livewire.
Isnt faster than building a SPA? where you have to deal with creating an API, then Auth if its needed. Livewire is reactive. There is also another adapter called Inertia which cuts a lot of bs that involves building an SPA, which is flawed because you have to work so much more , unless it serves mobile, web and other services then its ok, but for a website, a CMS, a CRM where most of the time SEO is important and everyone knows that SPAs built in the classical way have always had that problem, its been years already and the problem remains, there hacky workarounds for it but its just doesnt feel right.
Livewire is awesome. You should make a seperate video on livewire instead of comparison.
🔥🙏
But you are Livewire, right?
if not, Caleb will delete all your livewire videos
No thanks, I prefer to move as much as possible to the frontend and leverage the users cpu resources than my own.
Can some give me some examples using ssr in Vue spa
all JS frameworks suck for SEO related apps, its the wrong solution to that problem.
Waiting for famous blade+ jQuery enough comments
Wait wait, waaaait. You need BLADE? :O twitter.com/levelsio/status/1308145873843560449
was better to say smth about advantage or disadvantage to use livewire
weird to find actual web developers trying to avoid javascript.
stop fighting the inevitable. be more efficient
livewire is inefficient without learning whats going on behind the scenes and putting in extra work to improve it
looks like a godsend, javascript is a nightmare.
Try upload multiple big videos using Livewire, and see how it works
No client side preview (BEFORE UPLOAD): createObjectURL + video n canvas element, which is really easy and faster
But the fact is Livewire "instantly" upload selected files whenever input files is changing
Example case
I want to upload a video with size +-200MB, with my smartphone, currently in that moment, my phone connection is not really good
So what happen next? i have to "idle" in the upload form / page for few minutes (since my connection is bad) just to see what I have uploaded ($f->temporaryUrl()), this is not a good UX,
then, if I want to change the video (Cancel the previous video), then again, I have to wait again for few minutes for simple preview?????? Really???????
Nope nope and nope, just nope
I knew they provide JS function for manual upload, but still, nope and thank you, I'm sticking to Laravel n Vue
Thanks for pointing this, I have the feeling that it would be limited or could have some issues because it just looks a "cool" tool that isn't really well-thought. I will save my time from learning it.
@@ivantan222 for small project its good, but in large scale app, no, IT IS NOT
My advice is, for long-term website development, you should use something that has wide range community support, so in the future, you don't have to change many things for your future requirement, Vue is already easy to learn, its not gonna hurt to learn it, there are tons of plugins for Vuejs framework
@Gwein Lotusiana Yeah, I agree. Moreover, I often find a project that looks easy at the start, so we might be interested in a simple tool like this Livewire, but when the project goes bigger it will be much more complicated if the tool can't support or becomes the technical barrier.
@@ivantan222 indeed
For me, if I ever need to update my features, etc, I don't have to "entirely" change everything, and go through learn process, trial, and error all over again
That's why I choose to stick with Vue
And another example, for Laravel Eloquent
If ur model record is still below 50k - 100k records, it is still good using eloquent
But when you reach > 200k records, you should start using Laravel Query Builder
1. stackoverflow.com/questions/58314420/laravel-eloquent-vs-query-builder-pros-and-cons
2. medium.com/@abad.developer/laravel-eloquent-vs-query-builder-why-use-eloquent-to-decrease-performance-5aa17bed358a
3. (PDF) www.google.com/url?sa=t&source=web&rct=j&url=www.diva-portal.org/smash/get/diva2:1014983/FULLTEXT02&ved=2ahUKEwi0vPzvyYjsAhXJAnIKHXKLCVcQFjAOegQIARAB&usg=AOvVaw3Dz7Dk8x6LzIOFbzvp8zhW&cshid=1601183897129
@@delvinlotusiana2704 btw should I use nuxt for SEO or Vue would you enlighten
Livewire +
Blade was just enough functionality at the backend. Livewire doesn't have any future, especially with introduction of much simpler and efficient jQuery alternative (Vuejs) for years to come.
Actually I prefer avoid Livewire and go pure with Blade.
Livewire sucks.
a developer who locks on one stack will never be better than a developer who learns new things. vue expands consciousness, while livewire looks like a crutch for those who have not mastered vue
You make the assumption that Vue is the best alternative. And then presumably whatever JS framework supersedes Vue in the next few weeks/months will become the new best alternative and so on and so on. Personally I'm still on the fence with Livewire, but I welcome the option to remain within one stack. It's a "jack of all trades" vs "master of one" situation. But a "better developer" to me is one who gets the job done quicker, cleaner and simpler - not just one who knows more ways to skin a cat.
@@andy.robinson you are right
You couldnt be more wrong adminko.
Why are you even here in a Laravel channel? Its like someone from the Laravel side comes to a Vue channel and talks shit about why are you using this small library for backend , it is a crutch.
Laravel is a whole ecosystem, is a fullstack framework, no other framework achieved what Laravel did, JS is just a helper for Laravel, its a la carte menu to enhance some parts of it, do you think the world revolves around SPAs? Are CMS's, CRMs, ecommerce, and web applications in general all built with Vue or any other JS framework?
Each tech stack have its own uses, only hipsters put JS frameworks on everything, even in their salads and their laundry detergent. What happened to the Deno hype? where did the hipsters go?
you are very right