relying

If you're relying on a third-party API, you cannot, and that's the distinction that the OP is asking us to take more seriously.

If a system is not certified then you are relying on Linux developers making it work - they may do so, but are often hindered by drivers or small tweaks to hardware.

Again scheduling order is undefined so the order may change again in 1.6, explicitly relying on it would be an idiotic idea.

Please do your own research before relying on any of this, of course!

Maybe you eventually realise that writing your own task for rabbitmq and your own workers is simpler than relying on someone elses complex code.

By controlling the device, browser and the platform - they have an option to integrate their own search offering instead of relying on third parties.

I do think there are huge benefits to simplifying life, and relying less on all these time-consuming habits domesticated humans have invented.

But when you start relying on it, you will most likely lose it all when you lose your job because your market rate is considerably less.

In the centralized load balancer infrastructure, you end up relying on DNS so that your users microservice can talk to the shopping cart microservice (for example).

OpsGenie first implemented push notifications while PagerDuty was relying on people not knowing the competitive landscape and had a web-based Android app with SMS for years.

But some developers were retrieving the library from a random Android device to link against, but then relying on the OS to provide exactly those same symbols.

Convox achieves much of its stability and scalability from relying on hosted a AWS services.

Both are "hosted", relying on Java and JavaScript for low-level things and providing clean interop for those things.

You can poo-pooh security through obscurity but we're all relying on the "infeasibility" of defeating various systems.

"[...] starting around 2030 as processing power becomes cheap enough [...]" Surely you are not relying on an (arguably naïve) extrapolation of Moore Law-type progress?

Rust instead is based on different principles, specifically the idea of "borrowing", to handle memory management instead of relying on either extreme of "do what you want" or "the GC will clean up after you".

Relying on the free hand of the market to take care of things depends on there being a market, but any given company is massively incentivized to distort the market as far as humanly possible.