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

help-circle











  • Just a reminder, this shithead crossed state lines to dump gas on the fire of a protest

    The “crossed state lines” thing really irks me because does nobody know that maps exist? I’m thinking about crossing state lines today because I need to get more baby wipes. Shithead went to the next town over, which just so happened to be in a different state.

    But let’s also not forget he went and partied with KKK members immediately after posting his crowdfunded bail, just in case there’s any questions on how much of a shithead he is


  • In a race where it’s estimated 40k people will decide the entire outcome, getting 20% of the country on your side is good numbers.

    Republicans have been saying shit about eliminating income taxes for years, or even flat out eliminating the IRS. I don’t see this specific policy turning "millions"of voters like you say.

    The best thing trump can do is get voters excited. Voter turnout is abysmal in this country. Whoever gets more people to actually show up to vote wins. Joe Biden was a shoe in before he hard-backed Israel and now it’s a toss-up



  • Take a look at the JOLTS data

    516k job openings in April, 385k separations and 382k hires. That’s a deficit of about 100k jobs that aren’t being filled in manufacturing alone. The problem isn’t a lack of manufacturing jobs, in fact it’s the opposite. We have over a hundred thousand manufacturing jobs we can’t fill, and this matches what I hear through the grapevine at my work which does contract industrial cleaning. People don’t want those jobs, and people take advantage of the opportunities available to them to get out of those jobs. Trump would destroy the countries economy if he actually managed to implement this plan



  • The thing I don’t like about laptops are 1. Noise and 2. The bursty CPUs just don’t mesh well if I want to run a swarm of VMs or need to just run a big compress/decompress process. I watched one laptop slowly throttle itself all the way down to 700mhz while I was messing with a bunch of VMs and it really made me miss having a desktop where it can just chill at 5x the speed at 100% utilization and chew through whatever is being thrown at it


  • 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.)