If you're not developing k8s operators, you're calling the api server directly, then complaining about lock in, then that's a skill issue. If you're developing k8s operators, then you should use a tool like kind for integration tests and dependency injection for other stuff and the concept of lock in doesn't make sense. You can also deploy your helm chart directly to kind.
Yes you can? The container should be completely agnostic to the fact that it's running in kubernetes. You can do config the same way. Configmaps are mounted as regular files and environment variables. The application doesn't care if the configmap came from the cluster resource or a file your created on your dev machine with dev credentials. You can mount local files into the container yourself. It's docker run -v "source:destination" I think.
How is the kubernetes secret API lock in? Genuinely wondering - were you trying to use that deployment yaml for something other than a kubernetes deployment? For most applications, you should be mounting the secret on your application, then you can inject it as either an environment variable or a json file that your application reads in an environment agnostic way.
Then, on the backend, you can configure etcd to use whatever KMS provider you like for encryption.
But is every feature in a browser supposed to be standardized? Like, it's against the rules somehow to develop features without asking permission from Apple and Mozilla?
OTOH, are all of the browsers supposed to move in lock step? Is chrome supposed to wait for everyone else's approval before launching any kind of feature?
I think the hope is that you just start there. They might have migrated the meeting room devices. Why would you set out to replace *everything* at once? Do something, get some revenue/experience, then try to fan out.
Still a ways to go. I found out part of the reason for my linux bluetooth woes is that a settings in bluetooth called “JustWorks” and “FastConnect” default to off. Like. Why?
As if most linux users who enable bluetooth want it to connect slowly and not work.
Being a bit hyperbolic intentionally but the point still stands
Not sure where I fall on that one. In business, it is said that one ought to focus on core competencies and let other companies handle the rest. Why shouldn’t a country do the same? Should low level manufacturing be a core competency of the US? Why? Turning steel into screws is certainly lower margin than turning screws and engines into airplanes.
Here's the hope that the demand for software continues to increase as developer productivity rises, and that increases in developer productivity are partially captured in higher salaries.
It feels that way for a lot of privacy concerns. "Telemetry" is the scare word for debug log, core dumps, and stack traces. I think it’s completely reasonable to want those.
I don’t really agree with this. The vast majority of the time, if you encounter an error at runtime, there’s not much you can do about it, but log it and try again. From there, it becomes about bubbling the error up until you have the context to do that. Having to handle bespoke error type from different libraries is actually infuriating, and people thinking this is a good idea makes anyhow mandatory for development in the language.
It's really gonna depend on the project. When my hobby project was greenfield, the AI was way better than I am. It was (still is) more knowledgable about the standards that govern the field and about low level interface details. It can shit out a bunch of code that relies on knowing these details in seconds/minutes, rather than hours/days.
Now that the project has grown and all that stuff is hammered out, it can't seem to consistently write code that compiles. It's very tunnel visioned on the specific file its generating, rather than where that fits in the context of what/how we're building what we're building.
Why not both? Also detection?!? That’s crazy. Everybody should be doing this. The raison d’etre for these sorts of bans is their perceived negative health consequences.
You almost certainly safer using whatever PED you can get your hands on if you’re trying to climb Everest.
Having worked on a graphical application in rust for a (albeit not a complex one) computers today are fast.. latencies top out at 3 ms with cpu based rendering in an application with just a few rendering optimizations.
The fact that you just draw on the screen instead of doing whatever html parsing / DOM/IR is probably doing it? And doing rendering on the gpu means extra delay in the processing moving from cpu to gpu and being a frame behind because of vsync.
I think your perspective on this matters a lot less than that of the researchers. Their perception is that what’s happening at Harvard and NSF is fascism.
The perception is that we have a gestapo in ICE arresting mayors and judges, an admin talking about suspending habeas corpus, going after scientists who come to conclusions they don’t like, and just gutting funding for research in general.
You can say, “oh this is hyperbole” and “these people are wrong to leave,” but all that really gonna matter is that they were terrified and left.
I've had great success by asking it to do project design first, compose the design into an artifact, and then asking it to consult the design artifact as it writes code.
I can see a world where there's a private alternative to the FDA going around and certifying that food is safe for consumption. I just know that the world before the FDA didn't have one, and the FDA works well enough that I'm not willing to find out. I think this has a lot of parallels to software - if it ain't broke don't fix it.
What I hate about this argument is that the FDA does not predate civilization. In fact, it's a relatively recent development. Not only has this idea been tried, but throughout most of human history, people lived in the world you describe, died of salmonella, and the people who lived in that world decided they'd be better if that wasn't a thing anymore.