Oh yeah, the “ultimate failure of Rust”, and tell me how industrially successful Pony has been compared to Rust?

(Don't get me wrong, I liked the idea behind Pony for backend code, it's much saner than Go for the same target space. But it failed to capture that market, because Go was already there. And it was never a competitor to Rust because this model is only viable for web back end tasks, not for general computing).

▲

rurban 4 days ago | parent [-]

It isn't it a shame that the industry always falls for the liars?

The pony model was also better for compute tasks, not just IO. Because it provided safe concurrency, 10x faster than go.

▲

littlestymaar 4 days ago | parent [-]

No, the pony model isn't better for compute tasks…

Think for instance about how you'd do efficient matrix multiplication of two matrices with a million row and column, in Pony, versus how it works in languages with shared memory. You'd spend a gigantic amount of time copying data for no good reason…

▲

rurban 4 days ago | parent [-]

Of course pony can do shared memory. How about clevering up?

	▲	littlestymaar 2 days ago \| parent [-]
		Ditching the pony model to defend it is a very strange version of the mote and bailey fallacy.