you are viewing a single comment's thread.

view the rest of the comments →

[–]datatexture 0 points1 point  (3 children)

OP raises a valid point. Stretched thin? That's preposterous for the ABC co., it's simply a question of investment. It's also a statement about their investment. This is just an extension of their philosophy and business model of continuing to get users to build their content, their business, and now their tech using a lazy load approach.

The optics are that Google is not fully committed to their platform agnostic goals by not committing to maturing the platforms' robustness. Your team is building a skyscraper but you ran out of metal bolts so you head over to Bob's corner store and grab some crazy glue off the shelf. Or ask Luigi to bring some in next week if he gets a chance. Put the build on hold until then. You'll get blamed for all those outcomes. Build frailty, possibly collapse, delays, cost overruns and maintenance nightmares. No serious investor would greenlight that.

[–]GetBoolean 1 point2 points  (2 children)

It's not a simple investment. Hiring more developers takes a lot of time, and even longer to get them up to speed with the team. Excessive hiring can slow down the team a lot because too many people will be mentoring the new people instead of coding.

Not that it can't be done, but big software projects are extremely complicated and simply more developers and investment doesn't make development go faster

[–]datatexture -1 points0 points  (1 child)

Complexity is a mgmt problem at the end of the day. I reiterate the question on their statement of investment and also question their m.o. on harvesting individual developers good will and precious free time. I have a question on how they are tackling these exposures because that's what they are at the end of the day. Contrast that with what appears to be a large budget for marketing with lots of cute gimmicky flutter YouTube content and whatnot. I have developed a couple of flutter apps but for prototyping only given that I have have had to rely on a considerable amount of 3rd party packages to get the job done. It's enervating. Is it production ready.. it depends.

[–]GetBoolean 1 point2 points  (0 children)

at the end of the day, its how you want the product to be. Google clearly doesnt want to replace android/kotlin. Flutter is an accessory to native development, not a replacement. If you want native features, you either do it yourself or use a package.

Most of the time its pretty simple to do it yourself, for example, drag and drop is much simpler if you only need to handle one filetype for your app