Eh, he's given an interview where he talks about the Swift decision. He and several maintainers tried building some features in Swift, Rust, and C++, spending about two weeks on each one IIRC. And all the maintainers liked the experience of Swift better. That might have ended up wrong, but it's a pretty reasonable way to make a decision.

▲

zamalek 6 hours ago | parent [-]

Two weeks with Rust and you're still fighting with the compiler. I think the LLM pulled a lot of weight selling the language, it can help smooth over the tricky bits.

▲

written-beyond 3 hours ago | parent [-]

idk man it's rare to fight the compiler once you've used Rust for long enough unless you're doing something that's the slightest bit complex with async.

You get to good at schmoozing the compiler you start to create actual logical bugs faster.

	▲	zamalek 2 hours ago \| parent \| next [-]
		That's why I said "two weeks."
	▲	jacquesm 2 hours ago \| parent \| prev [-]
		That goes for almost every language. I recall my first couple of weeks with various compiled language and they all had their 'wtf?' moments when a tiny mistake in the input generated reams of output. But once you get past that point you simply don't make those mistakes anymore. Try missing a '.' in a COBOL program and see what happens. Make sure there is enough paper in the box under LPT1...