Earlier quoted context omitted.
That's a shitty explanation for dropping Whoops. The first time I remember the discussion of it being dropped got brought up was because of a bug in the framework relating to the assets, where Taylor didn't hesitate to blame Whoops and deleted comments on Github pointing out that the problem was actually in his own code. It would've been super easy to add some code that sets the HTTP code for Whoops's response if tha…
You can easily change the config to make the Blade tags work as they previously did. I'm unhappy about this change as well though. It's very reminiscent of some design decisions PHP has taken: 1. Create feature X. 2. Users don't understand feature X, and use it when they should be using feature Y (for safety.) 3. Update the API so that feature X does what feature Y did, and create feature Z that now does what feature…
> In Laravel 4 Blade included the following two styles: {{ and {{{. > The double curly bracket was a raw echo and the triple curly bracket escaped. > > Now both the double and triple curly brackets escape the variable and a new {!! $var !!} is for raw.
I'd argue that having unescaped output be shorter/easier than escaped output was probably a design error in earlier versions -- but I'm not sure I like the "fix"... If it was a green-field design, I must admit I like the "danger!"-feel that unescaped output has in L5 though.