Is Laravel arguably the best PHP framework?
>>60482640
Isn't it just another consumer of symfony?
>>60482640
works for me.
>2000 + a prime number
>still using PHP
>>60482640
PHP? It's 2017 buddy get with the time and use NodeJS.
>>60482640
> php
> the current year
>>60482640
>frameworks
go away Karlie Kloss
not since 2014, they added those providers and other pOOP shit that ruined it, i use codeigniter or phalcon now
PHP > NodeJs
Deal with it.
>php frameworks
>>60482640
It's the most popular and mainly because it's a copy of ASP.NET MVC
Now that .NET Core 2 is out there's really no good reason to use PHP
>>60482756
Yes
>>60484013
>Now that .NET Core 2 is out there's really no good reason to use PHP
there wasn't any good reason to use PHP since the time non-PHP-only hosting became cheap, so like 2010 at the latest
>>60484081
PHP is an acceptable option when the only alternative is C# or ASP.NET
>street shitting framework
Haven't seen so much hate in a while, PHP is maturing and becoming really good by the minute(hopefully not too late).
T. PHP dev
Do not use a framework. I don't even know why anyone would want to use a framework in PHP except the one you wrote yourself.
You can write a simple MVC, hell even gluephp (github duh) is enough.
>>60484834
forgot to add: and use htaccess (or nginx intern shit) to point every url to the index.php. That is fucking it. Done. Nice urls and easy to manage.
>>60484834
>>60484871
You've never had a job have you?
Laravel is pretty good, blade templates work well, database management and migrations are all top notch. It's a very good framework, I would probably say it is the best php framework around right now.
>>60483397
2003?
>>60484991
>>60485040
He means 2097
>>60484834
It's crystal clear you're a NEET
>>60482640
>Using frameworks in 2017 instead of microservices architecture.
>Using PHP or node.js in 2017
Go away.
>>60484108
it obviously isn't the only alternative, but that's a cool opinion I guess
>>60485181
>microservices architecture
>30 HTTP calls on the backend to retrieve data for a single pageload
yay microservices!
>>60484834
>Hey, I'd like to scale my application up to run on multiple load balancing servers but I have no database migration scheme. I guess I'll just do it all by hand cos I'm a fucking moron.
That's you that is.
>>60485221
>doesn't understand the advantages of microservices architecture.
>posts garbage regardless.
>>60485247
Oh please extol the virtues of rebranded SOA to me
>>60485247
I too would like to hear your reasoning. Proceed anon.
>>60485270
>>60485318
I'd rather hear about the advantages of the vertical scaling monolith framework-based garbage will impose.
>>60484771
how is PHP improving at all?
>>60485467
Simplicity and speed of development
No overhead from calls to multiple independent services for a single pageload
No need for the pointless complication of kubernetes or whatever container management shit is the flavor of the week
>vertical scaling
u wot m8?
haproxy + following first rule of 12 factor app
horizontal scaling doesn't get any easier
>>60485617
>Multiple apps sharing the same code is a violation of twelve-factor.
That's your average non-microservice piece of shit.
>No need for the pointless complication of kubernetes or whatever container management shit is the flavor of the week
Go away, pleb. Come back when you've run anything non-joke in production.
>>60485663
>>Multiple apps sharing the same code is a violation of twelve-factor.
I think you're confused as to what "monolithinc app" means
>Go away, pleb. Come back when you've run anything non-joke in production.
Not an argument. Still waiting for you to provide a single advantage of microservices
>>60485725
>I think you're confused as to what "monolithinc app" means
Your average "monolithic app" will have a million endpoints providing ajax garbage for your frontend code. It will probably even include some shit apis for third parties, and it will all be served with the same huge piece of shit of an app, likely constantly hitting a single bottleneck of a database.
>>60482640
CodeIgniter is better.
>>60485834
>Your average "monolithic app" will have a million endpoints providing ajax garbage for your frontend code
So hitting a bunch of microservices for this data is better instead? Not to mention you'll probably use an API gateway to aggregate that data for every call. You're still not solving any problems here, just adding layers of complexity or shifting that complexity around
>a single bottleneck of a database.
Completely separate from the architecture of your application. I'd wager your average microservice setup will fall into this same trap
Once again:
Still waiting for you to provide a single advantage of microservices
>>60486112
Flask FTW.
Micro frameworks are the way to go.
>>60486112
codeigniter is a cute
>>60482640
yo TM
No OP, Symfony is
>>60483397
2001?
>>60488612
>1
>prime
>>60488640
Divisible only by 1 and itself. Fight me, bitch
>>60488660
Bad definition
prime numbers have exactly 2 factors
>>60484991
Actually I am a 30 year old sysadmin, working for nearly 9 years now.
>>60485230
You sound like you have no idea what you are talking about. Not my problem if your 'website' needs longer than (max) 0.2s to load completely.