I would say that in general dynamic type languages are problematic in a large codebase without strict safeguards (Any everywhere, untested paths, lack of test coverage, large methods with different return scopes, etc.).
I've worked a long time in C++ land in large codebases and the issues there are different, but to undig a project from the spaguetti land is like pulling teeth.
> It is worth noting that despite all this cheap sovereignty talk from Brazil’s president, in practice Brazil would not be able to operate Pix at that scale without heavily relying on American hyperscalers companies.
> American companies are great to do business with.
US officials involving themselves in your national market because they are unhappy with the market share of their companies in it, with the implicit threat of stopping other areas of trade if you dont allow the companies to gain a larger market share makes US companies too untrustworthy to do business with. If Trump implements a trade ban for Brazil, will these hyperscalers continue providing the service at their own risk, or are they going to prioritize their state over their customers?
I would assume the answer will be the latter.
Given that, I believe it is in Brazil's (and most other states) best interest to divest and reduce partnerships with companies operating in the US
> US officials involving themselves in your national market because they are unhappy with the market share of their companies in it
Just to clarify, for anyone who’s been paying attention to the matter, it’s clear that the true reason for that Section 301 investigation is not due to Pix stealing market share of MC/Visa. In fact, if you check Brazil’s central bank own data, Credit Card usage has not gone down since Pix came in. What Pix really replaced was physical cash.
It's 100% a HMI and moving costs to the other end of supply chain.
We can have optimized automation in warehouses/logistics, but if you talk to any site manager you learn very quickly that no one wants any downtime or impact to their operation to introduce new machinery or optimize traffic, etc. If it is not built with that from the start it's very hard to introduce it later on unless there is a very clear deployment path and cost structure.
And boy, robotics currently has any of those today. Sure, move those billions in to R&D. Time will tell.
Correct me if I'm wrong but for Meta/Google, past layoffs in France, Germany, Netherlands were done on a voluntary basis. It also took many months between the announcement and the actual layoff and the severance was competitive.
One may argue that salaries are lower and there are less opportunities in tech in those countries - because of stronger regulation - but I think the layoffs procedures are objectively much more favorable for employees.
Layoffs don't happen the same way they do in the US, at least in Germany. It's expensive to lay someone off due to dual-party notice period requirements. "At will" is a foreign concept here.
I believe Microsoft biggest achievement is being capable to stay relevant for the past 50 years, largely due to enterprise.
If you take a close look as an user, all their products is half-baked in some way (inconsistent behaviors, dark patterns, poor support, etc.), good enough so they can lock you in and hold your data hostage with time.
I've worked a long time in C++ land in large codebases and the issues there are different, but to undig a project from the spaguetti land is like pulling teeth.
reply