Live data from Hacker News

Laravel 5.1 with LTS is released

laravel-news.com

31–40 of 57 posts

Re: Laravel 5.1 with LTS is released

#31
I'm super excited about Laravel 5.1

We've been using it with Cachet (https://github.com/cachethq/cachet) for a couple of weeks. Mainly it was to make testing our API easier, the new PHPUnit extensions are so freaking amazing - it makes unit testing a dream.

Other than that, other cool features I like are the LTS, dropping of the mcrypt extension requirement and also the broadcasting feature (which is worth checking out btw)

Also this release contains some code that I've committed too, which is always a nice feeling :)

Re: Laravel 5.1 with LTS is released

#32

Too bad it is still slow as a glacier.

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 the "fact" (yep, fact) that code is for building value.

In most cases, that value is provided via an automated service. Speed of that automation is typically not critical (obvious exclusions being something like medical equipment or stock trading, or making people wait ridiculous seconds after clicking a button. Please don't Well Actually™ me to death with pedantry).

Re: Laravel 5.1 with LTS is released

#33

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.

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...

Re: Laravel 5.1 with LTS is released

#34

Too bad it is still slow as a glacier.

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 performance "features" just to retain a measure of speed.

Is 5.x faster than 4.x? Sure. Does it include batteries and the kitchen sink? You bet. Do I still prefer a faster framework like Phalcon and implement the features I miss myself? Damned skippy.

Re: Laravel 5.1 with LTS is released

#35

Earlier quoted context omitted.

Annoyingly I just set up a Laravel install for evaluation on OSX and wrestled with getting mcrypt to work!

IM(not so H)O, wrestling with Mac is not worth anyone's time. Using Vagrant or a similar VM setup will get you in an environment much more like "production" and with fewer headaches caused by mac's special snowflake OS. (I personally use Mac as my host OS, because I love it, except when it comes to installing server software).

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

Re: Laravel 5.1 with LTS is released

#36

Too bad it is still slow as a glacier.

Have you seen any benchmarks? Route and config caching is a huge improvement in 5.0

Yes, I have seen 5.0 benchmarks and even run some boom tests myself (admittedly nothing in a terrible amount of depth). The one I can cite offhand is this one http://blog.a-way-out.net/blog/2015/03/27/php-framework-benc...

I'd be happy if you could link the benchmarks you have seen that demonstrates performance increases.

Re: Laravel 5.1 with LTS is released

#37

This is a great idea. My main gripe (on a very short evaluation) with Laravel is that the default application that artisan gives you comes with a lot of files dotted around the directory structure. With something like Rails these tend to be locked away in a gem and so when using CTRL+T (or similar) you get a lot of cruft popping up. That said I do like the things that Laravel gives you out of the box like auth and th…

`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

Re: Laravel 5.1 with LTS is released

#38

Earlier quoted context omitted.

IM(not so H)O, wrestling with Mac is not worth anyone's time. Using Vagrant or a similar VM setup will get you in an environment much more like "production" and with fewer headaches caused by mac's special snowflake OS. (I personally use Mac as my host OS, because I love it, except when it comes to installing server software).

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.

Re: Laravel 5.1 with LTS is released

#39

As interesting as LTS support is, 2 years is frankly very short. I'm used to thinking of LTS support in terms of 4-5 years. I suspect everyone else is too and Laravel is going to piss off everyone who doesn't read the fine print.

> I suspect everyone else is too and Laravel is going to piss off everyone who doesn't read the fine print. If I'm on a project where LTS matters I'd not be doing my job if I didn't read the small print .

I'd say that to the people that complain about MongoDB's default configuration in the early days but many people feel perfectly justified in that position.

Re: Laravel 5.1 with LTS is released

#40

As interesting as LTS support is, 2 years is frankly very short. I'm used to thinking of LTS support in terms of 4-5 years. I suspect everyone else is too and Laravel is going to piss off everyone who doesn't read the fine print.

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.
Post reply on HN