Seems like rust is this year's new hot language.
Apple is looking for engineers to convert its code from C to Rust
11–20 of 240 posts
Re: Apple is looking for engineers to convert its code from C to Rust
#12D now has an Ownership/Borrowing system implemented (though it is in its early stages). It will work with existing code, including DasBetterC code. You're able to incrementally adapt a program to O/B rather than rewrite it.
Was this a response to something else in this thread that you accidentally top-posted?
It's cool, technically, but maybe a little off-topic.
Re: Apple is looking for engineers to convert its code from C to Rust
#13Earlier quoted context omitted.
I think big companies see a lot of opportunity in locations outside of Silicon Valley. If you don't care about the weather in the Bay Area, which is quite pleasant, or the other industries around you (be it for business or for pleasure), then you can get an easier commute and a better house for the same salary, which is appealing to some people. (You can also pay people less, which seems to be a strategy used by comp…
But then it's weird to specify a location. Camrose is a town of 18,000 people – why not make it explicitly remote?
Yeah that's a really good point... Is this perhaps one of those hyper specific job postings so that a company can skirt some sort of regulation about hiring immigrants by saying they did a search? but why Apple? And why Camrose...
Re: Apple is looking for engineers to convert its code from C to Rust
#14> handle the encryption of every packet passing between servers within and across vast data centres This sounds like it’s doing packet processing in software, which doesn’t seem scalable, especially for the traffic volume I would assume Apple handles. Anyone have a clue what kind of traffic volume and bandwidth we’re looking at here? Granted, I might be overestimating the requirements given the industry I work in (se…
> This sounds like it’s doing packet processing in software
From the article:
> Based on a custom implementation of IPsec
Seems pretty clear.
Re: Apple is looking for engineers to convert its code from C to Rust
#15doesn't Apple prevent engineers from having related engineering hobbies when they sign the contract ?
Re: Apple is looking for engineers to convert its code from C to Rust
#16doesn't Apple prevent engineers from having related engineering hobbies when they sign the contract ?
Usually.
Re: Apple is looking for engineers to convert its code from C to Rust
#17> handle the encryption of every packet passing between servers within and across vast data centres This sounds like it’s doing packet processing in software, which doesn’t seem scalable, especially for the traffic volume I would assume Apple handles. Anyone have a clue what kind of traffic volume and bandwidth we’re looking at here? Granted, I might be overestimating the requirements given the industry I work in (se…
None of the big clouds use hardware network encryption. All of the resources in your network are at the leaves, so you might as well use their CPUs to do it. I think Google published that crypto and compression in their internal RPC stack cost them less than 1% of their global CPU resources.
Re: Apple is looking for engineers to convert its code from C to Rust
#18Why wouldn't they use Swift? Seems odd.
Re: Apple is looking for engineers to convert its code from C to Rust
#19Interesting, this is for encrypting server-server traffic. My question: how did Apple end up doing this work in Camrose, Alberta?
I used to go there as a kid. It was one small town, and I don't suppose it has boomed since.
Re: Apple is looking for engineers to convert its code from C to Rust
#20D now has an Ownership/Borrowing system implemented (though it is in its early stages). It will work with existing code, including DasBetterC code. You're able to incrementally adapt a program to O/B rather than rewrite it.
This is a 'mindshare' game. D had its chance, now Rust has its chance. Would have been cool though if D had caught on more back in the day. Re-invention seems to be impossible to avoid in the software world.