wewbull

Part of it might be that I’m often having similar arguments with the team I run about introducing dependencies.

Engineers have a tendency to want to use the perfect tool for a job at the expense of other concerns. It could be ease of maintenance, availability of the skill-set, user experience, or whatever. If there’s pushback it’s normally that they are putting their own priorities above other people’s equally valid concerns.

Often I’m telling people to step-back. Stop pushing, listen to the resistance and learn from it. Maybe I’m on a bit of a crusade when I see similar situations in open-source.

That’s where I assumed it was going.

Unlikely. You probably will injest the poison and die, and depending on if the poison also acts as a venom they may / may not.

It’s probably more accurate to say "Venoms are injected. Poisons are injested. "

That’s where they are right now.

Right, but I think what’s different on the GPU side is that the idea “nVidia make the best GPUs” has permiated through the whole market. And it’s true. Nothing touches a 4090.

A lot of buyers want to buy a 4090, can’t afford it and so move down the Nvidia product line until the reach one they can afford. They don’t consider other brands because “nVidia make the best GPUs” even if another brand might get them more bang for their buck now they are shopping lower in the product stack.

A halo product isn’t there to sell itself. It’s there to sell the rest of the range.

Maybe we’re agreeing. I’m not sure.

I think for python tooling the choice is Python Vs Rust. C isn’t in the mix either.

people like and want to program in rust

I think there’s a survivor bias going on here. Those that have tried rust and stuck with it, they also like it. Far more people in the python community haven’t tried it, or have and not stuck with it. I like and want to program Haskell. I’m not going to write python tools in it because the community won’t appreciate it.

Tools should be maintained by those that use them. Python doesn’t want to rely on the portion of the venn diagram that are rust and python users because that pool of people is much smaller.

Polaris remains one of the most popular AMD dGPUs to this day.

That’s not a high bar. AMD haven’t really had a big hit GPU since they shifted to GCN. RDNA was looking to be revival, but hasn’t really been competitive enough to shift the consumer mindset.

Those languages bring different things though:

• Python is the language the tool is for

• C is the implementation language of Python and is always going to be there.

• Cython is a very similar language to Python and designed to be very familiar to Python writers.

• Fortran is the language that BLAS and similar libraries were historically implemented in since the 70s. Nobody in the python community has to write Fortran today. Those libraries are wrapped.

• Rust is none of the above. Bringing it into the mix adds a new barrier.

Is a Tuk-Tuk still a Tuk-Tuk when it doesn’t go Tuk-Tuk and just goes vrrshh?

I don’t think it’s a dream of “everything in python”, but “python tools for python development”. It means users of the language can contribute to the tooling.

The only way this works is you make your products obviously better in terms of price/performance in the segments you compete in. You’ve sacrificed the effect of a halo tier product on mindshare to your competitor, so your value proposition has to completely undermine nVidia.

However, nVidia has a very big war chests. They could give the 50xx cards away for free and not really care, as long as it got rid of the opposition.

I personally think this is a suicidal strategy.