2,535 karma · joined October 1, 2020
50% of the support issues were because people could not properly sign requests and it caused me to learn how to make http in all sorts of crap to help support them.
Apple still makes 10s of billions a year letting Google be the default search, they have a vested interest in maintaining that revenue.
Plus whatever "values" they have will go right out the window if the golden iphone shaped Goose ever stumbles.
Got a soaker in April when I stepped on some snow that has hiding a deep puddle on a trail.
Now a days I am probably more likely to say "Clicker" unless otherwise prompted.
The browser APIs spit out so much info about the host system on demand and that doesnt even consider the other tricks they use.
They go remote, but don't change a lot of other things or attempt to mitigate the downsides (there are downsides, everything is a trade off) and then claim its a failure when they need a stealth layoff.
Also IBM has a long history of "Resource Actions" so this type of thing is not all unexpected from them.
If my systems guys are telling me the truth is it a real time sink to run and can require an awful lot of babysitting at times.
Also I assume this extension is pretty obvious so it wont take long for CF bot detection to see it the same as playwrite or whatever else.
You can increase interaction and thus ad revenue when people think there are others to interact with.
The optics are pretty shit though.
That coupled with the relative immaturity of the python async ecosystem leads to lots of rough edges. Especially when they deploy these things into heavily abstracted cloud ecosystems like Kubernetes.
FastAPI also trys to help by making it "easy" to run sync code but that too is an abstraction that is not majorly documented and has limitations.
We were doing some testing and > 96 cores at 100% caused a massive degradation in performance. We ended up going with dual 32C/64T Epycs (which cost twice as much) as a result. If they fix it in the Altra One chips they will be back on the table though because they were very good power wise for our workload and quite price competitive in a supermicro chassis.
People doing web dev in python could use pythons native json but rarely do because there are other far more performant options for example.
I have seen things that generate server stubs but have not encountered something that enforces things like error code/response types etc.
They want something that reads the go code they have written and creates an openapi spec used to generate clients in other languages.