Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Laravel 5.1 with LTS is released

laravel-news.com

Post reply on HN
Print view View original

41–50 of 57 posts

Re: Laravel 5.1 with LTS is released

#41

Post by Killswitch »

bovermyer wrote: post #38
Killswitch wrote: post #35

Earlier quoted context omitted.

Chris, I agree with you completely. I also suggest this beaut: https://github.com/fideloper/Vaprobash wink wink, hint hint.

An idempotent provisioner would be a better option. Ansible is my favorite.

I've tried Ansible and Puppet, but I just never could get used to them or like them. I like the shell provisioner because I know EXACTLY what it's doing. I can provision a server myself, I have the knowledge and understanding to. I can type up the commands in a bash script to provision it faster than I could learn exactly what Ansible or Puppet or Chef are doing when I tell it to install Nginx.

Re: Laravel 5.1 with LTS is released

#42

Post by Moru »

bpicolo wrote: post #30
darkhorn wrote: post #23

Why space? Why not tabs? Why do I need to press 10 times space instead of 2 times the tab?

Every editor in existence supports pressing tab to insert spaces and correctly handling backspace in those instances

Yes, even my Atari could do that.

Re: Laravel 5.1 with LTS is released

#43

Post by sarciszewski »

fweespeech wrote: post #40
sarciszewski wrote: post #4

Earlier quoted context omitted.

It's actually 2 years of updates + 3 years of security updates.

A web framework that no longer is accepting bug fixes isn't really supported. So yes, its only supported for 2 years.

https://php.net/supported-versions.php

PHP versions offer 2 years of support + 1 year of security fixes. So it doesn't really make sense for a PHP project to offer longer support.

Re: Laravel 5.1 with LTS is released

#44

Post by ceejayoz »

zefman wrote: post #33
romanovcode wrote: post #22

Earlier quoted context omitted.

This command has been removed since like half year ago. https://github.com/laravel/framework/commit/37ebc7ecc693405a...

No it hasn't https://github.com/laravel/framework/blob/5.1/src/Illuminate...

Heh, apparently it's going away. Again.

https://github.com/laravel/framework/pull/9161

Re: Laravel 5.1 with LTS is released

#45

Post by jbrooksuk »

jbrooksuk wrote: post #37
ceejayoz wrote: post #18

Earlier quoted context omitted.

`php artisan fresh` removes a lot of the default files. They're intended as a starting point for new users but are entirely removable.

Looks like the Fresh command wasn't registered in the ArtisanServiceProvider. I have a PR open to fix this. https://github.com/laravel/framework/pull/9161

Nope, looks like the command should have been removed anyway... https://github.com/laravel/framework/pull/9161#issuecomment-...

Re: Laravel 5.1 with LTS is released

#46

Post by fweespeech »

sarciszewski wrote: post #43
fweespeech wrote: post #40

Earlier quoted context omitted.

A web framework that no longer is accepting bug fixes isn't really supported. So yes, its only supported for 2 years.

https://php.net/supported-versions.php PHP versions offer 2 years of support + 1 year of security fixes. So it doesn't really make sense for a PHP project to offer longer support.

1) They aren't lining it up with PHP version support which means if that was their justification, they didn't think it through at all.

2) That doesn't make it long term support.

3) > Since originally launching in 2011, Laravel has always followed the “release early, release often” mantra which is popular in open source applications. With the historic rise in popularity of the framework, it was time to start focusing on the needs of large organizations and mission-critical applications that need security fixes but can’t upgrade quickly. Laravel 5.1 will now include 3 years of security fixes.

The logical way to have handled this if that was the reasoning would have been to say "Laravel 5.1 will be supported until Aug 2017 to line up with the PHP release cycle and provide a stable platform for large organizations along multiple levels of their tech stack.

As each version of PHP is released, we will release a LTS support version of Laravel in sync with PHP's cycle within X months."

That isn't what they did and that is not what they communicated in any, way, shape or form. It doesn't line up with PHP's release cycle, it doesn't have the coverage needed to be truly LTS. It isn't like PHP has breaking changes in every point release.

Re: Laravel 5.1 with LTS is released

#47

Post by thethimble »

sirstompsalot wrote: post #34
fideloper wrote: post #32

Earlier quoted context omitted.

