@sourcefli Where was this written

where are the "L8 "new feature" notes"

@lemmon probably https://laravel.com/docs/8.x/releases

Yes, @jlrdw is correct.

Scroll down just a tad bit, to the "Laravel 8" heading.

(I named it "new feature" notes for the sake of what I was saying in my previous comment)

upgrading projects from laravel 6 to laravel 8 would be like learning a new framework for me. Time to switch over from Laravel

@beracah.kings hardly. theres not a massive difference between Laravel 6 and Laravel 8. If you upgrade, you should go to 7 first but even then, that shouldn't be too much of a hike rather than scrapping your app and rebuilding into some other unknown framework.

if you watch the 'what's new in' lessons, you'll get a handle on what has changed.

How complex is your application to make it not upgradeable?

@beracah.kings

All the skills and techniques you know from Laravel 6 still work in Laravel 8.

If your project is complex then the upgrade will still be significantly simpler than porting it to a different framework.

If you feel you need help with the upgrade then Laravel Shift would speed up the process.

My personal preference is to make real work with LTS versions, and keep testing intermediate version to learn an keep tracking framework evolution

About BS, I was looking around for a replacement since version 3.3 but any alternative seemed to similar for me, so I kept working with it until last year I discovered Tailwind. What at first glance seemed to me like a overload of classes, but with a little use just let me absolutely delight. Just droping BS and jQuery from my sites implies about .5Mb of diet, I really like it.

I tried with inertia. New features doing the same things. documentation for Frontend in both laravel and jetstream will confuse beginners.

@beracah.kings That's just scaffolding Auth. You can use any css or JS you want. I already changed my logon page to bootstrap. I do not use Vue, inertia, livewire.

I use bootstrap and custom css and fetch JS. And a little jquery. You don't even have to use any JS if you don't want to.

@jlrdw Thanks. Since few of my projects are with vuejs, I thought using inertia would be easier. codeigniter 4 looks similiar to earlier versions of laravel.

I started with 5.8, moved to 6, moved to 7, and my hosting provider upgraded my app to 8 which took me by surprise me and terrified me.

However, Taylor and group have done a remarkable job in making sure that the install/upgrade went very smooth, and the upgrades don't cause harm. Had I not received notification from the host provider I am not sure I would have known for a couple of weeks.

I updated my development/testing environment and had NO issues.

I am not currently using Jetstream, but I think there is a very good chance I will due to the built-in authentication feature.

As for TailwindCSS, I LOVE it!!! I started with Bootstrap, but it just seemed to be clunky (drum brakes compared to Disk brakes). It worked, but very unimpressed with it. Once I started with TailwindCSS, I was hooked. Parts of it are overwhelming for me, but there are plenty of resources to help and to find examples from. And, you can have both Bootstrap & Tailwind in the same app. I still have some remaining bootstrap, but I have replaced ~99% with Tailwind.

The TailWind group created a site which contains quite a few UI examples that have been a GREAT help for me Actually, without that site I would NOT have switched to Tailwind due to the huge learning curve I was going to have. I still have a lot to learn about TailWind, but due to the examples I have found, their UI website, and their amazing documentation, I am doing pretty good at the moment and slowly expanding my capabilities with it.

Make a backup, upgrade, try it out, and perform a restore if you don't like it.

For me, the only problem I had with Laravel 8 was TailwindCSS plus I really wanted to use the Jetstream for my new projects which I think is similar to your dilemma, everything else I understood in a day. Livewire was mostly like VueJs but in PHP, AlpineJS had reasonably small documentation so in less than an hour, I was getting the hang of it. But tailwind tho it was a nice piece of work and all but I've always leaned towards frameworks that gave me some form of opinion, I mean if that wasn't the case I'd still be with Symfony.

So to solve my problem I decided to create a package that replaces only the tailwind aspect of Jetstream called Jetstrap. Check it out to see if it can make the same compromise.

Taylor makes Laravel/UI obsolete because the code and style are mixed there and he imposes the usage of Tailwind in JetStream! I find it difficult to follow

I will try this ;)

@cotiga I don't use tailwind, I only used jetstream to scaffold Auth. You can still use any JS and CSS you want.

I would go to 8. Listen to the following Video which will explain how you, if you reallllly want, could stay with the ui version from 7.x and lower. Just remember, ui is deprecated in 8.x and as such may not be available for the next major version. The video gives an amazing description of the changes, what each will do, which one makes sense depending upon what you are wanting to do, etc.

https://www.youtube.com/watch?v=NuGBzmHlINQ

Oh yeah, I would highly recommend that you "subscribe" to the channel.

if Laracasts could add videos for Laravel 8, it would be great. People say stick on with Laravel 7 but it will be supported only till next year. Difficult to convince team to switch over to Laravel 8 after investing so much time in the earlier Laravel versions

I'm pretty sure some is on the way, I believe he mentioned it in the What's new in Laravel 8 series.

I did like just laravel docs, now you have laravel, jetstream and fortify docs. Some new to laravel don't even know about jetstream docs.

livewire and inertia have documentation on their own and they have been around over a considerable amount of time. so much to learn for new comers. JS now has become mandatory

JS now has become mandatory

How do you work that out? Nothing has been taken away from you, and Livewire is a no-js philosophy

Too much 'hair on fire' around here

should we hv to read live wire documentation or not

Taylor Otwell Flying saucer @taylorotwell

Changed the wording on laravel/ui README that was making people uncomfortable.

now laravel/ui is considered as a simple scaffolding solution. For more robust consider laravel jetstream

Wow, does that mean it's not deprecated anymore? I wish someone would decide what's what.

I see no benefit of fortify over laravel UI. In fact UI gives developers much more control.

I just wish those new to development would take time to learn security correctly.......

I did miss my AuthenticatesUsers trait. But @snapey wrote a work around to replace redirecting after login depending on role. Was completely missing from fortify.

Edit: I am debating if I should redo with UI. But if I do it will probably get deprecated again. I will probably wait a while.

Just found this: https://laravel-news.com/youtube-jetstream-discussion

@taylorotwell discusses jetstream and confirmed laravel ui will remain in future versions.