laravel/framework tickets being closed in a hurry?

https://github.com/laravel/framework/issues/39959

This is a bug, not a question. It seems like driesvints is more interested in maintaining the "zero open tickets" award than actually reviewing submitting bug reports.

How is "renameColumn() changes the column type" not a valid bug?

20 thoughts on “laravel/framework tickets being closed in a hurry?”

  1. Yeah, they close almost everything really fast with canned responses and never come back to them. What’s even better is when they close a PR for no reason, wait a few months, and then implement it themselves claiming they came up with the idea.

    Reply
  2. They have the most unhealthy obsession with wanting 0 issues and 0 PRs across the board that it’s almost a knee jerk reaction for them to insert a template reply and close it.

    It pisses me off so much that a detailed issue or PR gets the official stamp of “fuck you” from Taylor or the others with a “Don’t really need this rn.”

    Worst part is, if you’re a part of the community you can’t say anything about it without someone quote tweeting you into oblivion.

    I love Laravel and the community but it’s literally a cult lmao

    Reply
  3. So much this. Yes. I often find active bugs and useful PRs that have been marked as closed, including the `renameColumn()` issue exactly. Also why is it a good thing for such a large community project to have 0 PRs and 0 issues, that’s not a metric that’s important to me when picking a new framework.

    Reply
  4. Annoying af. Maybe you could fork the repo and fix it yourself, then just pull down upstream changes as they occur? Would be much easier if they just properly reviewed your PR and accepted it, though.

    Reply
  5. If thats the case, need to switch Symfony.
    Wait a minute, it already got so many issues.
    Idea, lets create our own fucked up framework.

    Reply
  6. Tangentially, it’s worth noting that TIMESTAMP is a terrible datatype: it’s strictly defined as 32 bits, and it will overflow in January 2038. It’s the binary equivalent of using two-digit years.

    That said, stealthily upgrading the column is still bad.

    Reply
  7. This seems to be a problem in a lot of high-profile projects. The one that really bugs me is when they have some bot that closes issues which have gone too long without a comment. Ignoring an issue until it gets marked “stale” isn’t the same as fixing it.

    Reply
  8. I have seen Grahem Cambell (Sorry for the bad spelling) legit be rude to people, even to driesvints when they were trying to get Laravel 8.0 ready – constantly trying to close or demand an answer as to why or shut the subject down.

    Mean while Taylor tells people on twitter that haters, gonna hate.

    I stay away from Laravels github, if I found a bug, I just keep my mouth shut and hope they find and fix it. don’t want that kind of negativity and toxicity.

    Reply
  9. I admit his response isn’t ideal, but timestamp isn’t a good column type and shouldn’t be used. You’ll have to change to date time eventually anyway

    Reply
  10. well you can always fork laravel/framework and fix the issue there instead of crying here 🙂 or better – write your own framework!

    Reply
  11. Everyone should just keep reposting, and reposting, and reposting this 1 issue until the point is made and it gets resolved. lol

    Reply
  12. This seems like a classic case of setting the wrong goals and metrics. Having issues addressed is good. Having 0 open issues is a way to measure it, but a bad way. One that drives the wrong behaviour.

    They should improve the metrics to drive the correct behaviour.

    Reply
  13. i put in a tiny feature once, i forget what it was because it was years ago but it was mimicking a very similar one they already had a pattern set for so nothing out of line, and they were super dismissive and rude about it. i didn’t even mind if they were like “well, people can extend the framework to do this themselves if they really want it” that’s totally cool by me, but their attitude reminded me of the rich kids i’d see in high school that were bratty little mean girls. i enjoy the framework and defend it/Taylor’s decisions with it plenty (esp the unfair backlash over commercial projects), but if that were in person i would’ve bodied his 180 pound ass into a wall. it really took the wind out of my sails as a laravel developer for a good while. so when Taylor whines about people not liking him, i take it with a grain of salt because he’s likely reaping what he’s sown. maybe he’s cool in person one-on-one without his groupies around but doesn’t seem like someone i’d pick to have beers with (he probably drinks strawberry hard seltzers anyways haha).

    Reply

Leave a Comment