Re:Flutter: the good, the bad and the ugly
by k__ on Friday November 23, 2018 @07:04PM
(#18519601)
"airbnb abandoning it shows it's bad, but other companies using it successfully doesn't sbow it's good!"
[ Parent
| on HN ]
Re:Flutter: the good, the bad and the ugly
by nv-vn on Friday November 23, 2018 @08:45PM
(#18519952)
Abandoning something takes more work than using it, since it adds the cost of a rewrite. If Airbnb adopted framework X that wouldn't make me confident in framework X -- they haven't even used it yet! If they used it for a long time that would increase my confidence in X (in the absence of evidence to the contrary). But if everyone else started abandoning X I'd take Airbnb's experience with a grain of salt. I get that Discord is able to do well with it, but that doesn't mean everyone is able to do well with it depending on their needs. And who knows, maybe Discord is having just enough trouble that it hurts but too little to switch.
Re:Flutter: the good, the bad and the ugly
by chrisco255 on Friday November 23, 2018 @10:05PM
(#18520228)
They give it rave reviews: https://blog.discordapp.com/why-discord-is-sticking-with-rea...
Re:Flutter: the good, the bad and the ugly
by ryanwaggoner on Friday November 23, 2018 @09:40PM
(#18520147)
I was making a tongue in cheek retort about it “clearly” meaning that, since person I was responding to said it clearly meant they were dysfunctional. Probably could have made it more explicit.
I do think that scaling an app to millions of users says basically nothing on its own about the app framework / code quality itself. You’re scaling across as many devices as you have users. There’s no challenge at all there on the mobile dev side.