Use private mode exclusively. You will start getting into the captcha hell in a day or two.

I configured Firefox to delete all cookies on exit, except few whitelisted sites. So most of the time I have to accept Google privacy policy if I search there. Other than that, I never got into the captcha hell when trying to do a Google Search.

There are some sites I can't login at all unless I change the browser. SoundCloud is one of them.

Could be that IP Address/ISP reputation is also a factor for the variation in results.

So this serverless solution has a watchdog process always running and mapping requests to the correct process? It that more like a server than serverless? Will the next optimisation be launching one thread per request? In which case we are back to square one (:

You're quite right but as a customer I frankly don't care about how do they it as long as management and deployment are easier from my side.

At one point you do hit a limit on what you can do by cold-starting (almost) everything anyway, right? Let them optimize so they are competitive, and now they've given me a good reason to evaluate them.

>Will the next optimisation be launching one thread per request?

That is what Cloudflare Workers do. One v8 isolate thread per request.

More and more it appears that k8s is designed to extract maximum value from the tenants of the cloud companies.

You need to connect your cluster to public Internet? No problem that's $x for each load balancer (whether its needed or not).

Ohh you are feeling the whole thing feels like a blackbox and difficult to debug or observe? No problem that is $x for data dog.

Gcp is the worst when it comes to setting up k8s with preemptive nodes. Thought you could get away with preemptive nodes? Not so fast, we restart all the nodes together at end of 24 hours period so that your multi node cluster will have zero availability for 5 minutes everyday. Or jump through hoops to killing your own nodes periodically to keep them all restarting at the same time.

Those aren't features of Kubernetes.

If you like you can install a free ingress such as NginX and route traffic to it.

If you like you can just have logs on your physical nodes and go look one by one, just as you would have to before things like k8s came along. Datadog is a value add. It's not essential.

GCP preemptible VMs are nothing to do with k8s - they are literally designed to be short-term (up to 24 hours) VMs to do things with. Yes, GKE can use them, but not as persistent resources. That's not what they're for.

Here's what they're for:

> Preemptible VMs are Compute Engine VM instances that last a maximum of 24 hours, and provide no availability guarantees.

I.e. don't try and "get away with" them. There are plenty of options for cheap K8s.

Yes, you can setup your own kubernetes if you want, using just ec2, but nobody wants to do it because it's easier to just pay.

I think k8s actually saves you money, because it allows you to use your resources better.

Yep - you can also just use a VPS or even some Raspberry Pis in your home.

The ingress can be free with Nginx but not the inbound firewall rule that passes the traffic to Nginx. And 'coincidentally' it costs the same $ as using their load balancer which automatically has this rule applied.

You're talking about a cloud provider's fees, not kubernetes.

It sounds like it's just setting up the load balancer for you behind the scenes? Kubernetes isn't a load balancing engine, to my knowledge. It just sets up containers and stuff.

If there is anything nefarious in the design and rollout of k8s it's just to make it uncool to run something small.

I've worked with it for a bunch of years now and run a cluster at home, but I do hate that it scales down so poorly. Is so much work to run a bare minimum, if not for SME-purposes but for local development. It's just starting to get acceptable.

My only real gripe with GCP is that every project is set up to use their premium networking tier by default.

I'm not sure what value your harsh tone adds to your comment. Sharing experiences like this publicly benefits everyone. It obviously exposes blindspots in one's knowledge and it is expected that noone knows everything. That is the point of the. Comments functionality in HN. So that we can all share things that we know and absorb things we don't.

I personally enjoyed this article and learnt a few things from it. I learnt a few things from your comment too but it would have been better without all the harsh words.

Because its not easy to get fuel for nuclear reactors as there is an ever lasting cloud on India's nuclear status.

Existing reactors also run on partial capacity due to lack of fuel. What little is produced in the country has to be rationed between defence and electricity generation.

I continue to be surprised by this despite logging some good number of Rust hours. Cargo run and it just works as expected even with complicated data sharing code etc.

Of course most of the work gets done by the compiler safe guarding and guiding during development. People make noise about lifetimes etc but once you are ready to pay the penalty of Arc (and in most cases if you are using lifetimes you are already on the verge of using Arc). Same with using cloning as needed. End of the day, these incur a predictable and acceptable performance penalty than many other languages do while providing good safety.

There should be a reputation score for new releases on npm with scores from beta users who are part of the community. Sounds similar to app store but more community controlled.

In general, there should be a risk assessment score on npm for each package sourced automatically from different criteria like how many maintainers are there in a project, ownership changes etc.

Also, making the new package available only to few % of random users would have limited the impact.

Overall this pull with complete trust is just asking for trouble.

And yeah, this developer needs to be committed to a facility for his own good (if this doesn't qualify him for that then I don't know what will).

That's literally gatekeeping. It took me so long to get enough karma on HN to be able to leave a comment. This would just shift the system to be gamed by bots / upvote4upvote, and keep existing hegemony in the community on who gets the power and say in porjects. Do not want.

The flags sound real and its lucky for you they are showing up early. I would suggest to talk to someone in the inside through your network (may be from another team). If that chat doesn't seem to go well, then definitely back off this offer and start interviewing again.

Wow that's insane. They should start with banning power hungry data centers whose whole purpose is to serve ads first.