I want to start I have done some raw php at school, which laravel stack should I use as a somewhat beginner in web development? Also, does laravel fix full page refresh? Also I've only use a little Javascript for front end but I hate it
@@hungry_khid1007 you'd better start without starter kit so you won't get confused in the beginning. There are some tutorials on RU-vid. You're welcome.
@@hungry_khid1007 I think the stack that you use depends on what you want to achieve. We use Laravel, with either Inertia+Vue for the more bespoke User front-end, or use Filament PHP for the admin side of the apps I work on. I would recommend checking out Filament PHP, since you can code entirely in PHP (it uses Laravel Livewire under the hood, which I am fairly basically skilled in). Bear in mind, filament PHP is more for building apps, if you want to build a really beautiful interactive website I don't think you can do it without Javascript (not in a meaningful way). Both of these frontends avoid full page refresh most of the time.
@@hungry_khid1007 you should search on google for laravel bootcamp, and try it. this will answer almost all your question. About full page refresh, you also will find the a answer, however you should try with js + xhr / fetch / axios or with a solution like htmx. ;)
Laravel is on a different level, it's already incredible before even more so today. Everything is just easy with Laravel when it comes to web development.
8 дней назад
After 14 years as a web developer I finally decided to create something with laravel last month and basically that's the only thing I'm doing since
People confuse paths. Enterprise developer; full stack midsize; freelance developer; startup developer All have common denominators but are very different. Influencers like being controversial for views and confuse newbies. Rough times.
@@TravisMedia I wasn’t strictly talking about this video/you even tho you bashed .net because of Microsoft even though the documentation is comprehensive. But my point was these are all tools it’s not one or the other. Saying a shovel is better than an excavator because it’s ergonomic is not only wrong but short sited. I like your videos. I just wanted to share that with the channel.
What people like about PHP (and Ruby for that matter) is that Laravel and Symfony are pretty much the defacto frameworks and it’s an easy choice. Composer is the goto package manager. That’s it. With Ruby it’s RoR. With JavaScript, it’s fucking annoying and exhausting all the frameworks du jour. Then you wake up tomorrow and there’s another framework that is trying to supersede the previous ones. Same with the package manager. Which one is it? npm? yarn? pnpm? Make up your fucking mind people! You wanna get people confused and reluctant to your software then give them too many choices and never agree or reach consensus . In fact, fragment your ecosystem amongst frameworks and within your frameworks.
For Web development, Laravel is always my favourite ❤❤. Simple MVC, Clean very fast. Within minutes, your product is accessible on the Web. The Docs cover every aspect of the framework, with bootcamps, great details and we'll structured. Grateful to the Laravel Team & Community ❤❤
I have worked with many technologies and so far i can say that laravel gives me the highest productivity. It is also very nice that the ecosystem is not so fragmented making dependency handling easy
Fantastic docs, smooth framework and Jeffrey Way. I think the fact that Jeffrey Way of Laracasts is one of the best technical teachers on the internet has a huge role to play in making Laravel what it is.
I’m a React/NextJS developer and loving its capabilities. In the past worked with PHP more than a decade and used Laravel briefly (never liked PHP syntax and workflow due to classes and namespaces). But I want to congratulate Laravel team because they used similar hype of JS frameworks with fancy micro service titles, features and branding to revive PHP popularity again. Apparently React’s full-stack approach gave them an opportunity to shine and I must say they do a great job spreading the word.
Sorry I got to the part where you said Laravel didn't have fan bois and I nearly spit out my red bull. That community was the biggest fan community I ever experienced, Taylor "Lambo" Otwell could do no wrong and if you said anything bad about him you were immediately attacked. Super toxic a few years ago.
Hi, Laravel has a good Docs, however Symfony has better. And one thing that almost everyone dont pay attention or dont care, is the fact that laravel under the hood use some components / libs of Symfony. Symfony never was only framework, It has stand alone components and since Symfony version 5 is more like Vuejs, a progressive framework, where in symfony you start only as a router, if you only want as web API, you choose your own ORM or even use it without it. Add a view engine, if you are creating traditional web app, like twig or choose other or go with plain php, your choice. Ssymfony is not bloated when you start, like laravel, symfony start small. And to finish, symfony take advantage on latest feature of PHP when they are available, for example PHP attributes, released on php 8.0, symfony in next version was already use it in the routing system where laravel only now since this month it start take advantage with few attributes, only after 4 years. LOL. 😱
@@ivanjelenic5627 Lol. Recommend you to read the docs of symfony. For me , Laravel only has this 2 positive points better than symfony; - Great integration with modern frontend solutions ( even with some costs over time) - it is thanks to laracast with great and free content, in my opinion, that makes a big diff and of course nowadays exist a lot of content on youtube and on learning plataforms than symfony ( which even has something similar to laracast) With symfony as a framework ( because exist also symfony components which some for example laravel use), give you choices, install it as full framework with everything you already setup and ready to create websites or web apps or start small and simple as router and install only the packages / components you think you need. And your are always using the latest features of PHP. Just see how simple and clean the routing system of symfony is. With laravel, you only have one place and a way to define routes. Be prepare to organize your routes, even routes as resources or groups, always will exist a lot of definitions and you wll have to find a way to organize and keep it clean. This is not a exclusive problem of laravel, this can happen in another php framework like cakePHP, phaconPHP, CI4 (however they have other alternative way to define routes) and even in other framework on js universe backend or frontend. Another problem with laravel: is bloated , even that they start to trim it, However in the wrong way, They should look at what symfony and node js version of laravel, call adonisJS did. Start small and simple. What i mean being bloated ? for example if you are building a Web api, why you need a template engine installed, why you need a package for session or cookies, why you need things related to frontend. The official or not official packages should only be install when you need it. This is a problem on ecosystem of some frameworks on PHP, JS, etc,
PHP Developer for over a decade, almost a year in Laravel, and it is really good. Maybe I don't know about other great tools but this one is sufficient, at least for now.
I don't wish for Nextjs to go full throttle on opinionating stuff, but I wish for more stacks to popup for easier project kick-start. Tho, very few people need to kick-start lots of project in a short period of time.
Great coverage! I’m totally all for batteries-included, convention over configuration. It’s enough already on one’s plate to ship accessible, SEO friendly, responsive apps with decent UX, error handling, appropriate schema designs, integration with 3rd party services, metrics, testing, deployment… That said, I come from using Phoenix (Elixir) which also has excellent docs and conventions, but doesn’t promote a full-suite of great available utilities
2:20 Not to mention if its an SPA like app you want, Laravel has you covered with Interntia for Vue or React front ends, or Livewire's new SPA mode (which while not strictly an actual SPA operates like one by just switching out the parts of the DOM that change instead of a full reload).
Ruby on Rails, the framework that set the standard for MVC frameworks since its introduction in 2005, has been widely influential. If a new developer were to ask whether to pursue PHP Laravel or another path, I would advise them to consider JavaScript technologies like NodeJS, React, and Next.js, along with SQL and NoSQL databases such as MongoDB. This recommendation is based on the earning potential, as developers specializing in these technologies tend to have higher salaries compared to those focusing on PHP-based development.
Also, because JavaScript as a language and skillset is easily transferable to other platforms such as building desktop based applications with Electron and mobile applications with React Native.
I would only consider focusing on JavaScript taking into account the potential to also build mobile apps via React Native and just by sharing components with a web based React application. However, if I’m a solo developer trying to build product, I would just use Laravel or Rails, just because of how quickly you can ship.
As a long-time Ruby developer, I disagree on some minor points 😉, but I'm fully on board with making pragmatic choices that don't depend on the flavour of the month.
i noticed personally, the use of ctrl-shift-f5 has increased for me since the raise of SPAs. which page refresh is worse: the actual needed one or the one i am forced to do bc the FE tries to be clever, fails and gets stuck somewhere??? the latter one is the worse UX as it completely undoes all of the pretended benefits. just fetch the damn page. i can wait.
2:00 wait until people find out that you can use React as the view layer of Laravel (with components, interaction, spa navigation, and everything else), and you don't need to wire up several packages together just to have basic authentication, caching, queueing, mailing, and other stuff that comes out of the box in Laravel.
If you are thinking about Inertia, I'm doing a project with it but I am now thinking about replacing it by just doing classical SPA and Laravel for the Backend I think it's just easier. If you are ok with basically reloading the page on every state update Inertia is ok. But if you have a mix of Ajax calls and page reloads it's hard to master.
@@blubblurb you're not supposed to be getting page reloads when the state changes, but only when navigation occurs. Are you sure you're not using some form of `Inertia.reload()`?
@@rodrigorios78 Oh I do router.reload() on purpose, because I do some Ajax calls and the same page needs to reflect the change of that data. But it would be easier if I could just do the ajax request and change the state after the call using JS. But that's not how it works with inertia. The reload is not really visible for the user, so I don't mind it too much. Simple example, delete an item of the list. Instead of removing that item from the state after the ajax call you would do router.reload() or instead of ajax + router.reload you would do router.visit in one call. But anyway you would usually return the full new state in that call.
SvelteKit DX is just so good. Also, once the client side router loads, its page navigation performance is amazing compared to loading a new page each time.
@@reinhard_silaen it’s still “new” compared to other mainstream frameworks. Svelte 5 is going to have even better performance. I’ve been running my own comparisons of Svelte vs Astro vs Qwik. Yes, the other two have a marginal first time load performance advantage, but after that you’re only loading a few KB at a time. Amazing for slower connections
i love your videos,.... i saved some of your videos in media wallet so i could revisit them for future references. please continue to make these typa content
Big fan of both rails and laravel. One thing I’d say is the “quietness” of the rails community is that it has some benefits. Rails devs have just got their heads down, doing stuff. Once you enter the ecosystem you begin to realise the sheer number of products still built with it. The community itself is incredibly friendly, filled to the brim with knowledgeable people keen to share that knowledge in a positive way. It’s probably the nicest dev community I’ve come across. Even moreso than Laravel, which is also generally very friendly. The thing rails could really do with, is their version of laracasts. Gorails exists but it doesn’t have quite the same energy or coverage
no matter how much you hate js you cant completely ditch js and you dont need fancy frameworks to get job done with vanilla js jamstack you can build any application
While Laravel is fun, and for hobbiest. To be honest, the ecosystem, community ,libraries around React, Angular, Vue, NextJS are much much bigger. The prospect for Laravel in Enterprise apps is tiny
Because nothing can replace js, and it freedom to build your customize app tailored to your needs, lavaral is just too one sided, which is a risk for companies
The job market has definitely seen a downturn, and Laravel seems to be struggling to maintain its relevance. It appears that they’re trying to revive interest by leveraging social media influencers for promotion. While Laravel is a decent framework, it’s extremely opinionated and built on top of PHP, which has a mixed reputation. Over the years, it has improved by incorporating elements from languages like C#, Java, and JavaScript. Personally, I enjoyed using Laravel up until version 7. However, the frequent major version releases one every year have become a significant burden, as they require constant updates to keep your applications up to date. Lack of built-in generics in PHP is one of the things that makes type-hinting in PHP a nightmare. They're still one step behind the big players like Java and C# when we talk about enterprise application.
@@yashuabaryosef4413 great nuanced answer! For large scale, it really does not hold up as well as the likes of Java/modern .net and for smaller, more agile teams…honestly I’d just go with rails now. You don’t have the same development pace in Laravel and despite rails’ reputation, it’s much less restrictive than Laravel and holds together better when you need to do novel things with the framework. If you’re just serving an API, I’d still probably go with rails, I prefer active record to eloquent, rails routing is immensely good and rails is also a little faster than Laravel.
I hate people when they overhype something that isn't worth it. Laravel just does the job, why do people hate it? Some people literally worship JavaScript and other techs like Rust, Ruby, etc..
It's not like many people will use all its features. NextJS, SvelteKit are way simpler and don't throw at me unnecessary features or a complex architecture Also PHP is a joke in static typing when compared with TypeScript
Laravel v5.8 + queue jobs features from the v8 was the best version of Laravel.. basically everything else is just hype inspired from non-stable JS world
No, you must be out of your mind to say thats first time laravel user like it in 2024, because i dont. Its full of abstraction. Its not slow or bad and it has some level of community but i genuinely dont think you should start laravel in 2024 just because of the syntax and weird orm like Eloquent, personally i prefer something like sqlc or prisma. And the server setup is a madness compared to js. You really need to dig up a lot of deps from years ago
The JavaScript route is just too hectic for new aspiring developers. Learn JavaScript, then TypeScript, and then react, then nextJS. It takes eons. I would lose focus and get nothing done. Glad I chose the Python-django route. Now shifting to a new technology feels easy. That's how it should be like.
Never like Ruby either. Used Laravel off on and for years but haven't used it for about 5. Have to disagree about .Net. It may not have all the docs in one place but the support and training for it are everywhere.
What about a social media chatting app, where users can have star progress increase depending on how long they stay on the app. From Novice to legend star progress. 6-7 star progress in between novice and legend. just a simple interface like WhatsApp, users create their group themselves to chat with friends and family. A group where user can boost their star progress also by engaging in ai generated games in different fields. e.g sport, programming etc. leader board page with points earned.
I enjoyed the video, but the idea that "criticisms of PHP are unfounded" is just not true. Maybe dev's feedback should be heard and not dismissed as "hate". The same goes for JavaScript, PHP, NextJS, or any other language/technology. It's always easier to say "hater", than understand where the criticism comes from, because people's intentions are not bad most of the time, they're just expressing they're experience when using a language/technology.
It is unfounded most of the time because people compare it to the wrong things, and for being used for the wrong purposes. And hate? Who said anything about hate? It's just a language
the dumbest propaganda campaign in internet history Laravel is the best thing ever happened to software development, i'm also happy and dying to start a new project and it's fun all the way to the end
@@swfh3542 that’s proportional to the number of jobs available for the languages. In most cases, higher number of job opportunities will get paid low and vice versa, which explains why PHP, the most used language for websites, get paid low. There of course would be other factors too, but that’s the major reason, which really is not bad.
Laravel is an opinionated framework, but the main issue is that it relies on PHP. Looking ahead, the future of PHP appears limited. The JavaScript ecosystem offers a more robust alternative, providing a comprehensive and scalable solution for modern web development needs.
Yes and no. You can’t deny PHP advantage in certain scenarios. PHP process run only on request, PHP process don’t need constant babysitting and it can run on cheap servers.
@@winns.x the facts are the ecosystem of libraries, docs, communities are vast in JS framework and enterprise apps. It is like you use iPhone and Macs for the whole Apple ecosystem. The prospect for Laravel is only for hobbies. and dockerize and initial Laravel setup is no trivial
@@yassinertm it's not a joke, but don't think it just came out of nowhere. I have 12 years of commercial experience in marketing and design. I'm not even anywhere near a good developer though. I just used Laravel to do everything from route management, to cache, queued jobs, and even deployment. Used Inertia.js with React to have an SSR rendered SPA frontend. Used mailables to send emails and notifications. Used Breeze to have an auth system ready in under a minute. Used Reverb for event-based websockets. Used Spike (paid package) for advanced billing. Used Forge and Envoyer for deployment and SSL. Everything just exists in this ecosystem. Saved me so much time on all these things and I could just focus on what matter for my app. Highly recommended if you want to ship fast and see results and not to just waste time with the new "shiny thing". And what doesn't work just use Claude AI and you'll crack it in a hour instead of days.
@@yassinertm I just wrote a detailed comment but YT decided to hide it for some reason. Sometimes it appears after moderation. If it doesn't, well, no time to play with the algo. Just know it's awesome and will save you so much time.
Nope, it was just over hyped and yet all the problems are not discussed because fanboys don't want to talk about it. Still Js comes with PHP its the standard of most PHP devs
They're probably trying. But I doubt they can compete with Laravel at this stage. Laravel has just had 20 times the amount of dev time invested in it. It's older, more mature, and much more money behind it.
@@TravisMedia not baaaad, but i feel like having an instant feedback is a better experience in general, even if the instant feedback is a "skeleton screen"
Django has everything Laravel has without all the comical b*llsh*t! Laravel is always trying to reinvent the wheel and has way too many first-party paid services now it will have its own version of Vercel like soon as well. Vercel marketing is one of the reasons that the Javascript community is so toxic and obsessed with tiny meaningless numbers
fun how people like to get paid for their own work, but when someone does work to save their time, they're not very much into paying for that ;) well no one forces you to use paid laravel tools, nah? you can always write your own, better ones.
