I have yet to find a F50 company that has been completely “moral” from the start to now. They have all at some point stepped on the backs of numerous people (slave labor, toxic/unsafe working conditions), governments (tax dodging), and entities (ie, other companies) to get to this point. C-level executives are the worst offenders.
I do agree with the points in article that k8s is not a good fit for development environments.
In my opinion, k8s is great for stable and consistent deployment/orchestration of applications. Dev environments by default are in a constant state of flux.
I don’t understand the need for “cloud development environments” though. Isn’t the point of containerized apps is to avoid the need for synchronizing dev envs amongst teams?
Or maybe this product is supposed to decrease onboarding friction?
It's to ensure a consistent environment for all developers, with the resources required. E.g. they mention GPUs, for developers working with GPU-intensive workloads. You can ship all developers gaming laptops with 64GB RAM and proper GPUs, and have them fight the environment to get the correct libraries as you have in prod (even with containers that's not trivial), or you can ship them Macbook Airs and similar, and have them run consistent (the same) dev environments remotely (you can self-host gitpod, it's not only a cloud service, it's more the API/environment to get consistent remote dev enviornments).
Yeah, exactly. Containers locally are a basic foundation. But usually those containers or services need to talk to one another, they need some form of auth and credentials, they need some networking setup. There's a lot of configuration in all of that. The more devs swap projects or the more complex the thing you're working on the more the challenge grows. Automating depedencies, secret access, ensuring projects have the right memory, cpu, gpu etc. Also security - moving source code off your laptop and devices and standardizing your setups helps if you need to do a lot of audit and compliance as you can automate it.
In my experience, the case where this becomes really valuable is if your team needs access to either different kinds of hardware or really expensive hardware that changes relatively quickly (i.e. GPUs). At a previous small startup I setup https://devpod.sh/ (similar to gitpod) for our MLE/Data team. It was a big pro to leverage our existing k8s setup w/ little configuration needed to get these developer envs up and running as-needed, and we could piggyback off of our existing cost tracking tooling to measure usage, but I do feel like we already had infra conducive to running dev envs on k8s before making this decision -- we had cost tracking tooling, we had a dedicated k8s cluster for tooling, we had already been supporting GPU based workloads in k8s, and our platform team that managed all the k8s infra also were the SMEs for anything devenv releated. In a world where we started fresh and absolutely needed ephemeral devenvs, I think the native devcontainer functionality in vscode or something like github codespaces would have been our go to, but even then I'd push for a docker-compose based workflow prior to touching any of these other tools.
The rest of our eng team just did dev on their laptops though. I do think there was a level of batteries-included-ness that came with the ephemeral dev envs which our less technical data scientists appreciated, but the rest of our developers did not. Just my 2c
Sarcastically, CDE is one way to move cost from CAPEX (get your developer a Mac Book Pro) to OPEX (a monthly subscription that you only need to pay as long as the dev has not been lay off)
It's also much cheaper to hire contractors and give them the CDE that can be terminated on a moment notice.
The functionality you refer to is probably the creature comforts (ie, multi zone A/C, memory settings for front seats, …). But the essentials of a car (ie, transmission, wheels, structural integrity, windshield wipers) haven’t changed for decades.
What has changed though is:
- increasing size of vehicles due to increasing insecurity of American buyers
- a large majority of class C holders largely unprepared for the size of these vehicles
- this gives manufacturers the opportunity to stuff as much tech junk into these vehicles to give these less qualified drivers more assistance
- coincidentally, all of this tech junk comes with a very high premium for manufacturers and dealerships
Fear sells in this country. 9/11 changed the game.
Many of those essentials of a car have changed a good bit in the last few decades. Hybrid drive trains have become far better and far more common. Electric vehicle drive units are far better than they were before. Transmissions these days are far more complicated and achieve much better mileage than older transmissions and allow people to select gears electronically despite otherwise being an "automatic".
Designs for structural integrity are also different. Look at a 1997 Honda Accord and how big its windows are and how skinny those pillars are. Look at a modern Accord and see how big its pillars are. Look at a crash test of a 2000s Town and Country and compare that to a modern Pacifica. Radically different.
reply