How about flutter/dart teams? Are they safe?
Flutter was already affected in this wave.
Google lays off its Python team
421–430 of 476 posts
Re: Google lays off its Python team
#422Earlier quoted context omitted.
Because they have Python code that needs to be supported. The ML ecosystem, for example, is much larger in Python than Go.
Has Youtube been completely moved off from Python? Last account I have from it (quite outdated, I must admit) was that it had heavy ties with it.
Not sure, but I believe the performance-critical components are C++.
Re: Google lays off its Python team
#423Google feels like it can re-externalize costs. Therefore it does. As Brian Cantrill said, Don't Anthropomorphize Google!
Don't anthropomorphize Sundar Pichai
Re: Google lays off its Python team
#424Playing Devil’s Advocate - why does Google need a Python team when they made Go?
Go is not used in machine learning at all
Re: Google lays off its Python team
#425Earlier quoted context omitted.
Of course it does. Pretty much every FAANG, and many smaller ones, have teams for every programming language they consider important. Google has C++, Rust, Python, Java, JavaScript, and others (although I've heard that several of these teams were hard it in this round.) To take a basic example: Google has a team that works inside LLVM and Clang to improve the code it produces for Google's specific workloads. (Often t…
in addition to contributing to upstream python, we * maintained a stable version of python within google, and made sure that everything in the monorepo worked with it. in my time on the team we moved from 2.7 to 3.6, then incrementally to 3.11, each update taking months to over a year because the rule at google is if you check any code in, you are responsible for every single breakage it causes * maintained tools to…
We're hiring! https://boards.greenhouse.io/blackcanyonconsulting/jobs/5754...
Good life work balance
Re: Google lays off its Python team
#426Earlier quoted context omitted.
A visa is not permanent, but it might as well be for Indian and Chinese citizens. The green card lottery can easily take decades. You could have gone to college, got married, had kids, bought a house, and maybe even see your kids graduate college and have kids of their own before you get guaranteed residency in the US. "Oh you should be happy you had a good thing going" is not something I'd find especially comforting…
> got married, had kids, bought a house I lived in the US on a temporary visa and it's wild to me that people would put down roots in any country without a clear path to permanent residency. When you read the conditions attached to your employer-sponsored non-immigrant visa it makes it pretty clear that you're not in the country to settle permanently, you're there to work for the duration of your visa and that's all.…
A good friend of mine is Indian and also gay. Moving back to India and having a happy life with equal rights isn't on the table.
Re: Google lays off its Python team
#427If a Google recruiter comes for you, don't walk, run.
That is what Google has become under Sundar Pichai.
Re: Google lays off its Python team
#428Earlier quoted context omitted.
Well over 100m lines of Python as has been publicly stated several times over the years is not "very little".
In a codebase of 13+ trillion lines it's very little.
Google has published that it is at about 2 billion LoC not including experiments and scratch use. I don't know if the 100 million lines of Python includes experiments. Also, if the number is old, there is a chance that the number of lines of Python has actually gone down over the years due to the (soft) mandate to stop using it.
Re: Google lays off its Python team
#429Earlier quoted context omitted.
Of course it does. Pretty much every FAANG, and many smaller ones, have teams for every programming language they consider important. Google has C++, Rust, Python, Java, JavaScript, and others (although I've heard that several of these teams were hard it in this round.) To take a basic example: Google has a team that works inside LLVM and Clang to improve the code it produces for Google's specific workloads. (Often t…
in addition to contributing to upstream python, we * maintained a stable version of python within google, and made sure that everything in the monorepo worked with it. in my time on the team we moved from 2.7 to 3.6, then incrementally to 3.11, each update taking months to over a year because the rule at google is if you check any code in, you are responsible for every single breakage it causes * maintained tools to…
[deleted]
Re: Google lays off its Python team
#430Earlier quoted context omitted.
in addition to contributing to upstream python, we * maintained a stable version of python within google, and made sure that everything in the monorepo worked with it. in my time on the team we moved from 2.7 to 3.6, then incrementally to 3.11, each update taking months to over a year because the rule at google is if you check any code in, you are responsible for every single breakage it causes * maintained tools to…
Adding to the wonderful writeup by my now-ex teammate (thanks!): Several of us were/are/TBD also involved in both long term strategic leadership and maintenance of the open source CPython project itself. That direct feedback line from a major diverse needs user into the project and ecosystem was valuable for the world. The reason I stayed on this team for 12+ years is as zem said. It was an ideal impactful alignment…
well, why don't you guys stay together and continue work? start your own thing! google fired you, yes, but you're still alive and able to communicate. maybe you won't get paid as much as you did at google. but prove to them that you have something of value to provide to society.