My ethernet is also capped at 1 Gb/s for most of my computers. The 10 Gb/s connection is still useful as it makes sure that things running at different devices won't affect each other. Streaming won't affect games won't affect work-related video calls. It's great.
That is a narrative that misses the point of the thread and is generally not compatible with hard data. For example, the amount of suicides in US during 2020 went down.
It's not a string either though: in the same way integer addition (almost always) does not make sense, string concatenation (almost always) does not make sense either. The proper type would allow for equality check and explicit string (de)serialization only.
I guess it depends how you think about it. From computational perspective, it's heavyweight. On the other hand, it really optimizes for minimal human effort, on several levels:
* GPT-3 is conceptually simple: the effort to invent it and engineer it amortizes well.
* Once the model is trained, it can be reused to very different tasks.
I think we are really torturing language here. I don't want to get into specifics of what constitutes business value, how to value brand and customer satisfaction and so on. I can add more examples like https://deepmind.com/blog/article/deepmind-ai-reduces-google... that shows how neural networks helps in the pure bottom-line sense you care about.
Let me close my argument: neural network techniques developed in the last ten years are super useful here and now, they are used by billions of people every day and they do make their lives easier.
I don't understand why you think it's hard to tell your CI/CD pipeline to run itself on a schedule. I find this totally consistent with my tooling (I have CI/CD in place for many different reasons, this is one of them) and I don't know how this CI/CD cron makes me "packaging maintainer and infrastructure maintainer".
"With containers, you are responsible for figuring out which ones need which packages and how to re-build them."
Yeah, you need to know how to rebuild your world in ANY CASE. It's not an argument against containers that they require an approach that is the best practice.
No, in the context of the conversation, it's an argument for a higher valuation of the entity.
The value of every corporation primarily reflects expectation of future profits. That's the reason P/E ratios differs a lot even for established companies.
I agree that technology advances would have lead to massive deflation without all the money printing. The point of money printing is to do precisely this, so that the measure of economy does not get out of sync with the size of the economy. https://www.amazon.com/Lords-Finance-Bankers-Broke-World/dp/... is a great book that touches the topic -- it also shows this discussion is not new.
I also agree that the chosen transmission mechanism of money creation (buying bonds and stocks by central banks) might have lead to worsening inequality. I like the Yudkowsky treatment at https://www.lesswrong.com/posts/tAThqgpJwSueqhvKM/frequently... .
But I still think that the inflation is low and if we want to describe the problems that are happening even though it's low, we should create new language, not shift the current one.
Inflation, using the usual definition, cannot be 'masked by technology' as technology is one of the things that legitimately determine general price level. Inflation counts and always counted general price level with effects of technology advancements taken into account. So the poster you are replying to has it right: inflation is low.
Knative[0] pushes in that direction from the side of "complicated" Kubernetes. It's still far away from easy, but I expect that the solution will look like this -- a software that uses Kubernetes base to provide high-level primitives. Helpful cloud provider will give you a cluster with such thing already installed, as Google already does for Knative with the Cloud Run offering.
Microsoft allows you to publish a web application from Visual Studio project to Azure.[1] It's very simple, but more much opinionated. It's a great trade-off for an individual developer who needs to focus on functionality. In the context of this discussion, there's an important distinction -- it's not an interface, it's just a feature. It's tightly coupled to Azure from one side and to Microsoft dev stack from the other.
Kubernetes is our one shot at having the universal vendor-neutral cluster interface. The fact that it's time consuming to do simple things directly against it doesn't surprise me in the same way I'm not surprised that writing todo app directly against POSIX abstraction would be time consuming. It's a great way to learn how these interfaces work though.
It's not an uncommon way to get rich. Eastern European privatisation after the fall of the Iron Curtain often failed after management of corporations owned by many small shareholders borrowed company money to themselves, something that is obviously almost criminal negligence, certainly something that should get you removed from management ASAP. But before the shareholders managed to do anything, the money was used to buy controling stake in the company and weak protection of rights of minority shareholders took care of the rest.
As much as I like the described move from "functions" to "containers", solutions like KNative / Cloud Run are still inherently more hackable than solutions like Fargate.
It's good to have properly defined, stable, open interface for compute workloads (containers as defined by OCI), so we don't have to lock ourselves into whatever shape of runtime environment our current cloud provides for their flavor of FaaS. So we don't have to learn cloud-provider-specific tooling, getting certifications for handling various tasks at AWS, becoming 2010s variants of Cisco-certified network engineers of the previous age.
But it's even better to have a properly defined, stable, open interface for orchestration too. To be able to run stuff locally. To be able to extend things. To ease the lock-in cloud providers currently have. To be able to actually understand what happens under the hood. And last but not least: to enable rise of open source solutions for higher-level abstractions, like KubeDB.
I agree. If a smart investor notices that a company business model stops working the moment governments pass legislation introducing carbon markets, it's a good investment strategy to short the stock. But notice that it's the government that is doing the heavy lifting here, investors are just diligently passing the shock from the future so resources are not wasted.
If there is a climate catastrophe going to happen, but no government is going to punish companies responsible, it won't make sense to try to do that for yourself -- in the same way bad corporations are freeriding on climate, bad investors are freeriding on your efforts to punish such corporations.