4,597 karma · joined July 20, 2010
Those companies have R&D for a reason. A company _wants_ to make things, right? If this is impacting their ability to make things, wouldn't it be in a company's best interest to advocate openly against the tax code, rather than be silent about the reason, fire their staff, and just not make things?
It doesn't make sense to me how so many people are aware of this to the point that many many companies are all doing the same thing for the same reason, but seemingly nobody was talking about it before this post. That doesn't make a lot of sense to me.
>Fritz Jakob Haber (German: [ˈfʁɪt͡s ˈhaːbɐ] ⓘ; 9 December 1868 – 29 January 1934) was a German chemist who received the Nobel Prize in Chemistry in 1918 for his invention of the Haber process, a method used in industry to synthesize ammonia from nitrogen gas and hydrogen gas. This invention is important for the large-scale synthesis of fertilizers and explosives.[4] It is estimated that a third of annual global food production uses ammonia from the Haber–Bosch process, and that this food supports nearly half the world's population.[5][6] For this work, Haber has been called one of the most important scientists and industrial chemists in human history.[7][8][9] Haber also, along with Max Born, proposed the Born–Haber cycle as a method for evaluating the lattice energy of an ionic solid.
The second paragraph gives the context:
>Haber, a known German nationalist, is also considered the "father of chemical warfare" for his years of pioneering work developing and weaponizing chlorine and other poisonous gases during World War I. He first proposed the use of the heavier-than-air chlorine gas as a weapon to break the trench deadlock during the Second Battle of Ypres. His work was later used, without his direct involvement,[10] to develop the Zyklon B pesticide used for the killing of more than 1 million Jews in gas chambers in the greater context of the Holocaust.
You could do a filesystem snapshot and copy from that, but neither a cp or rsync is atomic.
>This means that you can write your entire application in a single language and deploy it as a single binary. No more microservices, no more containers, no more Kubernetes, no more Docker, no more VMs, no more DevOps, no more infrastructure, no more ops, no more servers.
This is an abstraction layer that will end up being applied on top of most or all of those technologies. You can't hide from the fact that the database instances need to run on something.
Yes. A company doesn't exist to hire programmers who write code. Software development is a means to an end.
Legitimately, Teslas have been the best cars I've ever owned, but thanks to Elon, I will never buy another one, so long as he runs the company.
* - not you, Cybertruck
In cloud environments, it's pretty common that your cloud provider has specific implementations of Kubernetes objects, either by creating custom resources that you can make use of, or just building opinionated default instances of things like storage classes, load balancers, etc.
It's pretty easy to not think about the implementation details of, say, an object-storage-backed PVC until you need to do it in a K8s instance that doesn't already have your desired storage class. Then you've got to figure out how to map your simple-but-custom $thing from provider-managed to platform-managed. If you're moving into Rancher, for instance, it's relatively batteries-included, but there are definitely considerations you need to make for things like how machines are built from disk storage perspective and where longhorn drives are mapped, for instance.
It's like that for a ton of stuff, and a whole lot of the Kubernetes/OutsideInfra interface is like that. Networking, storage, maybe even certificate management, those all need considerations if you're migrating from cloud to on-prem.
I mostly rubber duck and let him build castles in the sky which we'll probably never reach, or which will be overcome by events, but it's not the worst way for someone to spend their time. I'm not sure it's always productive, but I don't think it's harmful.
That's about what I've run into in my life. Most people do things on autopilot and don't think about what they're doing, or don't consider it worth thinking about. If you want to do something and be good at it, wanting to be good at it is enough to move you past most people, as long as you have a growth mindset.