HIP was such a self-own and clear demonstration of AMD software capabilities... well, the lack of software capabilities. HIP was hard-coded for one GPU architecture. CUDA did it right, it has a intermediate virtual assembly PTX and driver compiles it to whatever actual instruction set card actually uses.
Imagine a meeting where they signed off on that. So each developer will have to provide a different binary for each of our architectures? Yep. And once we release the new architecture, developer will have to recompile his program for the new architecture? Yep. Sounds good to me.
Yes, that was in part why they've had such a terrible history with GPU support.
They lost me as a customer when they rushed dropping support for the Radeon VII because of the need to ship binaries for every ISA, and didn't deliver proper 5700XT support until it was outdated.
Exactly. You want others to change to fulfill your needs. Their priorities and needs are different. In this case, it was evaluated and found not to be useful (cost > benefits).
That was basically what Ford vs Dodge was about. Ford lost and had to change direction. If C-suite does not operate in that direction, they can sue and will win. There is no point in going in different direction, courts already quite clearly said you will lose.
> My ambition is to employ still more men, to spread the benefits of this industrial system to the greatest possible number, to help them build up their lives and their homes. To do this we are putting the greatest share of our profits back in the business.
> A business corporation is organized and carried on primarily for the profit of the stockholders. The powers of the directors are to be employed for that end. The discretion of directors is to be exercised in the choice of men to attain that end and does not extend to a change in the end itself, to the reduction of profits or to the nondistribution of profits among stockholders in order to devote them to other purposes.
>If C-suite does not operate in that direction, they can sue and will win. There is no point in going in different direction, courts already quite clearly said you will lose.
If this is true, it should be easy to point to some examples from the last hundred years. Because that Wikipedia article you linked makes it very clear that the conclusion you're drawing is highly debated. The disagreement is important enough to be mentioned in the second sentence in that article. The first source on the page is the actual case and the next two are both criticisms of the interpretation that you seem to very confident in.
It faces criticism, but still held true. "sacrificing profit for moral reasons" is not acting in best interest of shareholders. That doesn't mean maximizing value at all times btw, e.g. assessing potential reputational damage and sacrificing some profit by not doing something can be acting in best interest of shareholders (or not, depending on circumstances).
Azure is not the best, but it mostly works. GitHub gets only 98% reliability for git operation component, reading and committing. This is the most basic component. The fact they are not on this 24/7 and it isn't fixed is the result of a culture (=what is prioritized, what quality is accepted).
Compare costs, monetary risk and TTM to renewables with battery backup. Nuclear is dead as a doornail.
Look at the nuclear buildup. Vogtle in US 10 years. Hinckley Point C is estimated to be 13 years. Flamanville 3 took 17 years. All these years you put money in and get nothing out. It's a disaster for balance sheet. Instead, you can build renewables plus batteries and have it connected within a year, generating revenue.
Signal to noise ratio is getting *lower (EDIT: was higher) than ever. I don't see a way out of this other than "human certified" digitally signed authorship (e.g. by using eIDAS in EU). There could be a proxy to at least retain pseudo-anonymity, but trackable to a human. Tragedy of commons strikes again.
"Tragedy of commons" is a false concept that obscures greed and selfishness and often lawlessness. Even its originator (Hardin) accepts that it does not describe actual history.
The use of the word Tragedy in the name I think makes it easier for people to excuse themselves when they monopolize the commons. “Oh it’s a tragedy humans are just selfish we can’t avoid it.” The tragedy is that people are comfortable excusing others selfish, greedy behavior by saying it’s innate.
There’s a lot of debate under your linked comment.
My understanding is that people tend to cooperate in smaller numbers or when reputation is persistent (the larger the group, the more reliable reputation has to be), otherwise the (uncommon) low-trust actors ruin everything.
Most humans are altruistic and trusting by default, but a large enough group will have a few sociopaths and misunderstood interactions; which creates distrust across the entire group, because people hate being taken advantage of.
> Most humans are altruistic and trusting by default ...
... towards an in-group, yes. Not towards out-groups, as far as I can tell.
Though for some reason this tends not to apply to solo travellers in many, many parts of the world.
Lots of debate, yes, but very little about the basic fact that Hardin's formulation of "the tragedy of the commons" doesn't describe actual historical events in pretty any well documented case.
Although, there are other large-scale examples where tragedy of the commons has been (practically) avoided: ozone depletion and Polio eradication. Wikipedia (https://en.wikipedia.org/wiki/Tragedy_of_the_commons#Non-gov...) also mentions Elinor Ostrom, but her examples involve "smaller numbers".
It could be interesting to have a search engine that only shows results that have human attestation via digital passports. Of course I'd prefer that to work without necessarily revealing the identity of the poster, similarly to how anonymous "sign-up tokens" for accounts would work, to prevent sybil attacks.
Marginalia doesn't actually use whitelists though, but it does give preference to results from known human websites, as well as sites that are linking to and being linked from that set.
Open source is not open contribution. There are many examples of open source, but closed contribution, e.g. SQLite.
What you are listing is a business strategy of a company (free labor and advertising). Desires of a company are very different from an unpaid volunteer.
In projects that leave PRs unanswered, the maintainer is already unpaid labor, but contributor want him to work on the contribution. That might not align with what maintainer wants.
Edit: Personally, I find reviewing least pleasant part of dev work. Thanks to LLMs, that now also significantly more of my paid work. My desire to do code reviews in my free time is massively lower. I would rather do it myself.
Imagine a meeting where they signed off on that. So each developer will have to provide a different binary for each of our architectures? Yep. And once we release the new architecture, developer will have to recompile his program for the new architecture? Yep. Sounds good to me.
reply