News for hackers. Stuff that matters.
Re:How Swift Achieved Dynamic Linking Where Rust Couldn't by sandGorgon on Saturday November 09, 2019 @04:30AM (#21490526)
The last part of the line reads (rather politically incorrectly) that Apple has more talent available to solve this problem.
Re:How Swift Achieved Dynamic Linking Where Rust Couldn't by zozbot234 on Saturday November 09, 2019 @05:43AM (#21490735)
Or they were just willing to accept a significant increase in language complexity, to deal with things that Rust just punts on by basically expecting you to stick to #[repr(C)] at your preferred dylib boundary. (Though, potentially, that #[repr(C)] could become e.g. #[repr(SomeArbitraryStableABI)], and there have been proposals to this effect.) And they did this precisely because of that perception that Swift "wouldn't be usable" otherwise.
Re:How Swift Achieved Dynamic Linking Where Rust Couldn't by atq2119 on Saturday November 09, 2019 @07:31AM (#21491130)
Resources != Talent, and the line talked about resources, not talent.

It's pretty obvious that Apple can throw more money at the problem than Mozilla can, if they choose to do so. That means they can buy more developers to work the problem, which is bound to be helpful whether those developers are particularly talented or not.

There's really nothing politically incorrect about that.

Re:How Swift Achieved Dynamic Linking Where Rust Couldn't by littlestymaar on Saturday November 09, 2019 @05:53AM (#21490763)
Given that the author is a Mozilla employee (working on Rust) and former Apple one (on Swift), I'd be surprised if your interpretation was correct.
Re:How Swift Achieved Dynamic Linking Where Rust Couldn't by Gankro on Saturday November 09, 2019 @09:14AM (#21491646)
Yeah motivation is the bigger factor (why would Mozilla care about the system APIs of an OS, of all things?) but also it doesn't hurt that Apple is one of the richest companies in the world (depending on the day).
Re:How Swift Achieved Dynamic Linking Where Rust Couldn't by sandGorgon on Saturday November 09, 2019 @06:07AM (#21490813)
I do admit that English is not my first language...but I am struggling to interpret "Apple had way more resources to throw at this very hard problem." any other way.
Re:How Swift Achieved Dynamic Linking Where Rust Couldn't by littlestymaar on Saturday November 09, 2019 @06:28AM (#21490886)
It depends what you mean by “talent”, if you use it in the HR way where a “talent” is an employee, then yes talent=resources, but then I don't understand how this is “politically incorrect”.

What I understand when you say this:

> the line reads (rather politically incorrectly) that Apple has more talent available

Is Apple employees are more “talented” than Mozilla's. That's politically incorrect, but I'm pretty sure that's not what's meant here.

Re:How Swift Achieved Dynamic Linking Where Rust Couldn't by sandGorgon on Saturday November 09, 2019 @06:40AM (#21490934)
maybe they were equal...but Apple had more number of "talent" available.

Which then begs the real question - Swift is what Rust would be if Mozilla had more money/resources ?

Re:How Swift Achieved Dynamic Linking Where Rust Couldn't by rjvs on Saturday November 09, 2019 @06:23AM (#21490868)
Cash is a resource.
Re:How Swift Achieved Dynamic Linking Where Rust Couldn't by bsaul on Saturday November 09, 2019 @06:16AM (#21490846)
Or maybe it's just the hard truth (which wouldn't be surprising considering the valuation of Apple and Mozilla respectively)
Re:How Swift Achieved Dynamic Linking Where Rust Couldn't by tinco on Saturday November 09, 2019 @04:48AM (#21490584)
How would it not?
Re:How Swift Achieved Dynamic Linking Where Rust Couldn't by saagarjha on Saturday November 09, 2019 @04:51AM (#21490598)
I have no idea of the amount of resources spent, so I'm not sure I can comment on that.