So someone looking for the perfect languages while actively using the only two languages I actively avoid is very strange to me.

C# has close to zero community and only really works properly in Windows which is far past its glory days. Except for Microsoft aggressively pushing it as a Java alternative it has no right to exist.

Rust is an overcomplicated subset of C++ that solved memory problems the most recent versions of C++ don't have anymore, and only survives by aggressive marketing, full of grouping things together that don't belong together, like C/C++. And memory safety / use-after-free.

If C and C++ are basically the same because they have access to manual memory allocation then Rust/PHP are also basically the same.

And Rust's borrow checker only solves use-after-free which statistically are 10% of memory related vulnerabilities. Not "memory safety" of which 60-70% is just array out of bounds.

Really the worst two languages that both only survive in aggressive marketing.

We also migrated from AWS and Azure to European cloud.

But as you can see Mac is still from the USA so although the making things European sounds nice, it's only part of the reason.

Mac has greatly improved with the M chip line. Windows has greatly degraded over time.

AWS and Azure are by now something like 10x the price per year of just buying the hardware yourselves. They always compare the price to the salary of a senior engineer in San Francisco if you include vested stocks.

However installing a database with the correct security settings has also become a lot easier since AWS started.

And if they constantly scan your code with various settings and updates you will spend hours a day reading, trying to understand locally coherent but structurally incoherent vibes trying to pinpoint the exact reasoning flaw. Exhausting.

Literally 2 meters from my desk is a 2x RTX-4090 server and many times I just use my 8 year old GPU anyway so you don't need it.

I use VIM and I get some inspiration from LLMs sometimes, but me and other developers always after some time give up and just quickly do it manually.

AI Agents will just full the code with maaaassive swaths of texts it will just make a project unusable.

We even get paid to turn client's AI LLM Claude sketches into real programs.

But it cannot be done because it only allows AppStore content with a 30% cut for Apple.

Technically it's not challenging as you can see with this new MacBook.

In DHL the link to get tax documents is already broken for a year or so, so I cannot get VAT back on DHL shipments.

With FedEx I can but it's a manual process of screenshotting a bank transaction and emailing a specific email address with a shipping number.

When tariffs started all the servers of the shipping companies went down.

So I highly doubt they will just do some computer magic.

From experience I assume they will "accidentally" run into all kinds of technical difficulties making it a 274 step process to get the money back.

For scale: Shopify, a software company by heart, with 170bn market cap and 3500 engineers employed, does not have native VAT support, required in the Europe which accounts for 15-20% of their revenue. All they would have to do to support this is add a checkout field "VAT number" that shows up on a pdf invoice.

So to assume a shipping company will just work some computer magic is really far fetched. The FedEx page only lets you login after you refresh the page exactly once already for more than a year.

80% of memory safety bugs in C++ are just basically "array out of bounds", for which you don't need a memory checker at all just array bounds checks which LLVM has enabled by default for Rust but you can also use it for C++.

70% of vulns in C++ are memory related but only ~10% of those would be caught by borrow checking. Most are already caught by forcing object initialisation and array bounds checking. Only use-after-free is caught by either borrow checking OR OTHER TOOLS like ARM has 4 bits in addresses that can encode if the memory location has not been pulled from under you.

So aaaaall this trouble if the borrow checker to have in some cases max 10% fewer vulnos.

I'm not going to switch to Rust/PHP just for that little memory safety bonus.

In a company you will want to cultivate this, since interactions within the company are far more frequent than with the outside world.

Replacing solid code with vibe code basically, in the name of safety.

sudo-rs for example which is specifically mentioned has a drastically worst safety record than the C sudo.