Am I really the only one that works with both TALL & VILT without budging, complaining or questioning? :P Regarding choosing a stack when getting into Laravel: It depends on the experience you already have with the front-end library (Vue, React, ..) and if so, go for that combination. You'll have a lot to learn in the back-end stack, so if you're already familiar with the front-end stack, it's fine. But, to be honest? At least trying out Livewire for a bit, for a personal project, will also learn you _even more_ about how they handle that back-end stack, as they actually use it to make that work. Livewire might seem to pull/keep you out of the Javascript eco-system somewhat, but: the combination with AlpineJS is vastly imminent when dealing with more complex components. And guess what AlpineJS mimicks so we don't have issues getting some of the concepts down? (: To be fair? Don't make a choice at all at first. Try it before you make your mind. Also, a tech-stack isn't an identity, it's a tool. Stop making your identity a tool. (That's the same for Linux,Windows,Mac btw)
VILT developer here! I'm in love with VILT stack ❤❤ About speed: I created my reusable components so for every new project I just change the style of those components and I spare a lot of time.
TALL = Tailwind AlpineJS Laravel Livewire VILT = VueJS Intertia Laravel Tailwind (but “Inertia” is there for the vowel really - it’s not something you have to spend long learning)
I am a junior developer with angular experience. I learned Laravel with blade and would prefer livewire, since your learning projects are finished faster with that. But to get a job I would learn both since it augments your chances.
Can you please tell me when exactly you would use a closure like that? when you filter query for the products inside the livewire component ( Products.php)
I know this gets asked a lot and typically a matter of preference, but you said for larger apps, vue/ react may offer more customizability. But almost any video on the topic typically shows examples that could be done in livewire. So, I am really still at a lost as to what vue or react may do better than livewire. What use cases might prompt a company to switch other than available talent? I know every framework / language has pros and cons but its hard to judge pros and cons if you dont have experience with something. and it would seem silly to learn 3 different tools that basically produce the same result, just to see whats better. Are there any definitive or measurable examples of performance, ease of development, or any other matric between the 3 options? If you were designing a project in livewire, what sort of thing might make you want to switch to a different tool? can different tools be used on different sections of the app without conflict?
It's hard to create complex examples in both stacks, it takes a lot of time. But we'll see if we manage to find that time with the team and shoot the showdown with comments.
@@LaravelDaily It would be interesting to see an example that is easy to implement in Vue but hard (or impossible?) to implement in Livewire (or maybe just very inefficient to implement in Livewire), and another example that is easy to implement in Livewire but hard to implement in Vue (if such an example exists).
The worst part i have about the "full-stack developer" is the fact that EVERYBODY require AWS. It's a DEVOps job to handle that. Their administration panel it shit. In regards to the 2 staks, I wrote projects in both. Depending on the complexity of the project i prefer vue especially for making lot of client side operations before buzzing the server with requests
I second that their management panel doesn't make sense. It's a cognitive load of options and "hidden structures" and "special names" to make something normally very simple work, and if not done right: it won't work (as expected) or just be a wallet drain. I know there's some tools out there making it easier, but there's so damn much aws tools, I just can't seem to find it right now. -_-
In my experience with my projects, I didn't have any issues with Filament, but maybe I haven't worked with LARGE scale as you mentioned it. Can you try to describe a "large scale" application so we would try to simulate it with Filament?
@@LaravelDaily I mean an application that is used by hundreds of thousands of people and receives a large number of requests. Is also is filamentphp suitable for sensitive applications in terms of security and so on? Or is it just a way to create small or medium applications? // thanks for reply I am top fan for your content and I am a premium member at laraveldaily website 💗
I mean an application that is used by hundreds of thousands of people and receives a large number of requests. Is filamentphp suitable for sensitive applications in terms of security and so on? Or is it just a way to create small or medium applications?@@LaravelDaily and Thanks for all I am a big fan of your content and I am a member at laravel daily website ❤
So, in your opinion, "scale" is the amount of TRAFFIC. That could be scaled with server hardware pretty easily, no matter the code under the hood. Unfortunately, I haven't worked with Filament applications used by 100k people so can't comment or simulate it.
@@Mr.Error__ do you have such application? Doesn't seem like. When it will reach such number of visitors then you will see. Until then you will be fine. Especially when v4 will be released with partial reloads
There is one more major difference between both stacks and that is SSR. TALL is server-side rendered by default while VILT requires extra setup and that's very important for SEO
So should i move towards VILT or TALL for my self learning? PS: I have 3 years of experience in Laravel, and almost 0 years of professional experience in any front-end technology (besides learning projects).
How about the camp of Vue + Laravel as a REST API without intertia? In the future when you expand your web app to mobile, or maybe create other portals in different domains, you won’t slap yourself in the face.
I hate that Tailwind has gotten so popular, I'm happy with Vue or Livewire they both serve their purposes in the stacks but I personally don't like the whole shift to Tailwind.
@@jcc5018 Sounds just about the same "issue" as Bootstrap some years ago. - I'd be happy to hear which packages unwillingly force you into TWCSS except for maybe Filament.
@@salaccarljosepht.8681 It's just my opinion and you should 100% complete learning it and I'm sure it will be beneficial to your career. The reason I don't like it is that it feels like regression. It's hard to read afterwards especially with a bunch of class names wrapping over multiple lines. It gives me the same vibes as just doing inline styling with a little bit less typing.
VILT is better, here's why. Vue3's composition API has the best syntax of any frontend framework and it is also very intuitive for a Laravel dev to pick up. Vue3 is a cutting edge frontend framework and being able to seamlessly use it with Laravel gives you everything.
Am I really the only one that works with both TALL & VILT without budging, complaining or questioning? :P
Regarding choosing a stack when getting into Laravel: It depends on the experience you already have with the front-end library (Vue, React, ..) and if so, go for that combination.
You'll have a lot to learn in the back-end stack, so if you're already familiar with the front-end stack, it's fine.
But, to be honest? At least trying out Livewire for a bit, for a personal project, will also learn you _even more_ about how they handle that back-end stack, as they actually use it to make that work.
Livewire might seem to pull/keep you out of the Javascript eco-system somewhat, but: the combination with AlpineJS is vastly imminent when dealing with more complex components. And guess what AlpineJS mimicks so we don't have issues getting some of the concepts down? (:
To be fair?
Don't make a choice at all at first. Try it before you make your mind.
Also, a tech-stack isn't an identity, it's a tool. Stop making your identity a tool. (That's the same for Linux,Windows,Mac btw)
The power of Twitter: there's now also MingleJS to close the gap between Livewire/JS :)
VILT developer here!
I'm in love with VILT stack ❤❤
About speed: I created my reusable components so for every new project I just change the style of those components and I spare a lot of time.
TALL = Tailwind AlpineJS Laravel Livewire
VILT = VueJS Intertia Laravel Tailwind (but “Inertia” is there for the vowel really - it’s not something you have to spend long learning)
I am a junior developer with angular experience. I learned Laravel with blade and would prefer livewire, since your learning projects are finished faster with that. But to get a job I would learn both since it augments your chances.
Can you please tell me when exactly you would use a closure like that? when you filter query for the products inside the livewire component ( Products.php)
I know this gets asked a lot and typically a matter of preference, but you said for larger apps, vue/ react may offer more customizability. But almost any video on the topic typically shows examples that could be done in livewire. So, I am really still at a lost as to what vue or react may do better than livewire. What use cases might prompt a company to switch other than available talent? I know every framework / language has pros and cons but its hard to judge pros and cons if you dont have experience with something. and it would seem silly to learn 3 different tools that basically produce the same result, just to see whats better.
Are there any definitive or measurable examples of performance, ease of development, or any other matric between the 3 options? If you were designing a project in livewire, what sort of thing might make you want to switch to a different tool? can different tools be used on different sections of the app without conflict?
It's hard to create complex examples in both stacks, it takes a lot of time. But we'll see if we manage to find that time with the team and shoot the showdown with comments.
@@LaravelDaily It would be interesting to see an example that is easy to implement in Vue but hard (or impossible?) to implement in Livewire (or maybe just very inefficient to implement in Livewire), and another example that is easy to implement in Livewire but hard to implement in Vue (if such an example exists).
Nice video Povilas! It would be amazing if you could make a video about Hybridly as well.
Never used it, so can't make a video, sorry.
What exactly would you want about it? It's pretty much the same as inertia. Only that pushes more typescript
@@krekas An introduction video would be nice.
The worst part i have about the "full-stack developer" is the fact that EVERYBODY require AWS. It's a DEVOps job to handle that. Their administration panel it shit.
In regards to the 2 staks, I wrote projects in both. Depending on the complexity of the project i prefer vue especially for making lot of client side operations before buzzing the server with requests
That's why tools like Forge or Vapor exists and are popular.
I second that their management panel doesn't make sense. It's a cognitive load of options and "hidden structures" and "special names" to make something normally very simple work, and if not done right: it won't work (as expected) or just be a wallet drain.
I know there's some tools out there making it easier, but there's so damn much aws tools, I just can't seem to find it right now. -_-
@@LaravelDaily I still find having a Digital ocean droplet and use something like jinking's to be more straightforward
thanks for sharing and it clarifies the confusion.
Nice video, plz What is your opinion about using Filamentphp as full stack Application that will have large Scale?
In my experience with my projects, I didn't have any issues with Filament, but maybe I haven't worked with LARGE scale as you mentioned it. Can you try to describe a "large scale" application so we would try to simulate it with Filament?
@@LaravelDaily
I mean an application that is used by hundreds of thousands of people and receives a large number of requests. Is also is filamentphp suitable for sensitive applications in terms of security and so on? Or is it just a way to create small or medium applications?
// thanks for reply I am top fan for your content and I am a premium member at laraveldaily website 💗
I mean an application that is used by hundreds of thousands of people and receives a large number of requests. Is filamentphp suitable for sensitive applications in terms of security and so on? Or is it just a way to create small or medium applications?@@LaravelDaily
and Thanks for all I am a big fan of your content and I am a member at laravel daily website ❤
So, in your opinion, "scale" is the amount of TRAFFIC. That could be scaled with server hardware pretty easily, no matter the code under the hood.
Unfortunately, I haven't worked with Filament applications used by 100k people so can't comment or simulate it.
@@Mr.Error__ do you have such application? Doesn't seem like. When it will reach such number of visitors then you will see. Until then you will be fine. Especially when v4 will be released with partial reloads
What about RILT? React instead of Vue but with Inertia. Why isn't that mentioned?
That is mentioned in the next video on the channel, the next day.
There is one more major difference between both stacks and that is SSR. TALL is server-side rendered by default while VILT requires extra setup and that's very important for SEO
So should i move towards VILT or TALL for my self learning?
PS: I have 3 years of experience in Laravel, and almost 0 years of professional experience in any front-end technology (besides learning projects).
Try "Hello world" in both and see which one you like more, then learn deeper.
When Tall or Talt will be released? Lack of stacks
Can you please make a video regarding table partitioning. Please
What about select2? in livewire.
Just use the TallStackUI Select component. And the other TallStackUI components...
forget select2. let it rest in peace
@@kreaweb-be google is really shitty at searching if i find about this package from a youtube comment
You can use it, look for wire:ignore in livewire
Can you make a video about sanctum and fortify
I didn't use fortify outside Jetstream ever, to be honest, so can't make a video
Make some video for server with laravel and make api response faster when i have huge data
How about the camp of Vue + Laravel as a REST API without intertia?
In the future when you expand your web app to mobile, or maybe create other portals in different domains, you won’t slap yourself in the face.
Yes, that's another option of the stack.
I hate that Tailwind has gotten so popular, I'm happy with Vue or Livewire they both serve their purposes in the stacks but I personally don't like the whole shift to Tailwind.
same, i mostly only have tailwind cause a lot of packages rely on it, but im starting to swtich to basic CSS styles
why? I'm currently learning tailwind
@@jcc5018 Sounds just about the same "issue" as Bootstrap some years ago. - I'd be happy to hear which packages unwillingly force you into TWCSS except for maybe Filament.
@@salaccarljosepht.8681 It's just my opinion and you should 100% complete learning it and I'm sure it will be beneficial to your career. The reason I don't like it is that it feels like regression. It's hard to read afterwards especially with a bunch of class names wrapping over multiple lines. It gives me the same vibes as just doing inline styling with a little bit less typing.
If you know css tailwind isn’t hard to learn on the fly
laravel and nodejs are not used for backend 😅
VILT is better, here's why. Vue3's composition API has the best syntax of any frontend framework and it is also very intuitive for a Laravel dev to pick up. Vue3 is a cutting edge frontend framework and being able to seamlessly use it with Laravel gives you everything.
How about Svelte instead of Vue?
@@omfgihopethisworks Svelte is good too. I hate returning HTML. Svelte just doesn't have a breeze starter kit.
Laravel Hybridly
Vue has quasar and vuetify.
And using laravel as backend
Perfect.