{"id":120389,"date":"2024-10-29T13:09:18","date_gmt":"2024-10-29T11:09:18","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/proekt-flock-osnoval-fork-frejmvorka-flutter"},"modified":"2024-10-29T13:09:18","modified_gmt":"2024-10-29T11:09:18","slug":"proekt-flock-osnoval-fork-frejmvorka-flutter","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/proekt-flock-osnoval-fork-frejmvorka-flutter","title":{"rendered":"The Flock project was founded as a fork of the Flutter framework.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The Flock project has been introduced, which creates a fork of the user interface framework Flutter, developed by Google under the BSD license. The initiative to create this fork was taken by Matt Carroll, a former Google employee who was previously part of the Flutter development team. The reason for creating the fork is cited as the insufficient amount of resources that Google allocates to the project. <\/p>\n
Google discontinued the expansion of the core Flutter development team in 2023, and in 2024, the company laid off some employees. According to the founders of the fork, the remaining developers at Google and outsourced contributors are not enough for the full development of the project. Consequently, the lack of Flutter developers has led to a shift in priorities and stagnation in the development of the framework for desktop platforms (development for 3 out of 6 supported platforms is currently limited to maintenance of the existing codebase). The shortage of developers also negatively affects bug fixing \u2014 some error reports may remain in the queue for years. <\/p>\n
The Flock project does not intend to split the existing community and considers itself as 'Flutter+' \u2014 a synchronized fork with the main project, adding community-requested improvements and bug fixes that the core Flutter development team at Google cannot or does not want to implement. The project's goal is to accelerate development and expand the resources involved in development through a community not associated with Google. Currently, the contents of the Flock repository fully correspond to the Flutter repository. <\/p>\n
Issues hindering direct interaction with the main Flutter team include a lack of time for core developers to review third-party changes, excessive time spent on various approvals, lengthy discussions over contentious decisions, and a lack of understanding of the challenges faced by application developers (the core team focuses on developing Flutter, not building applications based on it, which complicates understanding the urgency of resolving certain issues quickly). It is assumed that experienced Flutter application developers and those maintaining packages will be able to use the fork to promptly address arising issues and introduce desired innovations without waiting for responses from the main Flutter team or coordinating changes with them. <\/p>\n
For its part, the main Flutter team will, as much as possible, align with its schedule and criteria to incorporate changes from the fork into the Flutter core. Given that Flock plans to involve a large number of participants in reviewing changes, the transfer of changes from the fork will enhance the quality of the Flutter codebase. This way, the community will not be limited by the capabilities of the main Flutter team and will be able to use more efficient and flexible development rules. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"