So, I figured out my Lambda layer issue mentioned in @merge: Bref's runtime build assumes Amazon Linux 2 (not AL2023), so you need to spec AL2 in the function for it to work.
@ramsey@ian@merge I wouldn’t recommend Serverless Framework as it’s a bootstrapped company running out of money with no sustainable business to keep it up
@heiglandreas I dropped my Docker usage in about 95% after buying a MacBook and tbh it’s not so bad. Before that I had used Docker so so long (7 years) that I didn’t realize all non-docker options also improved
@heiglandreas Laravel Herd or Laravel Valet will let you define per-folder PHP version. NVM will let you switch Node version. For local work, any Redis version will do. MySQL is the only one that held me back longer, but with the sunsetting of 5.7 that’s starting to become a non-issue as well.
I will still reach to Docker if I need Postgres, specific MySQL, Elasticsearch, Logstash, etc. but more with the mindset of binding it to a specific local port as a complementary service
@heiglandreas I’ve spent 6 years working on a Windows PC and running everything inside a VM with just Git and Docker installed and then about 1 year on a Linux Desktop before I became an Apple fanboy. Turns out Docker wasn’t really easier, it was just what I was used to for so many years
I’m finally feeling better after my earlier low this week, & I’m beginning to accept that my next job probably won’t involve #PHP.
Before you tell me how good other languages or communities are, understand that I considered my interactions with the PHP community as a second, unpaid role, which I thoroughly enjoyed in an entrepreneurial sort of way. That’s why this is difficult for me.
I would love to find an employer who sees value in that side of me, but I don’t think that’s going to happen.
@ramsey I’m becoming a ultrastack developer now. 13 years experience in backend, 6 years experience in AWS Cloud DevOps and now 6 months experience in Vue. InertiaJS makes it a breeze from a technology standpoint. What’s harder is realizing that taking care everything (ideation, architecture, FE, BE, Cloud, data modeling, logging, diagnostic, support tools, etc) is a tremendous challenge because it forces you to rethink what you thought was “easy on the frontend”
Another week, another opportunity to use @Crell PFA that got rejected. I never needed this until I leaned about it, now it really feels like I’m always needing this.
We need to forbid @Crell from proposing RFCs, because they just show us a wonderful world we can’t have
@heiglandreas@Crell I’ve tried it a few times. The 90’s style of the PHP internals triggers my ADHD and make me useless. I can’t for the life of me submit myself to working with such boring tools and environment and I can’t change it either
Zum Hintergrund: "Clown World" wird als ein Meme und ein Dog Whistle (verstecktes Signal) von Neo-Nazis und sogenannten Alt-Rights verwendet, die u.a. die Vorherrschaft der Weißen durchsetzen wollen. Es gehe auf ein Meme zurück, das mit der Verwendung von honk honk ("HH") als Dog Whistle für "Heil Hitler" verbunden sei.
@larsmb@LorenzMeyer I agree he’s the worse and I would love nothing but Twitter to just crash and become unavailable without recovery. But at this point I tried Blue, Mastodon and Threads and the best Tech content is still at Twitter :(
I'm late to the PSR PER 2.0 party. What does PER mean? Why is this not a PSR-# standard? Is PER-2.0 a continuously evolving standard as new PHP versions release? What was PER-1.0? Was there an in-between version?
@awoodsnet@ericpoe@ramsey@bobmagicii with the amount of tooling our industry has today, I would consider “self-inflicted” any suffering/complaint coming from the inability to search/replace all “4-spaces” indentation into “1-tab”
@grmpyprogrammer I can see how that would hold true, but I’d attribute it more to development hype than DX (my dev happiness comes from DX). I’m often 1 year behind hype and I don’t always jump on them all but spending about 2 months per year improving my DX and taking tech improvements is how I manage to keep 9 months highly engaged and focused on delivering value to the end user
I don’t understand folks getting super-excited that they won’t have to use an XML config file. Is using an XML config file that big of a hurdle to developer happiness?
@ramsey verbose, looks bad, takes too much horizontal space, not as easy to parse as JSON but ultimately a huge chunk of the excitement isn’t just about saying good bye to XML but instead having a good API configuration.
I think I know what you’re talking about and the person driving it would 100% without a shred of a doubt develop a better configuration file even if they used XML
Due to some questionable life choices, I need to use PHP/MySQL for the back end of a simple web app. In particular for user authentication.
I'm coming from Django (which I like) and .NET MVC (which is OK I guess). Which PHP framework will I vibe with the best? I see words like "Laravel" and "Symfony". Are these any good?
@hughstimson@Crell it’s also quite bull. Laravel has the best development experience across the web and has just been featured as potentially the happiest community on GitHub
@rdohms@hughstimson@Crell there is when that’s what those opinions are. I work with Laravel for nearly 8 years and nowhere in my codebase there’s globals or “magic”. Crell is a known Laravel hater and when folks spread hate in the world it’s bound to trickle back. He could have said all the nice things that Symfony has and left Laravel out of it but he can’t miss the opportunity. He’s like an anti-religious fanatic spreading hate because he can’t understand it
I have only recently learned of the "before" attribute in @phpunit. It seems appealing. What I don't get is... why would I ever use setUp() when I can instead use a before method? It seems like the easier, more portable solution in ever case except when I actively want to bypass a parent class's setUp().
@Crell@phpunit I just tried this out to see how it was like and before() runs before setUp. Laravel uses setup() to prepare the container and everything so there’s basically no way to use before given the amount of testing features Laravel prepares and offers
@ramsey feels better than Mastodon to me, although with less people for now. Best experience is actually on Threads, but what we need is one place where all the devs are. Right now it’s nowhere
@ramsey I didn’t dive much into it but as I could see it’s just because their end goal is to not do it at all and outsource the responsibility of timeline aggregation, which if you think about it will make so much sense with cheap LLM. At a distributed global scale people post whatever garbage they want, LLM categorize it and feeder systems clean it up and offer content based on applicable laws, user interest and common sense of the feeder owner
If you voted against the Interface Default Methods RFC for #PHP, please take a moment to read some of the most recent mailing list replies, starting with @Crell’s here: https://externals.io/message/120725#120798
I agree this feature goes against a lot of what I’ve learned as “best practices,” but I did a lot of introspection on this and decided that this feature is good for the future of the PHP language. It unlocks a lot of potential.
@gmazzap if you were designing a language in 2023 would you still make that concept part of the syntax instead of providing abstract classes only and letting users decide whether they want abstract-only or abstract+body?