Sorry theshiftexchange but your argument flies right out of the window when you realise echo still works in Laravel (obviously) and again, it is so easy to switch back to the 4.x way. If security is the reason then surely rolling back this 'feature' shouldn't be so easy? The top and bottom of it is that writing more secure ways of dumping data on a screen isn't going to help much if the insecure ways still exist. And aren't the insecure ways still needed?

To me this just isn't making sense, but hey, I give up, so long as switching back remains compatible then I'll just have to use that. Just another step I have to take before using what is essentially a great framework. Besides, sitting here arguing the point isn't going to change a thing eh? :)

@cooldot: I think you're misunderestimating the power of defaults, and how quickly people will abide by a default. I like the "the right way should be the easy way" paradigm and this one gets closer to it. And yeah, you can still run off the path, but it just got a little harder.

Well I must be missing something! :)

Okay, so we had 'defaults', they were {{ }} for raw and {{{ }}} for escaped.

We now have {!! !!} and {{ }}

Okay, so there is a debatable advantage in that one is harder to type than the other, but I doubt that will stop the mistakes. Personally, I never had a problem spotting the difference between {{ $me }} and {{{ $me }}}.

What's the difference? Other than a load of incompatibility within existing projects and what people have learnt already. We have the same risk, we have the same knowledge of the problem, we have the same chance of making a mistake and, as an added 'bonus', confusion amongst many people who are wondering why their output is up the spout, until they realise that a fundamental has been changed to it's exact opposite ({{ now escapes output).

When I began learning Laravel {{ and {{{ made perfect sense. {{ would output, while {{{ would do the same with an extra level of security. It even looked logical. Now we have {{ which no longer does what it used to do and {!! which almost bears no relation to it's 'sister' operation. Strange, since Laravel was touted as a framework that has great looking, easy to read code. To me it's as if Blade just took a small step back from this.

Remember though - Blade is optional, so being a little harder to 'run off the path' is only ever going to be relevant when using Blade. When not using Blade, well, then I guess we'll have to stick with good old 'insert your preferred bareback function here' and have a good understanding of the problem at hand (as we should any way). Unless we use some other front end wizardry.

Speaking of defaults (and the power of), if you think {{ and {!! is safer than the old way, then why isn't the default view that's installed with Laravel a Blade template? After all, if we stick with the default and use the default view, our options are what? Do I hear an echo?

As I said earlier though, we could go on about this for a month and still be no further forward. I'm not going to lose sleep over this, I'll simply override back to the old way when I have to (probably when converting older projects), which keeps things just a little more compatible across versions.

Horses and courses I guess, personally, I still think it's a lot of confuddle for a questionable advantage. Although, a year down the line, when there are no more projects to be converted and everything has settled down, I could well agree with you :)

I would like to mention that you can make phpstorm recognize the new blade escaped tag by going to Preferences > Languages & Frameworks > PHP > Blade and setting Start: {!! and End: !!} under Text tags > Escape tags. This will fix the formatting of blade in PHPStorm for escaped characters. This works in PHPStorm 8.0.2 and above.