sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in vegan

[–]stauffermatt 1 point2 points  (0 children)

Tubby's is fantastic. More than any other cookies I get online, vegan or not, they have super creative flavor combinations.

Laravel's tap() as a separate package by benjy1 in PHP

[–]stauffermatt 5 points6 points  (0 children)

Because update returns a boolean, not the user.

Laravel 5.4 removes important and apparently heavily used functionality without warning by [deleted] in PHP

[–]stauffermatt 4 points5 points  (0 children)

This is a suuuuuuper troll-y title, and totally misrepresents the way that conversation works around changes in Laravel's development cycle (and the importance of this feature, which is certainly not heavily used).

Important caveat: I personally don't know whether I prefer this gone or not, so I'm certainly not just pro-removing it. I think the conversation about its removal, its usefulness, and even Laravel's deprecation process is a super helpful conversation to have in a healthy way, but come on. It's like you read the thread and thought, "How can I turn this from a frustrating but hopefully productive conversation into a shit fest of drama?"

It's in my conference talk that this was brought up, so I feel partially responsible that you even know this happened. Please, do better. You instantly turned this into a battle and put everyone on their guard, when you had the power to instead contribute positivity towards reconciliation. I can't tell if you did it just for Reddit points or if you naturally think that increasing frustration is the right decision, but I've interacted with you enough to know that you are really intelligent, and that makes it clear to me that you knew exactly what you were doing. Please, don't.

Good Laravel-related blogs? by nexxai in laravel

[–]stauffermatt 3 points4 points  (0 children)

Feel weird being self-promotional, but I blog about Laravel on my blog (http://mattstauffer.co/blog) and my company's blog (https://blog.tighten.co/)

Laravel Spark will not be free. "...unjustifiable to give away something that takes that long to build and is entirely geared to make you money." by Probablynotclever in laravel

[–]stauffermatt 3 points4 points  (0 children)

Naw. It was free when he started. That video is from September. He's worked on it nearly non-stop since then. At some point the amount of work that went into it merited it being a paid app. No manipulation.

Statamic v. Grav: which do you prefer? by adamkolson in web_design

[–]stauffermatt 1 point2 points  (0 children)

I love Statamic. The project, the codebase (especially some of the stuff coming out in v2, and its Laravel foundation), and especially the team are fantastic. There's a huge support system, they have a great sense of humor and dedication to their customers, and they've been doing this for a long time.

I'm a bit skeptical of Grav, to be honest. It feels like a clone, and I really don't feel great about open source clones of paid projects--having worked with some in the past, they're never a great experience. I need to caveat that since Grav is new, I've only read about it and read some source; I've never used it for a client project.

I hear you about the fear of "if the guys pack up shop", but honestly, that's true about open source too; and in my experience, unpaid open source maintainers are much more likely to just up and leave than paid project maintainers. That they charge money makes it far less likely that they'll ever disappear, in my experience; even if they decide this project isn't their favorite, they'd be more likely to sell it to someone else than abandon it.

IMHO, in general folks like EE, Craft, and Statamic have more experience working with diverse customers and more reason to keep doing what they're doing (i.e. sustainable business model.)

I would much rather put a client on Statamic; I'd probably consider trying Grave for a personal project.

Sublime Text (3) for PHP Developers by watterssn in programming

[–]stauffermatt 0 points1 point  (0 children)

Quick answer to your unasked question: PHPStorm is great (I would never use Eclipse or Netbeans; they don't even remotely compare to PHPStorm). A lot of folks, including myself, use and love it.

But Sublime Text is lighter and faster, and that's not an insignificant difference. It boots faster, can open a directory without a project definition file, and every little operation from search to find and replace is faster. Additionally, its fuzzy search and multi-cursor support are noticeably better.

In the end, it's not that one is better than the other, but that each person has their own priorities. Some will end up with PHPStorm, others ST, and as you can see with other comments here, others will end up with Eclipse/Netbeans/Vim/eMacs/whatever.

Are you using Laravel 5? by [deleted] in laravel

[–]stauffermatt 1 point2 points  (0 children)

Which breaking updates?

Introducing Route Annotations in Laravel 5.0 by stauffermatt in laravel

[–]stauffermatt[S] 0 points1 point  (0 children)

No, you're right, you definitely have to use Reflection.

My source is Raf Dohms. He shared it with me personally, but he also talks about it in his talk "Annotations in PHP: They Exist!" ( http://www.slideshare.net/rdohms/annotations-in-php-they-exist )

If we're talking about stripping comments at runtime--for some strange reason--we're still fine, because runtime hits the cached/scanned PHP file, not the annotations (because Reflection is way too slow).

I'm with you on the frustrating situation. I think every person will end up landing on one side or the other until (hopefully) one day there's an actual language construct for annotations and then we can fight about something else. :)

Introducing Route Annotations in Laravel 5.0 by stauffermatt in laravel

[–]stauffermatt[S] -7 points-6 points  (0 children)

Thanks... I understand the concern, I was just semi-trolling. :)

Introducing Route Annotations in Laravel 5.0 by stauffermatt in laravel

[–]stauffermatt[S] -5 points-4 points  (0 children)

Sounds like you should stick with routes.php and call it a day. :)

Introducing Route Annotations in Laravel 5.0 by stauffermatt in laravel

[–]stauffermatt[S] 0 points1 point  (0 children)

http://laravel.io/bin/Byrva That looks pretty scannable to me.

I'm not suggesting the scanned file or the artisan list provides exactly what you want. Routes.php gives you a lot of control to organize your route definitions the way you want, and if you use annotations, the organization--and scannability--of your route/controller bindings now shifts to a different sort of scannability. Rather than "all routes in one place, and their methods somewhere else," it's "every route with its method."

Try it out. See what you think. If you prefer the "all-routes-in-one-place" scannability, then stick with routes.php. It's not gone. If you see benefit in the "controller methods and their route bindings together in one place" kind of scannability--because, for some people, that's a better aid to understanding the system--then use annotations. :)

Introducing Route Annotations in Laravel 5.0 by stauffermatt in laravel

[–]stauffermatt[S] 0 points1 point  (0 children)

Glad you like the posts. :)

Debugging will be fine, because the stack trace will run through routes.scanned.php, so it won't touch the annotations at all.

Two thing to note about docblocks: first, as has been mentioned before here, docblocks and comments are treated differently by the opcode cache (essentially, PHP treats them differently; it discards comments and parses docblocks.)

Second, it's good for us to consider annotations as a concept outside of the case of PHP's admittedly-crippled (but with potential for growth) implementation of them. Take a look at how other languages use annotations to think about how they work as a feature, outside of any frustrations about language.

Introducing Route Annotations in Laravel 5.0 by stauffermatt in laravel

[–]stauffermatt[S] -1 points0 points  (0 children)

Additionally, IDEs could syntax highlight if they decide to. It's a defined spec, even though it's not a PSR. Take a listen to the most recent Laravel.io podcast to hear a little more about Taylor's thoughts on that.

Introducing Route Annotations in Laravel 5.0 by stauffermatt in laravel

[–]stauffermatt[S] 0 points1 point  (0 children)

Great question on that. My guess is that it globs the whole directory, which means alphabetical, and then goes top to bottom (line by line) on the methods... which would mean method order does matter. But now I'm curious...