1,232 karma · joined July 4, 2017
I am surprised by this because Python minor versions break backwards compatibility all the time. Our company for example is doing a painful upgrade from py39 to py311
There is literally a timeline that only shows the feed of people you follow.
And I mean, wasn't the last Administration effectively Autopen? Yes, the President receives recommendations and tries to make the best judgement on those.
What would Biden's answer be for pardoning Fauci?
Instead of just commenting about being dismayed with the state of things, how about step back and speculate as to why he did this pardon, and what the implications of it are.
I don't know the answer to either, but I surely didn't learn much from what used to be an insightful, intelligent crowd
If you don't understand the difference between now, and those events, then I can't help you.
> "I think it really started when we took out the nuclear capability of Iran," Trump said, referring to the June strikes on Iran’s nuclear sites. "When you look at what they had, you couldn't have made this deal with someone sitting over there with a nuclear weapon over your head." [1]
[1] https://www.foxnews.com/politics/trump-credits-iran-nuclear-...
I’m not suggesting at all it’s ok to use your phone while driving, and is unlawful for a good reason. Yet CarPlay, a dumbed down phone bolted to your dash, is totally fine, despite being no more safe IMO
Sure, in total, other jobs may be created and growth is increased -- it's essentially a tautology.
Having to plan your day around when to charge your Apple Watch doesn't sound like a good experience to me.
There are a number of blog posts echoing a similar critique[1].
Using KubernetesOperators creates a lot of wrong abstractions, impedes testability, and makes Airflow as a whole a pretty overkill system just to monitor external tasks. At that point, you should have just had your orchestration in client code to begin with, and many other frameworks made this correct division between client and server. That would also make it easier to support multiple languages.
According to their README: https://github.com/apache/airflow#approach-to-dependencies-o...
> Airflow has a lot of dependencies - direct and transitive > The important dependencies are: SQLAlchemy, Alembic, Flask, werkzeug, celery, kubernetes
Why should biz logic that just needs to run Spark and interact with S3 now need to run a web server?
[1] Anecdotes from various posts - https://medium.com/bluecore-engineering/were-all-using-airfl... - https://eng.lyft.com/orchestrating-data-pipelines-at-lyft-co... - https://dagster.io/blog/dagster-airflow
> Airflow, in its design, made the incorrect abstraction by having Operators actually implement functional work instead of spinning up developer work.
> By simply moving to using a Kubernetes Operator, Airflow developers can develop more quickly, debug more confidently, and not worry about conflicting package requirements.
> Airflow lacks proper library isolation. It becomes hard or impossible to do if any team requires a specific library version for a given workflow
> There is no way to separate DAGs to development, staging, and production using out-of-the-box Airflow features. That makes Airflow harder to use for mission-critical applications that require proper testing and the ability to roll back
> Data pipelines written for Airflow are typically bound to a particular environment. To avoid dependency hell, most guides recommend defining Airflow tasks with operators like the KubernetesPodOperator, which dictates that the task gets executed in Kubernetes. When a DAG is written in this way, it’s nigh-impossible to run it locally or as part of CI. And it requires opting out of all of the integrations that come out-of-the-box with Airflow.