• 0 Posts
  • 428 Comments
Joined 2 years ago
cake
Cake day: June 21st, 2023

help-circle



  • The problem comes in so many directions in real life though. Say your company has a very large database. Replicating it across regions means you’re paying for data ingress/egress and more than one region’s copy of that already sharded and/or duplicated database. It even applies when transferring data across AZs in a given region. Backing it up to S3 is expensive, backing it up to Glacier is cheaper, until you ever have to do a restore, and then you have to lay off half the staff to pay for it.

    Other issues can arise, possibly through the fault of yourself, sometimes at the fault of Amazon, if data traffic routing has a glitch and data is routing to the wrong place. The onus either way is on your company to show Amazon the receipts if you expect to get credits for the overage. At larger scale, this could be hundreds of thousands of dollars in overage. Easy to torpedo smaller companies with one mistake.

    They didn’t used to nickel and dime as hard as they do now, which doesn’t help, but outside of history, they set up AWS to be the biggest slippery slope of wallet-deletion, as almost every move you make costs money. Entire companies exist to manage your AWS costs (for more money, of course) and other companies’ products you may use that are hosted in your infra may accidentally delete your wallet if you don’t constantly monitor them.

    Using AWS cost-efficiently is only accomplished by ostensibly day-trading your cloud resources like a high frequency stock trader, capitalizing on unpopular/weird system types, and keeping your code as portable as possible.

    …but if one didn’t care about cost, one would probably get pretty good reliability out of them, sure.


  • Not to be that guy, but having had to repair ovens with these GE control boards on and off, what that display is saying (as the oven is on) is “PRE” for pre-heating.

    The updoot lover that created this image just photoshopped the E over the R. You can tell as the segments on both Es are exactly the same in brightness and intensity, which is highly improbable in simple digital electronics design used for these types of boards.





  • Windows ME had the same fixed 64KB user resources and 64KB GDI resources memory limits as Windows 95 and Windows 98 for system resource allocation regardless of how much actual RAM you had. Since ME was more resource-intensive than the previous versions, you could run out of these resource allocations while still having very much free RAM much faster.

    The end-result was the computer becoming unusable even though you had resources available that the OS could have otherwise used. Certain inefficient applications like I believe Quicken could snarf up all of the system resources so you had to restart with everything you could disabled to run that one application. Same computer on Win2K would run circles around WinME.





  • The muppets in the Federal government are trying their hardest to make this occur so they can try and find some loophole to go ahead with their martial law plans to arrest all the people they don’t like that week. What we’re likely seeing is mature restraint on behalf of firearm owners.

    Some years back, the quote was something like, “as soon as you discharge your weapon, you are looking at spending at least $10,000 from legal fees” (if you don’t have firearm insurance and/or if it would even be applicable) - that number is probably tenfold now. Not to mention the very likely personal harm others have mentioned.

    Legal fees or not, being dead is pretty hard to come back from.