home.social

#laravel — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #laravel, aggregated by home.social.

  1. Behind the scenes at LaraPlugins: full PHPStan level 8, consistent typing everywhere. @LaraPlugins

    The kind of invisible work that keeps the plugin health scores you see honest.

    #Laravel #PHP #OpenSource

  2. Behind the scenes at LaraPlugins: full PHPStan level 8, consistent typing everywhere. @LaraPlugins

    The kind of invisible work that keeps the plugin health scores you see honest.

    #Laravel #PHP #OpenSource

  3. Behind the scenes at LaraPlugins: full PHPStan level 8, consistent typing everywhere. @LaraPlugins

    The kind of invisible work that keeps the plugin health scores you see honest.

    #Laravel #PHP #OpenSource

  4. Behind the scenes at LaraPlugins: full PHPStan level 8, consistent typing everywhere. @LaraPlugins

    The kind of invisible work that keeps the plugin health scores you see honest.

    #Laravel #PHP #OpenSource

  5. Behind the scenes at LaraPlugins: full PHPStan level 8, consistent typing everywhere. @LaraPlugins

    The kind of invisible work that keeps the plugin health scores you see honest.

    #Laravel #PHP #OpenSource

  6. It's been fascinating to catch snippets of other #opensource #developers coming together to establish common ground over the last week. We had to work through a number of negative emotions once we got word about parts of our own projects being associated to #fascist shitbirds.

    But what I'm enjoying the most is how like minded people are coming together and discussing how to move forward together, with a lot of common goals. People are discussing the effectiveness of current software licensing (#agpl, etc) and whether we need to make new ones, vetting of 3rd party libraries, and above all else, keeping the aforementioned shitbirds out.

    And we do need to keep them out. Because they are going to keep outing themselves as the horrible people they are.

    So far in the last month, I've watched #tailwindcss, #laravel, and #digitalocean go deep into the abyss with either supporting fascism and/or aggressively shoving AI shit into every thing they do.

    Those 3 things I just mentioned are the primary tools I use in the work I have done for over a decade. And with each announcement regarding them, they were dead to me in that same moment.

    I'm determined to build out my own replacements for #css and #php framework. Just like the #indieweb, it's all about owning your works with a strong #diy ethos.

    It appears the #technofascist reveal party we're going through has allowed for good things to happen. Much to their chagrin...

  7. It's been fascinating to catch snippets of other #opensource #developers coming together to establish common ground over the last week. We had to work through a number of negative emotions once we got word about parts of our own projects being associated to #fascist shitbirds.

    But what I'm enjoying the most is how like minded people are coming together and discussing how to move forward together, with a lot of common goals. People are discussing the effectiveness of current software licensing (#agpl, etc) and whether we need to make new ones, vetting of 3rd party libraries, and above all else, keeping the aforementioned shitbirds out.

    And we do need to keep them out. Because they are going to keep outing themselves as the horrible people they are.

    So far in the last month, I've watched #tailwindcss, #laravel, and #digitalocean go deep into the abyss with either supporting fascism and/or aggressively shoving AI shit into every thing they do.

    Those 3 things I just mentioned are the primary tools I use in the work I have done for over a decade. And with each announcement regarding them, they were dead to me in that same moment.

    I'm determined to build out my own replacements for #css and #php framework. Just like the #indieweb, it's all about owning your works with a strong #diy ethos.

    It appears the #technofascist reveal party we're going through has allowed for good things to happen. Much to their chagrin...

  8. It's been fascinating to catch snippets of other #opensource #developers coming together to establish common ground over the last week. We had to work through a number of negative emotions once we got word about parts of our own projects being associated to #fascist shitbirds.

    But what I'm enjoying the most is how like minded people are coming together and discussing how to move forward together, with a lot of common goals. People are discussing the effectiveness of current software licensing (#agpl, etc) and whether we need to make new ones, vetting of 3rd party libraries, and above all else, keeping the aforementioned shitbirds out.

    And we do need to keep them out. Because they are going to keep outing themselves as the horrible people they are.

    So far in the last month, I've watched #tailwindcss, #laravel, and #digitalocean go deep into the abyss with either supporting fascism and/or aggressively shoving AI shit into every thing they do.

    Those 3 things I just mentioned are the primary tools I use in the work I have done for over a decade. And with each announcement regarding them, they were dead to me in that same moment.

    I'm determined to build out my own replacements for #css and #php framework. Just like the #indieweb, it's all about owning your works with a strong #diy ethos.

    It appears the #technofascist reveal party we're going through has allowed for good things to happen. Much to their chagrin...

  9. It's been fascinating to catch snippets of other #opensource #developers coming together to establish common ground over the last week. We had to work through a number of negative emotions once we got word about parts of our own projects being associated to #fascist shitbirds.

    But what I'm enjoying the most is how like minded people are coming together and discussing how to move forward together, with a lot of common goals. People are discussing the effectiveness of current software licensing (#agpl, etc) and whether we need to make new ones, vetting of 3rd party libraries, and above all else, keeping the aforementioned shitbirds out.

    And we do need to keep them out. Because they are going to keep outing themselves as the horrible people they are.

    So far in the last month, I've watched #tailwindcss, #laravel, and #digitalocean go deep into the abyss with either supporting fascism and/or aggressively shoving AI shit into every thing they do.

    Those 3 things I just mentioned are the primary tools I use in the work I have done for over a decade. And with each announcement regarding them, they were dead to me in that same moment.

    I'm determined to build out my own replacements for #css and #php framework. Just like the #indieweb, it's all about owning your works with a strong #diy ethos.

    It appears the #technofascist reveal party we're going through has allowed for good things to happen. Much to their chagrin...

  10. It's been fascinating to catch snippets of other #opensource #developers coming together to establish common ground over the last week. We had to work through a number of negative emotions once we got word about parts of our own projects being associated to #fascist shitbirds.

    But what I'm enjoying the most is how like minded people are coming together and discussing how to move forward together, with a lot of common goals. People are discussing the effectiveness of current software licensing (#agpl, etc) and whether we need to make new ones, vetting of 3rd party libraries, and above all else, keeping the aforementioned shitbirds out.

    And we do need to keep them out. Because they are going to keep outing themselves as the horrible people they are.

    So far in the last month, I've watched #tailwindcss, #laravel, and #digitalocean go deep into the abyss with either supporting fascism and/or aggressively shoving AI shit into every thing they do.

    Those 3 things I just mentioned are the primary tools I use in the work I have done for over a decade. And with each announcement regarding them, they were dead to me in that same moment.

    I'm determined to build out my own replacements for #css and #php framework. Just like the #indieweb, it's all about owning your works with a strong #diy ethos.

    It appears the #technofascist reveal party we're going through has allowed for good things to happen. Much to their chagrin...

  11. Laravel v13.27.0 adds a Cloud facade, refreshForUpdate() for Eloquent models, and re-introduces orWhereKey()/orWhereKeyNot() without breaking Builder subclasses. Solid QoL release. #Laravel #PHP

    github.com/laravel/framework/r

  12. The point of an AAR is not the report. It's that the lesson survives the session.

    What worked, what didn't, what we'd do differently. Root causes, saved as dated markdown, referenced from the guides.

    #Laravel #PHP #Programming #AI

  13. The point of an AAR is not the report. It's that the lesson survives the session.

    What worked, what didn't, what we'd do differently. Root causes, saved as dated markdown, referenced from the guides.

    #Laravel #PHP #Programming #AI

  14. The point of an AAR is not the report. It's that the lesson survives the session.

    What worked, what didn't, what we'd do differently. Root causes, saved as dated markdown, referenced from the guides.

    #Laravel #PHP #Programming #AI

  15. The point of an AAR is not the report. It's that the lesson survives the session.

    What worked, what didn't, what we'd do differently. Root causes, saved as dated markdown, referenced from the guides.

    #Laravel #PHP #Programming #AI

  16. The point of an AAR is not the report. It's that the lesson survives the session.

    What worked, what didn't, what we'd do differently. Root causes, saved as dated markdown, referenced from the guides.

    #Laravel #PHP #Programming #AI

  17. After adding Compose watch to a project, every rebuild paused for ten seconds before the new container came up. If your restarts drag like that, here's a workaround that may help improve speed. #php #laravel masteringlaravel.io/daily/2026

  18. After adding Compose watch to a project, every rebuild paused for ten seconds before the new container came up. If your restarts drag like that, here's a workaround that may help improve speed. #php #laravel masteringlaravel.io/daily/2026

  19. After adding Compose watch to a project, every rebuild paused for ten seconds before the new container came up. If your restarts drag like that, here's a workaround that may help improve speed. #php #laravel masteringlaravel.io/daily/2026

  20. After adding Compose watch to a project, every rebuild paused for ten seconds before the new container came up. If your restarts drag like that, here's a workaround that may help improve speed. #php #laravel masteringlaravel.io/daily/2026

  21. After adding Compose watch to a project, every rebuild paused for ten seconds before the new container came up. If your restarts drag like that, here's a workaround that may help improve speed. #php #laravel masteringlaravel.io/daily/2026

  22. After Action Reports for every significant session now.

    Agents reflect on what worked, what broke, and the root causes. The lesson gets folded into the project docs, not lost.

    The next project starts where the last one ended.

    #Laravel #DevOps #programming

  23. CVE-2026-53932: OS command injection in laravel-backup-restore via crafted backup archives. CVSS 8. Unpatched before v1.9.4. If you restore Spatie backups, update now. Details: valtersit.com/cve/CVE-2026-539 #CVE #infosec #Laravel

  24. Found that @gonedark created a better Mockery replacement for PHP.

    github.com/jasonmccreary/double

    My problem with this library is not that it's not stable, is the stance behind it. «I just have it 0.x until it gains adoption»

    What fucking logic is behind that? It's like saying I should drive a car once I can complete 24 Heures du Mans. LOL.

    #Programming #SoftwareDevelopment #WebDevelopment #WebDev #Coding #Code #PHP #Laravel #Symfony #Testing #LaravelShift

  25. Found that @gonedark created a better Mockery replacement for PHP.

    github.com/jasonmccreary/double

    My problem with this library is not that it's not stable, is the stance behind it. «I just have it 0.x until it gains adoption»

    What fucking logic is behind that? It's like saying I should drive a car once I can complete 24 Heures du Mans. LOL.

    #Programming #SoftwareDevelopment #WebDevelopment #WebDev #Coding #Code #PHP #Laravel #Symfony #Testing #LaravelShift

  26. Found that @gonedark created a better Mockery replacement for PHP.

    github.com/jasonmccreary/double

    My problem with this library is not that it's not stable, is the stance behind it. «I just have it 0.x until it gains adoption»

    What fucking logic is behind that? It's like saying I should drive a car once I can complete 24 Heures du Mans. LOL.

    #Programming #SoftwareDevelopment #WebDevelopment #WebDev #Coding #Code #PHP #Laravel #Symfony #Testing #LaravelShift

  27. Found that @gonedark created a better Mockery replacement for PHP.

    github.com/jasonmccreary/double

    My problem with this library is not that it's not stable, is the stance behind it. «I just have it 0.x until it gains adoption»

    What fucking logic is behind that? It's like saying I should drive a car once I can complete 24 Heures du Mans. LOL.

    #Programming #SoftwareDevelopment #WebDevelopment #WebDev #Coding #Code #PHP #Laravel #Symfony #Testing #LaravelShift

  28. Found that @gonedark created a better Mockery replacement for PHP.

    github.com/jasonmccreary/double

    My problem with this library is not that it's not stable, is the stance behind it. «I just have it 0.x until it gains adoption»

    What fucking logic is behind that? It's like saying I should drive a car once I can complete 24 Heures du Mans. LOL.

    #Programming #SoftwareDevelopment #WebDevelopment #WebDev #Coding #Code #PHP #Laravel #Symfony #Testing #LaravelShift