Hacker News new | ask | show | jobs
by chiefalchemist 2705 days ago
As someone who recently took on the Laravel learning curve, be aware that Laravel moves atypically fast. That is, something in say version X.Y might be different in X.Y+1 or Y+2. That ends up manifesting itself as a lot of noise when you're asking The Google for help.

It can be frustrating. When you're on a deadline it can be unnerving and then some.

2 comments

Ha ha. Joke's on me. I just inherited at 3.x site. Getting it upgraded to 5.5 looks like it will be a half-total rewrite.
If you can get it to 4.2, you may find this helpful: https://laravelshift.com/
That's true for additional features, but rarely does documented behavior change in a point release. That usually only happens when there is a security bug.
That’s not true. It happens quite often. Variables, classnames, php targets are changed on a whim.
More than twice The Google found me solutions that were out of date by Y+1 or Y+2.

I finally got into the habit of making sure what I found was current. But that doesn't prevent so much noise in the Laraval + The Google signal.