How many other Frameworks offer LTS releases? Plenty are mature enough to offer this, but commercial backing must be hard to come by.
Regarding Python, Django does LTS releases.
Laravel 5.1 with LTS is released
11–20 of 57 posts
Re: Laravel 5.1 with LTS is released
#12http://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.
Re: Laravel 5.1 with LTS is released
#13Just 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.
Re: Laravel 5.1 with LTS is released
#14http://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.
Annoyingly I just set up a Laravel install for evaluation on OSX and wrestled with getting mcrypt to work!
Re: Laravel 5.1 with LTS is released
#15By extension, would Lumen (Laravel's micro framework sibling) also now have LTS releases?
Re: Laravel 5.1 with LTS is released
#16This 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.
Re: Laravel 5.1 with LTS is released
#17http://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.
Annoyingly I just set up a Laravel install for evaluation on OSX and wrestled with getting mcrypt to work!
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...
Re: Laravel 5.1 with LTS is released
#18This 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.
Re: Laravel 5.1 with LTS is released
#19Earlier quoted context omitted.
Annoyingly I just set up a Laravel install for evaluation on OSX and wrestled with getting mcrypt to work!
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...
> If mcrypt is such a pain for OSX users
It's not, if you're using Homebrew (which you should be). `brew install php56-mcrypt` and you're done.
Re: Laravel 5.1 with LTS is released
#20Earlier quoted context omitted.
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...
> If mcrypt is such a pain for OSX users It's not, if you're using Homebrew (which you should be). `brew install php56-mcrypt` and you're done.
I am using homebrew but it definitely wasn't that simple. I think it was because my OSX (for some reason) wasn't using the right PHP version and so installing mcrypt from homebrew didn't have any effect until I reconfigured apache.