Here we are - 3600 which was still under manufacture 2-3 years ago are not get patched. Shame on you AMD, if it is true.

You are viewing a single thread.
View all comments View context
2 points

I think what most people disagree with, is that the active choice from AMD to not fix a very fixable issue, is a choice they know leaves customers is a seriously bad position. This is something they choose to do to their customers, because they could just as well choose to help them.

permalink
report
parent
reply
1 point

they could just as well choose to help them.

I think that’s what I have a hard time believing. If they could “just as well” help, it is my belief that they also would. Because I don’t think they’re morons. I think they know this hurts their reputation. There has to be some obstacle, be it financial or lack of man power or… something. That is my belief.

Don’t you (all) think that sounds more likely than them just leaving their customers in the dark for no other reason than not having to do work?

permalink
report
parent
reply
1 point
*

Of course there’s a financial reason, they’ve probably done a cost/benefit analysis and decided that it’s financially better to screw over those customers than to spend money fixing it. But that’s exactly the issue!

permalink
report
parent
reply
1 point

I mean… 🤷‍♂️ The analysis is made, decision made. I probably have an affected system but… What’s the real risk for private end users? Should I really be so concerned?

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 5.1K

    Monthly active users

  • 3.6K

    Posts

  • 81K

    Comments