> I am somewhat concerned about the volatility.

Not just volatility but also flip-flopping. Rust was explicitly a contender when they decided to go with Swift 18 months ago, and they've already done a 180 on it despite the language being more or less the same as it was.

▲

zem 5 hours ago | parent | next [-]

they tried swift, it didn't work, and they figured rust was the best remaining option. that's not "flip-flopping" (by which I assume you mean random indecisiveness that leads to them changing their mind for no reason)

	▲	lioeters 4 hours ago \| parent [-]
		Yup, this was not flip-flopping, it was willingness to be open to options, even if it means going back on a decision branch made earlier in the process. For the Ladybird project, now is the best time to be making a big decision like this, and it's commendable that the project lead was honest to recognize when an earlier attempt was not working, to be able to re-think and come to a better decision. I'm no fan of Rust, but for this project I think most of us would agree it's a better language than Swift for their purpose.

▲

qingcharles 5 hours ago | parent | prev | next [-]

They made a very pragmatic and sensible decision after reviewing Swift that it wouldn't be suitable for their purposes, so they shifted to the next best alternative. I think they reasoned it very well and made a great decision.

▲

0x457 3 hours ago | parent | prev | next [-]

I guess they bet on Swift being more than Apple's blessed way of writing UI software.

▲

fmajid 8 hours ago | parent | prev [-]

It's not that they are loving Rust, but they realized going all-in on Swift means becoming sharecroppers on massa Tim Apple's plantation.