6,703 karma · joined December 10, 2010
>>> Remove the explanation parts and only leave yaml in place from above response. apiVersion: apps/v1 kind: Deployment metadata: name: my-deployment spec: replicas: 3 ...
Alternatively this worked as well >>> Write a YAML file with kubernetes deployment object in it. Response should only contain the yaml file, no explanations. ... ions. ```yml apiVersion: apps/v1 kind: Deployment metadata: name: example-deployment spec: replicas: 3 selector: matchLabels: app: example-app template: metadata: labels: app: example-app spec: containers: - name: example-container image: nginx:latest ports: - containerPort: 80 ```
I am asking because I get the feeling that there's not much you can do and Google's way is the only thing anyone can do and still be in business. Now how much they rely on ad revenue and how much more they have to compromise is another story. Probably Google should be thinking of including better search to paying Google One customers?
Biggest problem is inertia - that would have to be solved - one way is that Google search gets useless and people have an option to move to something better. I doubt this will happen. Other way is someone builds not just a marginally better product but a 10x better product and people move there - I don't see that happening anytime soon either.
> Thank you for expressing interest in potential job opportunities at EdgeDB! At this moment, we are not actively hiring.
Posting link points to home page. So just like an ad or does the careers page need updating?
But it was predictable - Andreas comes from Apple background so.. The other thing is no one can build a browser alone - the ability to attract the right people is what differentiates a mainstream usable browser and a toy one. IOW focusing on adding another language that is not as popular amongst the right developer demographic seems like the wrong thing to focus on at this stage.
Crowdstrike knows the computers they're running on, it is trivial to implement a system where only few designated computers download and install the update and report metrics before the update controller decides to push it to next set.
Sure they have recently implemented some features like IndexedDB but the data does indeed show that they dragged their feet!
Just scroll down - the jobs link in an anchor to it, for some reason it doesn't scroll there.
You see if you don't meddle with my terminal data in the first place I would feel much better that I am in control of my data, and not reliant on. 3rd parties to accidentally drop guard and leak my data out.
> This release adds some safety valves to eliminate the risk of private information leaving the terminal via the AI endpoints.
If it's still not clear - I don't want my terminal to even have the possibility of leaking my data.
They had an advantage after all the other electronics brick and mortar retailers cratered but they blew it away by dumbing everything down and making the store experience boring.
When you are signing up for a job it's not just the money and the physical things you do - it's also the intangibles, the time spent in unproductive meetings, time spent afterwards feeling unproductive and worried, the resulting stress you have to manage etc, it all adds up and takes away something more than the money. I would argue that well managed jobs with some semblance of stability, human connection and predictability/routine are quite pleasant and easier to do compared to Software/IT.
x64 is here to stay with its incredible ecosystem and OSS friendliness - Coreboot, Intel and AMD GPU drivers, great choice of operating systems and apps with a fairly long usable lifespan even with Windows updates.