4 ms·

Remember, this is from the company that thought that laying off their Python team was a good idea. https://news.ycombinator.com/item?id=40171125 https://news.y

by ta20240226 2y ago

Remember, this is from the company that thought that laying off their Python team was a good idea. https://news.ycombinator.com/item?id=40171125 https://news.ycombinator.com/item?id=40171125 Draw your conclusions of the level of support for this library.

foota 2y ago
I don't think you need to draw your own conclusions: "This is not an officially supported Google product".
- devsda 2y ago
  For small time developers and normal users, "Google support" already feels like best effort community support.
  - MattGaiser 2y ago
    Even GCP seems “best effort.”
    - metadat 2y ago
      Is it really, though? Not in my experience. The bureaucracy has taken full control of The Host.
nickysielicki 2y ago
You’re totally missing the point. The point is: you have some Python script, and you don’t want it to disappear into the sad world of a ticket attachment, and if you add the 5 lines of code and have a nice onboarding experience, it doesn’t have to disappear into a ticket attachment, it can instead disappear into your browser bookmarks. You should never test the limits of this framework because if it’s anything other than putting a simple script into a webpage, you shouldn’t be using this. It’s rot proof.
shmatt 2y ago
The US Python foundational team was less than 10 people. If you think any 10 person team in a 200,000 employee corporation is that critical well I’d have to disagree When their jobs were moved to Munich there was a lot of discussion about how important they were, but something else stood out to me. One of the things they accomplished was taking over a year to make sure the monorepo can be upgraded to the latest version of python As an outsider this definitely smells like an org creating work just to justify its budget. You have a single team of a handful of engineers doing the python upgrade work for tens of thousands of engineers. Doesn’t feel right out of the bat I’m sure soon enough with the role moving they’ll find out if the team is needed at all
- djtango 2y ago
  What? The monorepo is huge that sounds like a nightmare to coordinate across so many engineers and such a huge codebase
  - kevindamm 2y ago
    It was a nightmare. Mostly because there were a lot of special cases (think of a Python2 appengine-classic having no upgrade path on some //third_party lib that the team needed to keep running anyway), and it's not just the 10^5-10^6 # of concurrent contributors to the codebase, it's 10+ years of contributions much of which were maintenance-mode projects, many of those had been inherited two or three times over. There was a lot of cat-herding.
  - keredson 2y ago
    you are right. made worse because there's an internal rule that you can't ever have two versions of a library in the monorepo ant the same time. it has to be one giant CL for the entire migration company-wide.
  - shmatt 2y ago
    IF every package in the monorepo is forced to use the same exact version then there would exist literally thousands of these teams, even tens of thousands, which I doubt I don’t really believe if I go to 500 Google owned websites I will find the exact same version of angular everywhere
deleted 2y ago
[deleted]

foota 2y ago

I don't think you need to draw your own conclusions: "This is not an officially supported Google product".

devsda 2y ago
For small time developers and normal users, "Google support" already feels like best effort community support.
- MattGaiser 2y ago
  Even GCP seems “best effort.”
  - metadat 2y ago
    Is it really, though? Not in my experience. The bureaucracy has taken full control of The Host.

nickysielicki 2y ago

You’re totally missing the point. The point is: you have some Python script, and you don’t want it to disappear into the sad world of a ticket attachment, and if you add the 5 lines of code and have a nice onboarding experience, it doesn’t have to disappear into a ticket attachment, it can instead disappear into your browser bookmarks. You should never test the limits of this framework because if it’s anything other than putting a simple script into a webpage, you shouldn’t be using this. It’s rot proof.

shmatt 2y ago

The US Python foundational team was less than 10 people. If you think any 10 person team in a 200,000 employee corporation is that critical well I’d have to disagree When their jobs were moved to Munich there was a lot of discussion about how important they were, but something else stood out to me. One of the things they accomplished was taking over a year to make sure the monorepo can be upgraded to the latest version of python As an outsider this definitely smells like an org creating work just to justify its budget. You have a single team of a handful of engineers doing the python upgrade work for tens of thousands of engineers. Doesn’t feel right out of the bat I’m sure soon enough with the role moving they’ll find out if the team is needed at all

djtango 2y ago
What? The monorepo is huge that sounds like a nightmare to coordinate across so many engineers and such a huge codebase
- kevindamm 2y ago
  It was a nightmare. Mostly because there were a lot of special cases (think of a Python2 appengine-classic having no upgrade path on some //third_party lib that the team needed to keep running anyway), and it's not just the 10^5-10^6 # of concurrent contributors to the codebase, it's 10+ years of contributions much of which were maintenance-mode projects, many of those had been inherited two or three times over. There was a lot of cat-herding.
- keredson 2y ago
  you are right. made worse because there's an internal rule that you can't ever have two versions of a library in the monorepo ant the same time. it has to be one giant CL for the entire migration company-wide.
- shmatt 2y ago
  IF every package in the monorepo is forced to use the same exact version then there would exist literally thousands of these teams, even tens of thousands, which I doubt I don’t really believe if I go to 500 Google owned websites I will find the exact same version of angular everywhere

deleted 2y ago

[deleted]