Laravel 5.1 with LTS is released

https://laravel-news.com/2015/06/laravel-5-1-released/

by ericbarnes • 11 years ago

81 55 11 years ago

laravel-news.com

ericbarnes2• 11 years ago

Being the first release offering LTS is fantastic news for the community.

fweespeech4• 11 years ago

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.

sarciszewski4• 11 years ago

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

fweespeech4• 11 years ago

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

romanovcode3• 11 years ago

2 years for bug fixes, 3 years for security fixes

noir_lord2• 11 years ago

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.

fweespeech4• 11 years ago

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.

Olap84• 11 years ago

How many other Frameworks offer LTS releases?

Plenty are mature enough to offer this, but commercial backing must be hard to come by.

gondo• 11 years ago

staying in PHP world, Symfony2 does http://symfony.com/doc/current/contributing/community/releas...

speg• 11 years ago

Leaving the PHP world, Django does: https://docs.djangoproject.com/en/1.8/internals/release-proc...

mtbcoder2• 11 years ago

Regarding Python, Django does LTS releases.

sarciszewski4• 11 years ago

http://laravel.com/docs/5.1/releases#laravel-5.1

    In previous versions of Laravel, encryption was handled by the
    mcrypt PHP extension. However, beginning in Laravel 5.1, encryption is
    handled by the openssl extension, which is more actively maintained.

This is easily my favorite aspect of the new release. Please, everyone else, follow their example and stop using mcrypt in your projects.

colinramsay3• 11 years ago

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

sarciszewski4• 11 years ago

Sorry to hear that.

If mcrypt is such a pain for OSX users, I might offer to refactor some other frameworks' libraries to use openssl in the near future.

Why mcrypt sucks: https://paragonie.com/blog/2015/05/if-you-re-typing-word-mcr...

fideloper5• 11 years ago

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

noir_lord2• 11 years ago

Just upgraded a large 5 to 5.1 codebase in under 5 minutes (4 of that was composer ;) ) and everything passed functional testing.

Outstanding work and the new docs are an excellent improvement.

mtbcoder2• 11 years ago

By extension, would Lumen (Laravel's micro framework sibling) also now have LTS releases?

fideloper5• 11 years ago

It will use 5.1's base libraries, so "yes" (with air quotes).

colinramsay3• 11 years ago

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 the command pattern.

ceejayoz3• 11 years ago

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

romanovcode3• 11 years ago

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

jbrooksuk4• 11 years ago

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

sirstompsalot4• 11 years ago

Too bad it is still slow as a glacier.

jbrooksuk4• 11 years ago

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

sirstompsalot4• 11 years ago

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.

romanovcode3• 11 years ago

Probably not when it's running on HHVM, it has 100% integration with it.

fideloper5• 11 years ago

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

sirstompsalot4• 11 years ago

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.

spronkey• 11 years ago

For any nontrivial service that wants to build a large audience, something with the glacial performance of Laravel (and I use Laravel, so I'm not completely knocking it) has the downside that things you would normally do when much more mature crop up earlier. Like having to worry about horizontal scaling, or rewriting parts of your app in another language.

I'm not quite sure where L5's performance gets sunk so badly, but it really is a lot slower than earlier variants of the framework. About the only thing slower is Rails, really!

... and unlike Rails, Laravel hasn't had the stability and ecosystem to make those things really easy. Hopefully this LTS plan will change that a wee bit, but we'll see.

darkhorn• 11 years ago

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

pestaa• 11 years ago

If you're pressing spaces to align indentation, you're doing it very, very wrong.

ericbarnes2• 11 years ago

Because that's what the PHP community decided with PSR-2. It's an endless debate. :)

bpicolo• 11 years ago

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

Moru• 11 years ago

Yes, even my Atari could do that.

jbrooksuk4• 11 years ago

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 :)

Laravel 5.1 with LTS is released

Related Stories