The Internet is bad.

  • 0 Posts
  • 35 Comments
Joined 2 years ago
cake
Cake day: August 4th, 2024

help-circle








  • People are now conditioned to need INSTANT GRATIFICATION FOR EVERYTHING ALWAYS!

    “I want a Steam Deck! I can’t actually afford these new prices! I’m buying it anyways!”

    Then retailers see the insane prices people pay for stuff without blinking. Steam Decks sell out after a 40% markup. RAM & SSDs & HDDs sell out at 4x what they sold for a year ago. So the prices never go back down.

    And everyone goes full surprised-Pikachu-face when everything is now always goddamn expensive.

    Show some fucking restraint for once, people!

    Goddamn.



  • Unfortunately, like GPUs during the cryptomining era, consumers have shown their hand as to just-how-many-people will pay insane exorbitant prices. Remember when you could pay $200-300 every 2 years and get about double the GPU power? (It was only 5 years ago…) Nvidia & AMD learned that they no longer had to offer that anymore.

    RAM prices have quadrupled in a year. Yet 25% of gamers still plan to upgrade this year, and 40% in the next 2 years. Even if we make believe that the previous status-quo was “everyone upgrades every year” (which is obviously a gross overestimation), this is a huge “line-going-up” scenario for the RAM manufacturers.

    Why would they even bother lowering prices until forced to do so?





  • It’s been a year or two since I gave up on Jellyfin, so maybe it’s better now… But the Android TV client was rough, rough, rough when I tried using it.

    If you watched Live TV, the transcode buffer would just keep going and fill your entire disk over the course of a few days after you shut down the client and stopped watching.

    It was a coin toss whether you’d actually be able to stream any given movie. If you had media with more than 6 audio channels, and also needed to transcode (because you live in the U.S. and don’t have unlimited upload bandwidth)… playback would just die right around the 5-10Mbps range. I spent a weekend on the forums chasing down the exact scenarios that caused this one, someone had a Pull Request that fixed it in a matter of hours (by mimicking the transcode logicr of the official desktop client)… and the dev told them to kick rocks