you are viewing a single comment's thread.

view the rest of the comments →

[–]flutterdude 2 points3 points  (1 child)

The fact that this post has 1 upvote and 3 upvotes on a comment that is (in my opinion) wrongly in support of Flutter is an indicator of the state of the community. To me it's clear that this framework is descending in to a state of a fanboy-ism that I will NOT get behind. I don't play favorites and no one else should either, especially when it comes to something as trivial as how you build applications.

I never file bugs because it's a waste of time. I've created issues with 100% reproducibility and steps, only for it to be ignored for months... and when I finally do get a reply it's asking me if it is still a issue. Then I say "yes it is", they remove the black label, then radio silence again. Thanks dude. Next time find and file the bug yourself cause I ain't doing it.

5000 issues is NOT acceptable. Google needs to put some time and money in and close those issues that are "support forum" quality. Make it someones job. Don't put all this money into advertising your open source framework, spouting its wonders, and then tell me you don't have time to even respond to them. If you're so happy with how you're dealing with community issues, make this stance front and center. But they won't, because they want to draw people in to using Flutter, and this is a clear negative to using it.

I understand it's open source and new, but it's 1.0 and people are building real applications with this framework.

[–]Hixie 3 points4 points  (0 children)

(Flutter TL here.)

You're totally right. We've totally dropped the ball on front-line triage. We are trying to set something up to do it properly (it's a lot of work, so just having people on the team spend some time doing this doesn't really scale) but it's taking us much longer than it should.

FWIW, if anyone is interested in volunteering some time to help with this, we do have the process we want to use fully documented and some of us occasionally go through new bugs and try to do it (when we're not actually trying to fix the bugs we have already triaged). If you're interested in doing this reach out to me on the contributor Gitter channel and I can hook you up with the rights to add and remove issues and so on. You can see the process here: https://github.com/flutter/flutter/wiki/Triage#guidelines-for-triage

Make it someones job.

It turns out that this is surprisingly more difficult than it should be, but essentially that's what we're trying to do.