• 1 Post
  • 381 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle







  • UN, which… failed to keep dictatorships out

    The UN while created with noble intentions certainly fell for the paradox of tolerance. They tolerate the dictatorships and human rights abusers because if they didn’t they’d be much less empowered to take action against them, or worse they’d form their own competing UN made up of nations motivated to join them and you’d just end up with another NATO and Warsaw Pact for example. It’s damned if you do, damned if you don’t.

    Ultimately the challenge comes down to how do you ultimately tame the leaders of the world who have absolute power. The founding fathers of the United States of America thought they had the solution with democracy and the many checks and balances they implemented into this new form of government they setup, but even that has its challenges and failures that they never could have forseen. The UN was the next experiment, trying to take the similar principles onto the world stage, and it’s been less successful (but at least has had some successes)








  • x86-64 is a CISC architecture

    In many cases it’s actually RISC under the hood and uses an interpreter to translate the CISC commands and run them in the most optimal manner on the silicon

    ARM and RISC-V absolutely scale up to multi-hundred watt server CPUs quite easily. Just look at the Ampere systems you can rent from various VPSes for example

    The big benefit that ARM and RISC-V have is they have no established backwards compatibility to keep carrying technical debt forwards. ARM versions their instruction sets and software has to be released for given versions of ARM cores, and RISC-V is simply too new to have any significant technical debt on the instruction set side.

    Atom cores were notable for focusing the architecture on some instructions then other instructions would be a slog to execute, so they were really good at certain things and for desktop use (especially in the extremely budget machines they got shoved into) they were painful. Much like how eCores are now. They’re very carefully architected for power efficiency, and do their jobs extremely well, but an all eCore CPU is a slog for desktop use in many cases



  • My experience when I worked in support for a device manufacturer is that if you get high enough in the support tree and can demonstrate that this effects you (and the support person will also have a matrix of affected devices) you’ll still get a repair/replacement outside of warranty for them bricking your computer with a bad update.

    We had a specific instance where a specific budget model of phone sold by Boost mobile would brick after a specific update for people who had subsidy unlocked it and taken it to a GSM carrier such as T-Mobile (this was shortly pre-merger) or AT&T. This update rolled out about 2.5 years after this devices release, so most customers were ~12 months outside of warranty. Since the scope of affected devices was so narrow our directions from the top was to replace affected devices regardless of warranty status, and the replacement would come with a standard 30 day replacement warranty

    So in short, I would expect HP to repair/replace affected devices that bricked after this BIOS update regardless of warranty status, but I would expect some amount of hassle in terms of reaching a specific support department before you get assistance and standard refusal of service for customer induced physical damage (smashed screen, smashed ports, mashed potatoes in the ports, badly bent, etc.)