Interestingly enough, there's been a reply by the Flutter engineering lead since...

ignoramous · on Nov 10, 2021

> Hi all. Flutter engineering lead here. Thank you for the bug.

> ...

> I've retitled the bug to specifically target the blinking cursor issue. I don't expect us to attack this soon, but it's on our radar. The best way to indicate your support for this or any other issue is to use the +1 button.

I don't get prioritizing based on 'popularity' contests. To me, 'a blinking cursor' taking up 10% CPU and 50MB RAM doesn't sound like a bug that needs one.

Of course, unless you are a team at Google having issues, then the flutter team's going all hands on deck: https://news.ycombinator.com/item?id=26333973

derefr · on Nov 10, 2021

Imagine having 1000 open bugs that are all of that level of severity/urgency. When the house is on fire and being knocked down by a tornado and a meteorite is coming for it, you really need some other criteria besides "disaster" to decide which disaster to address first.

ignoramous · on Nov 10, 2021

danShumway vibes: https://news.ycombinator.com/item?id=26335329

ssijak · on Nov 10, 2021

Flutter repo in Github has 10 000 open issues, so I don't know how you prioritise that at all.

Hixie · on Nov 10, 2021

https://github.com/flutter/flutter/wiki/Issue%20Hygiene describes our policies here.