PHP Reddit – Telegram
PHP Reddit
33 subscribers
293 photos
37 videos
24.9K links
Channel to sync with /r/PHP /r/Laravel /r/Symfony. Powered by awesome @r_channels and @reddit2telegram
Download Telegram
Ae you bullish on Laravel?

Howdy r/Laravel!

As the noscript states, I’m curious about the fine folks here opinion of the future of Laravel in terms of community and job security. TL;DR at the end, but to summarize the massive wall of text below, I’m a .NET/TS dev looking to make the jump to Laravel/PHP.

Some background:

I’m coming up on almost a decade of employment as a professional developer. The majority of my time has been spent in .NET, Java, and JS/TS. I’ve even had a brief stint working on embedded systems, and have worked up and down the stack, from the frontend down the depths of DevOps and databases.

The last four or five years of my career, I’ve been primarily working in the Microsoft™️ stack, and to cut a long story short, I’m growing fairly disdainful of it as the days go on. Everything these days just feels so… Microsoft-y. Don’t get me wrong, I love C# as a language, but I’m burning out on the typical way over engineered enterprise-y apps that I work on that have been hacked on by thousands of devs over the years to create an amalgamation of absolute code chaos.

I picked up PHP and Laravel about two years ago while on paternity leave to learn something new and keep myself sane. That quickly grew into an obsession and I’ve been spending damn near all of my spare/open source time writing PHP. Small utility packages, Laravel side projects and libraries, and even small business websites around my town with Statamic. I’ve been watching every Laracon talk and trying to be somewhat active in the Laravel communities on Discord/X/Bluesky.

I’ve been loving the solo builder/entrepreneurial spirit of Laravel and its ecosystem, identifying more with its community and general sentiment that that of .NET. In essence, I’m all in on Laravel.

I never took a “real” chance at Laravel jobs until recently, and after punching out a few applications, I have a pretty good response rate so far and have some interviews lined up. I’ve been pretty picky about the jobs I’ve been applying too as I can’t afford to take a pay cut at the moment being the sole breadwinner between my wife and I. I’ve noticed that PHP/Laravel salaries tend to be a good bit below the .NET/TS market for developers, and I’m nervous about taking a jump if the opportunity presents itself to side step (pay-wise) into a Laravel role.

I have an opportunity with a company that seems pretty cool and tapped into the Laravel community. My nervousness is kicking in though as I’ve only been at my current company for about 9 months, a gigantic F500 with a mega old legacy monolith that I was baited to working on. The promise was working on newer microservice-based stuff, but that hasn’t come to fruition and is not looking likely in the near future. Pile on a metric shitload of red tape and bureaucracy, and I’m basically a well paid code janitor at the moment. It’s done nothing but accelerate my growing annoyance of .NET and its surrounding ecosystem.

With all that said, I’d love to get the community’s opinion(s) on Laravel and PHP, from past, present and future. Do you feel like the growing momentum Laravel has had over the past few years will sustain? In your opinion, what’s the outlook of PHP and Laravel over the next few years?

Thanks everyone!

TL;DR - I’m a TS/.NET career sellout and want to transition into Laravel/PHP. I have an opportunity to do so, but I’m getting cold feet.

https://redd.it/1iwp0o4
@r_php
Weekly Ask Anything Thread

Feel free to ask any questions you think may not warrant a post. Asking for help here is also fine.

https://redd.it/1iwtfg5
@r_php
Weekly help thread

Hey there!

This subreddit isn't meant for help threads, though there's one exception to the rule: in this thread you can ask anything you want PHP related, someone will probably be able to help you out!

https://redd.it/1iww2wk
@r_php
Tempest alpha 5 is now released with PHP 8.4 support, improved console styling and components, Vite support, and much more
https://tempestphp.com/blog/alpha-5/

https://redd.it/1iwwytz
@r_php
Laravel Cloud - Hype train "woo woo!"

Anyone else super hyped for the Laravel Cloud release today? Can't wait to be a Guinea pig :-)

https://redd.it/1iwzzwi
@r_php
New Laravel website. First impressions.

First impression ? Bad.
After re-evaluation? Fu*king horrible.

Hijacked scroll, you need to scroll 5 times to move out of a section.
Page down to navigate? Good luck, you will "miss" information that's only visible after you "scroll" a specific section of the page.


Mobile ? I am not even going to start here.

Disc: This is my opinion and does not reflect the opinion of any of my peers.

https://redd.it/1ix4g5k
@r_php
Am I the only a bit sad that there is no more a classic Blade MVC starter-kit?

I skimmed through the new starter kits (React, Vue and Livewire) and I like the idea. I think they partially solve the fragmentation problem and confusion that Breeze + Jetstream caused when first launched.

However, I think that they overcomplicate things and for simple applications they are an overkill. I liked the Blade template for breeze because it was "a breeze" to install and super simple to get started with classic MVC apps. Now there is no more a classic MVC approach and I think it would be great to have that for simpler apps that have a lot of backend logic but not too much reactivity.

What do you think?

https://redd.it/1ix6uox
@r_php
Are you worried about the Laravel Ecosystem becoming oversaturated?

We've got Livewire, Inertia, Jetstream, Breeze, Volt, Forge, Vapor, Cloud, and the list goes on.

I get that these tools were designed to solve specific problems, but I worry that as the ecosystem continues to grow, the skill requirement to build Laravel applications will continue to grow.

I'm not saying that we need to go back to basics, or that the Laravel community needs to pick a single stack. But with all of the product names being thrown around, I'm starting to see people getting confused.

I feel like this problem gets exasperated when some of these products feel minimally maintained over time. When's the last time we saw a meaningful update to Horizon, Dusk, Pennant, Mix, or Telescope? Did anyone notice that Laravel Spark isn't even in the product list anymore?

I worry that some of the new features and products coming out are hype trains. I get that they provide value and the Laravel team worked hard on them, but will they see significant additional features, or just minimal maintenance?

What are your guy's thoughts on the direction of Laravel in the recent years? Do you guys share the same concerns?

https://redd.it/1ixmd09
@r_php
Integrating AI into the framework

I was thinking , that AI can integrated in this framework , or other framework, or maybe this thing already exist.
Like for example in debugging, there is an error page that display the error message and file. sometimes it's something simple that a was solved many times ago , and a prompt to ai can solve the problem in minutes.
It can be used to suggest corrections and implement them in a click.

another example is the maker, the code generator , it can be more intelligent , and provide more options to generate every component , improve components , in the command line.

what do you think? is it a good idea? is it something that you would like to see in the future?

https://redd.it/1ixqqlj
@r_php
Filament v4 - overall changes and timeframe?

I could not find any timeline mentioned on the Filament site or the v4 alpha GitHub repo.

Also, I want to confirm before I embark on a large project -

\- I know Filament v3 won't work with Tailwind v4. Should I still start off with Laravel V12, and downgrade Tailwind (which I guess means removing it, then re-installing 3.x, to get it to load as Laravel V11 was doing)? OR, should I only use Laravel V11, for that and maybe other reasons? (I am not sure that I will miss out on anything by using V11, although I'd like to know I'm on the version with the longest support timeframe... then again, V12 is a day old, so it might be foolish to use it now.)

\- will it be hard to update to Filament v4? I didn't have time to read all the changes in GitHub, but it seemed a lot of them are smaller updates, not differences in the way it works.

\- any other tips about anticipating Filament v4 would be useful (any groundbreaking new features, or features or practices that will become discouraged/deprecated)


Thanks to anyone who might know any or some of these answers!

https://redd.it/1ixuc04
@r_php