Tailwindcss is great for making crazy complicated layouts with very little boiler plate code. Bootstrap is very cumbersome and a lot of code to get very little done. Think of it as them both being a salad. Say today you prefer this salad because it is quick and easy to make, but other days you want your favourite salad that takes a lot of effort and time to make. Whose to say the salad that is your favourite is my favourite? That's the reason.
I also failed to mention that bootstrap has constant vulnerabilities, where-as taliwindcss itself has none because it is just an abstraction of css. With Bootstrap you need a tonne of js of theirs that takes them very long to fix. I have yet to have the same experience with tailwindcss and it's headlessui js counterpart.
my point is ... everything is designed towards tailwind. there are no packages or conversion from breeze/jetstream/fortify which are running tailwind to bootstrap. I think i speak in the name of many programmers who would prefer bootstrap over tailwind. even though the percentages might be 55 tailwind 45 bootstrap (not sure if these percentages are correct) - but i do think that 45% should be relevant enough to consider a fork in the development of the auth scaffolding.
I did it this way: component: {{ $slot }} and then I use the component like this:
/about
About Us My component looks much more complex though than using attributes Just curious what thoughts are on doing it this way, the pros and cons apart from the more lines of code involved and i looking more complex than it needs to be? EDIT: Okay i watched the rest of the video :)
Watch Full Series as well as more courses on laracasts.com/
That typing act at the end 😂😂..Btw awesome series ❤
I noticed the same thing😃
yup. noticed it the previous episode. he is a fun dude.
Outstanding series!
thx for your teaching ♥
im from iran 🇮🇷
Jeffrey is such a funny guy and he makes learning laravel fun.
I really love the style of your teaching!
Thanks for a new informative series! Awesome job as always
Awesome teacher 🩵🙏
Laravel is really pleasing!
Jeffrey you are a funny teacher
pls continue recording youtube videos and courses
thx
Great tutorial..
why use component for layout and not @yeld?
How did the reference codes at 6:16 come automatically?
That is a "live template" from phpstorm. He just defined it before and uses it to save time, useful snippets!
@@DamianS78 ı know but how?
Done.
Used Bootstrap 5 instead of Tailwind,
Thank you.
Can I acces "14 more videos"?
Slot function is not working
😂 Typing like the BBC news lady
hi. i still do not understand why tailwind and not bootstrap.
Tailwindcss is great for making crazy complicated layouts with very little boiler plate code. Bootstrap is very cumbersome and a lot of code to get very little done. Think of it as them both being a salad. Say today you prefer this salad because it is quick and easy to make, but other days you want your favourite salad that takes a lot of effort and time to make. Whose to say the salad that is your favourite is my favourite? That's the reason.
I also failed to mention that bootstrap has constant vulnerabilities, where-as taliwindcss itself has none because it is just an abstraction of css. With Bootstrap you need a tonne of js of theirs that takes them very long to fix. I have yet to have the same experience with tailwindcss and it's headlessui js counterpart.
my point is ... everything is designed towards tailwind. there are no packages or conversion from breeze/jetstream/fortify which are running tailwind to bootstrap. I think i speak in the name of many programmers who would prefer bootstrap over tailwind. even though the percentages might be 55 tailwind 45 bootstrap (not sure if these percentages are correct) - but i do think that 45% should be relevant enough to consider a fork in the development of the auth scaffolding.
i want moar!
The videos are wonderful, but I'm not keen on the full side-on shots. It feels like you are detached from the audience.
ugh tailwind, gonna ignore that
I did it this way:
component:
{{ $slot }}
and then I use the component like this:
/about
About Us
My component looks much more complex though than using attributes
Just curious what thoughts are on doing it this way, the pros and cons apart from the more lines of code involved and i looking more complex than it needs to be?
EDIT: Okay i watched the rest of the video :)