Just curious what does a Python team do? It doesn’t make sense to dedicate a team to a programming language.
Google lays off its Python team
61–70 of 476 posts
Re: Google lays off its Python team
#62Earlier quoted context omitted.
This isn't the greatest submission and lacks any semblance of context. The poster is in Netherlands apparently and the new team in Germany? I have no idea what to make of this.
My read of it is that a US team was laid off. The poster is in NL and has to train he Munich team. The poster was not laid off.
Re: Google lays off its Python team
#63So TensorFlow is not officially dead.
New version release 1 month ago: https://blog.tensorflow.org/2024/03/whats-new-in-tensorflow-...
JAX (and Keras) is where the push is now. And, grudgingly, PyTorch
Re: Google lays off its Python team
#64Earlier 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…
Re: Google lays off its Python team
#65Earlier 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…
Re: Google lays off its Python team
#66Google's future is strictly tied to its AI products
All AI is written with Python.
Google lays off all Python team.
Segmentation fault
Re: Google lays off its Python team
#67Re: Google lays off its Python team
#68Google is an AI first company Google's future is strictly tied to its AI products All AI is written with Python. Google lays off all Python team. Segmentation fault
Type error on line 3: “Python” is not a valid type for “all AI”.
Re: Google lays off its Python team
#69Earlier quoted context omitted.
How do you "protect" a job?
Tax breaks for hiring citizens. Tariffs for hiring non citizens. Force companies to follow all the same employment laws for employees and contractors in other countries.
The cost of living of an Indian developer is way less than that of a US one, especially if the US one is in a high cost of living area such as SF or NYC. How can the US worker complete when they have US housing and college costs, not Indian ones, that need to be paid for?
Offshoring like this is allowing dumping of below-cost labor into US markets. Great for US C-suite folk and their profit-based bonuses, and for lobbyists getting paid big bucks to let this happen, but not so great for US citizens trying to make a living as software developers, which one might have thought would be a thing the US would strategically want to encourage, rather than strengthening a foreign country.
Re: Google lays off its Python team
#70Same thing with the Kythe (aka Grok) team that does the cross references for codesearch.