> When did the industry put the onus on the user to understand how the computer works?
Just after the turn of the century, that was when there was a big shift in the industry to move all user interface design work to artists, and away from original user interface specialists. The whole profession of user interface designer (one who understood "form follows function") ceased to exist in the early 2000s, as all work was assigned to graphic designers (who only understand aesthetics).
This movement can be seen clearly in the evolution of widget toolkits for desktop applications, which peaked in usability in the late-90s/early-2000s, and have been losing usability while getting prettier with every iteration since.
(I was editing when you repplied so I'll add it here for you:)
And just to add, you can have "chargeback" for PIX as a separate service, most banks offer PIX insurance that is basically CC chargeback by a different name. But the key is that it is separate from the payment infrastructure itself, it is an insurance service that you contract separately. And that separation ins very important, the insurance company can't roll back transactions arbitrarily, or deny people access to the financial system, they have to pay the victim and then claw back their money in court, which is the appropriate venue to decide who is right or wrong in a transaction.
That is by design. It separates the payment processor so it does just that, just payments. It is like money, once you give it to someone else there is no automatic way to fish it back from their pocket to yours. The correct avenue to deal with fraud, bankruptcy and other malicious actor is the small claims court (or civil court, or criminal court).
The moment you start burdening the payment processor with the roles of judge/referee over all goods and services you end up with the mess we have with CCs where Visa/Mastercard are morality czars that dictate what goods and services are valid or invalid, nuking people and companies out of modern society for their own arbitrary reasons.
Edit: And just to add, you can have "chargeback" for PIX as a separate service, most banks offer PIX insurance that is basically CC chargeback by a different name. But the key is that it is separate from the payment infrastructure itself, it is an insurance service that you contract separately. And that separation ins very important, the insurance company can't roll back transactions arbitrarily, or deny people access to the financial system, they have to pay the victim and then claw back their money in court, which is the appropriate venue to decide who is right or wrong in a transaction.
What makes Portugal's situation unique is that it is a small population that is eclipsed in models by the bigger weights of the much bigger population of Brazil.
Yes, there are much smaller European countries, but those are generally the only source of truth for their specific language, so the context of a LLM query in that language steers the LLM towards facts from that country, for example, if I ask a big generic LLM something in Latvian then it most likely will answer something relevant to the context of Latvia. But Portugal, being the much smaller user of its language, have the somewhat unique problem that if I ask a generic model something in Portuguese it will probably answer something related to Brazil instead of Portugal.
Maybe the UK and Spain have somewhat similar struggles, but I suspect that none has it as bad as Portugal in that regard.
> Ethanol is not a good fuel source for something like a personal vehicle.
It is about as good as gasoline (or better), Brazil has been running a good chunk of its personal car fleet on sugarcane alcohol for decades. Yes, EVs are better than ICVs, but there is nothing uniquely bad about ethanol that makes it worse as a fuel source for a personal vehicle than any other combustive fuel.
Wrong because Brazil DOES fuel cars on sugarcane alcohol. Most petrol stations in the country have pumps for sugarcane alcohol, nearly all the ICE cars sold in the last two decades have a flex engine (in the past you had to chose when buying the car if you wanted a alcohol engine or a gasoline engine, now the engines just takes whichever you trow at it and adjusts the injection accordingly), and roughly half the personal vehicles in the country run daily on alcohol. That fact has softened this oil crisis a tiny tiny bit in the country (when oil is expensive many people just pump alcohol instead of gasoline).
And right that electricity is much cheaper than gasoline or alcohol, so people are changing to EVs because of the cost savings in fuel. In fact electricity was already much cheaper even when the price of oil was down, what was holding back EV adoption in the country was never the price of oil, but the relatively high purchase prices of EV vehicles (the average upper-middle-class Brazilian can't afford a Tesla like an American or European can), but the latest batch of basic EVs (like the BYD Dolphin-mini/Seagul) started to break that barrier about one or two years ago, and are now on the top sales charts.
My last phone was all glued and the entry point was the screen. The repair guy said there was a 50% chance the screen would break in trying to unglue it so it was not worth the try. It was a shame, it was a decent phone killed prematurely by a faulty battery.
On my Debian system I use the flatpack version of Steam, it comes with the 32bit stuff inside the container, so you don't need any 32bit packages in the OS.
I'll have to agree to disagree. In my experience IDEs are the one type of software that were always slow, Eclipse is two decades old, and it's slowness was on a whole different level.
The move thowards SaaS started long before the rise in prominence of F/OSS, it was the creation of the Internet that was the catalyst to the rise of SaaS, nothing to do with the FOSS-vs-Proprietary fight. In fact, in the beginning of the Internet, the first wave of SaaS was all built on top of proprietary solutions, Oracle was the king, Sun Java was the up-and-coming go-to platform.
You lost me on being against ABS. I understand your position being that automation reduces the senatorial feedback, it is an abstraction with loss of information, but in the case of ABS there is nothing a driver can do better than an ABS, no matter how much feedback they have.
Regarding the other examples of driving aids, yes, those are abstractions with some drawbacks, and a top-of-the-curve driver could do a better job without it. But still they could be a net positive because of the benefit they bring to not-that-good drivers.
Screens though, those I agree 100% shouldn't be on a car.
> There is nothing inherently wrong with stick built houses using drywall.
There are some things wrong, just to list a few:
- Stick+drywall building have terrible sound isolation, that drives people away from more efficient high density housing options, everybody wants a fully detached house so the air between the houses may help isolate you from the neighbor's noises.
- Stick+drywall needs more diligent maintenance (a simple leak may destroy a house), so again it drives people towards fully detached houses, otherwise your neighbor's bad maintenance may cause troubles for you.
Good walls make good neighbors. I'm convinced that big part of the American aversion to urban living comes from their use of sticks+drywall.
For us software developers, it seems like the shipping industry has the container equivalent of a memory leak (a "container leak" if you will). Then the stacking rule change is the equivalent of simply adding more memory to the system, it doesn't fix the problem, but it buys you some more time of normal system operation before the next out-of-memory crash. Hopefully they use this time they bought to work on an actual solution to the original leak.
Just after the turn of the century, that was when there was a big shift in the industry to move all user interface design work to artists, and away from original user interface specialists. The whole profession of user interface designer (one who understood "form follows function") ceased to exist in the early 2000s, as all work was assigned to graphic designers (who only understand aesthetics).
This movement can be seen clearly in the evolution of widget toolkits for desktop applications, which peaked in usability in the late-90s/early-2000s, and have been losing usability while getting prettier with every iteration since.