Ten years leave。  Let's see :  We're forking Flutter. This is why. 
<https://flutterfoundation.dev/blog/posts/we-are-forking-flutter-this-is-why/>
  

After google freeze Flutter team head count,
    
    A labor shortage can always be fixed through hiring. However, due to 
company-wide issues at Google, the Flutter team's head count was frozen 
circa 2023, and then earlier in 2024 we learned of a small number of 
layoffs. It seems that the team may now be expanding again, through 
outsourcing, but we're not likely to see the Flutter team double or 
quadruple its size any time soon.

To make matters worse, Google's corporate re-focus on AI caused the Flutter 
team to de-prioritize all desktop platforms. As we speak, the Flutter team 
is in maintenance mode for 3 of its 6 supported platforms. Desktop is quite 
possibly the greatest untapped value for Flutter, but it's now mostly 
stagnant.
The golang team has the same problem, If google continue freeze head count, 
or cut the job.

let's see what will happen. 

Time will told you what will be.

On Monday, December 22, 2014 at 5:17:28 AM UTC+8 Henrik Johansson wrote:

> It would not change anything of course. Had it been another company 
> backing Go I might be inclined to agree (Java is fairly hard in Oracle 
> control regardless of the surrounding organizations) that a foundation or 
> some such may be better. Had I been using say Swift for example... I have 
> no illusions whatsoever about Google's financial motivations but given its 
> fairly outstanding track record in the open source area I am easily willing 
> to give the current setup the benefit of the doubt. 
>
> Either way, if the shit hits the fan alternate setups can always be put in 
> place like you said. 
> On Dec 21, 2014 9:30 PM, "Ian Lance Taylor" <ia...@golang.org> wrote:
>
>> On Sat, Dec 20, 2014 at 9:39 PM, zixu mo <hufen...@gmail.com> wrote:
>> >
>> > http://www.apache.org/foundation/
>> > Apache is the one of the honor open source project.
>> > Leading many open source projects development.
>> > It's good and open.
>> > Golang really need a organization behind. not only google.
>>
>> You've made two different arguments.
>>
>> The first is that if Google decides to stop supporting Go, there
>> should be some organization that continues to support it.  You've
>> suggested that this should be a foundation.  My response is 1) there
>> will be time to think about that in the unlikely event that the
>> situation arises; 2) there are many successful languages with no
>> associated foundation, and there are also many successful open source
>> projects with no associated foundation.
>>
>> The second argument you've made above, that Go (by the way, it's Go,
>> not Golang) needs an organization behind it, not just Google.  My
>> response is: why?  How would that help?  What would change?
>>
>> Ian
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "golang-nuts" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to golang-nuts...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/golang-nuts/139679a1-6a7f-4d37-8535-ce2109f80d7en%40googlegroups.com.

Reply via email to