This comment makes no sense. Well, it makes sense, but I don't believe it comes from someone who's really considered what they're saying. First, it's PHP. Same situation with Ruby and Python. All generally slow as a glacier (obvious exclusions being different implementations of said languages). Developers' focus on code speed is ridiculous (is that too strong a word?) due to relative inexpensiveness of "hardware" and…

Great response, and you make a great point - focus on coding speed is a great reason to choose Laravel. It's also hugely popular and now with it's LTS, it's going to be around for a while. For me personally, I was a ZF 1.x guy; when I started a new project I chose Laravel, and it was a dream - crazy zippy (compared to ZF). But as I started to do more with it, I started to need to reduce my feature set, implement perf…

We're doing 2k req/s with Laravel for one of our API services. In order to maintain ~150ms of latency, this takes us ~14 c3.2xlarge boxes in a load balanced environment. We've done a lot of tuning to squeeze this much out of the boxes (nginx + php fpm) but ultimately I feel pretty let down by laravel/php. ~150 req/s per c3.2xlarge box is very disappointing. I'm hoping to migrate off and go with something like Scala+Play or even Go perhaps.

Re: Laravel 5.1 with LTS is released

#48

Post by sirstompsalot »

thethimble wrote: post #47
sirstompsalot wrote: post #34

Earlier quoted context omitted.

Great response, and you make a great point - focus on coding speed is a great reason to choose Laravel. It's also hugely popular and now with it's LTS, it's going to be around for a while. For me personally, I was a ZF 1.x guy; when I started a new project I chose Laravel, and it was a dream - crazy zippy (compared to ZF). But as I started to do more with it, I started to need to reduce my feature set, implement perf…

We're doing 2k req/s with Laravel for one of our API services. In order to maintain ~150ms of latency, this takes us ~14 c3.2xlarge boxes in a load balanced environment. We've done a lot of tuning to squeeze this much out of the boxes (nginx + php fpm) but ultimately I feel pretty let down by laravel/php. ~150 req/s per c3.2xlarge box is very disappointing. I'm hoping to migrate off and go with something like Scala+P…

Yeah, that's the same conclusion that I came to myself. In my past experience the bottleneck is almost always the database but throw in Laravel and it takes some serious hardware just to stay afloat.

I recently started thinking about switching languages and like everyone I know I started with Node.js first. I found myself rapidly infuriated with it and decided to try out Go. I wrote a quick S3 upload demo app just to grok it and I was thrilled with the results. Scala outperforms Go but I like Go a little more for rapid app dev. If you decide to take the plunge do let us know how it goes!

Re: Laravel 5.1 with LTS is released

#49

Post by fideloper »

thethimble wrote: post #47
sirstompsalot wrote: post #34

Earlier quoted context omitted.

Great response, and you make a great point - focus on coding speed is a great reason to choose Laravel. It's also hugely popular and now with it's LTS, it's going to be around for a while. For me personally, I was a ZF 1.x guy; when I started a new project I chose Laravel, and it was a dream - crazy zippy (compared to ZF). But as I started to do more with it, I started to need to reduce my feature set, implement perf…

We're doing 2k req/s with Laravel for one of our API services. In order to maintain ~150ms of latency, this takes us ~14 c3.2xlarge boxes in a load balanced environment. We've done a lot of tuning to squeeze this much out of the boxes (nginx + php fpm) but ultimately I feel pretty let down by laravel/php. ~150 req/s per c3.2xlarge box is very disappointing. I'm hoping to migrate off and go with something like Scala+P…

Hey, that's really interesting! Is that laravel specific or is that general with PHP (frameworks) in general? Would love to know more about that and your setup/tuning.

(Also wonder how well php7 will help that out).

I think at that scale, it's certainly reasonable to try getting away from PHP.

Re: Laravel 5.1 with LTS is released

#50

Post by fideloper »

bovermyer wrote: post #38
Killswitch wrote: post #35

Earlier quoted context omitted.

Chris, I agree with you completely. I also suggest this beaut: https://github.com/fideloper/Vaprobash wink wink, hint hint.

An idempotent provisioner would be a better option. Ansible is my favorite.

I've made that too: https://github.com/vagrant-ops/vagrantops (although work in progress, and I have some sneaky/evil/delicious plans for it)
Post reply on HN