Earlier quoted context omitted.
It has an unfortunate name though, maybe a short shelf life. Rust++ doesn’t seem inviting either.
Rust does not have a ++ operator, so that name would make no sense.
Not yet.
Swift at Apple: Migrating the TrueType hinting interpreter
121–130 of 139 posts
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#122If you want to help improve the security of OS software through the magic of memory safe languages, the team that did this work is hiring: https://jobs.apple.com/en-us/search?search=Spear&sort=releva... Knowledge of Swift not required. If you know your way around OS software, can reason about the security of the code you write, and are excited about writing exhaustively tested software, we’d love to talk to you. We’r…
How do I apply? Historically jobs.apple.com is a black hole unless you know people.
Apple (like most large tech companies) is indeed a resumé black hole, and knowing people helps, so definitely network if possible. However, applying to the right position, with a good resumé that highlights experience/skills/projects/open source contributions/education/etc. that are directly related to the position, also matters. I am aware of several people who simply applied online and got interviews.
I may be wrong about this, but I don't think Apple bans you from applying to multiple positions within the same year the way some companies do.
There also seems to be a decent pipeline for new graduates (though I think highlighting relevant academic, research, and open source projects can still help.) Internships can also be a path if you are currently in school.
I don't know if Apple recruits on linkedin, but that might also be an option.
Of course connecting right here on HN seems like a great idea as well.
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#123Earlier quoted context omitted.
How do I apply? Historically jobs.apple.com is a black hole unless you know people.
Apple (like most large tech companies) is indeed a resumé black hole, and knowing people helps, so definitely network if possible. However, applying to the right position, with a good resumé that highlights experience/skills/projects/open source contributions/education/etc. that are directly related to the position, also matters. I am aware of several people who simply applied online and got interviews. I may be wron…
I was hoping to get some sort of a more direct contact from GP since he advertised the position. Not sure why would you mention it on HN otherwise.
> However, applying to the right position, with a good resumé that highlights experience/skills/projects/open source contributions/education/etc. that are directly related to the position, also matters.
I assume that Apple is even more competitive, than my current place. But even here it is not realistic: I heard we’re getting 500+ applications/position/day and _nobody_ looks at them unless there’s a lead/recommendation.
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#124Earlier quoted context omitted.
Oh my sweet summer child. Even software being written TODAY isn’t being tested in HiDPI. Win32 still makes it difficult.
I’m not your child, and that’s false, it’s literally one key to change in the settings. That allows you to select the exact scaling factor, not macos’s “more text”/“less text”.
Have you ever tried to write HiDPI-aware Win32 code? I suggest enabling HiDPI in Control Panel sometimes and marveling at how many Win32 apps just don’t notice and draw as postage stamps.
Mac OS X 10.4 tried the same thing (Quartz2D scaling) and it was so damn difficult that they threw it out and went for simple 1x/2x/3x auto-scaling. Even 3x was a challenge because of pixel alignment.
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#125Earlier quoted context omitted.
Rust does not have a ++ operator, so that name would make no sense.
Not yet.
I can assure you that Rust will never have a ++ operator. Not only is it semantically bizarre, it's entirely unnecessary in a language where iteration is overwhelmingly performed via iterators rather than via manually incrementing array indices.
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#126Welcome to the club of doing high performance text in a memory safe language!
> high performance text Just strings or rendering strings? If the latter, who are the other members of the club?
Yeah, probably should have made a more substantive comment. I'm mostly thinking of the trio of Skrifa, Harfrust, and Parley, but there is other open source Rust work that qualifies as well.
There's also, very relevantly, the DWriteCore work from Microsoft. My understanding is that there's been some talk of open sourcing that, but it's still proprietary.
There are other things that count as high performance text in memory safe languages, for example implementations in Go, but in general those are not a good candidate to replace C and C++ in environments like operating systems and browsers.
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#127Earlier quoted context omitted.
My last 1080p monitor was around 20 years ago. I have trouble comprehending people still use them regularly.
People also use usable mice instead of touchpads, and they put the "ctrl" key where Apple thinks a useless "fn" should be. All kinds of things happen outside Apple world. To me, it's more about what I'm used to. I have a perfectly fine several years-old monitor, so why should I throw it away?
I'm a PC user with a work MacBook. I was talking about my PC.
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#128If you want to help improve the security of OS software through the magic of memory safe languages, the team that did this work is hiring: https://jobs.apple.com/en-us/search?search=Spear&sort=releva... Knowledge of Swift not required. If you know your way around OS software, can reason about the security of the code you write, and are excited about writing exhaustively tested software, we’d love to talk to you. We’r…
Do you folks also hire outside the US?
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#129Earlier quoted context omitted.
Not yet.
I can assure you that Rust will never have a ++ operator. Not only is it semantically bizarre, it's entirely unnecessary in a language where iteration is overwhelmingly performed via iterators rather than via manually incrementing array indices.
Is that a bullet point in the Rust manifesto? :) In any case, ++ has taken another meaning outside of operator loading and such some.
The “Rust” branding, to this rando, implies corrosion, oxidation, decay, regardless of the true origin of the name. Swift is “quick”, Java is “caffeine”, Rust is something I need kerosene for.
Re: Swift at Apple: Migrating the TrueType hinting interpreter
#130Earlier quoted context omitted.
I can assure you that Rust will never have a ++ operator. Not only is it semantically bizarre, it's entirely unnecessary in a language where iteration is overwhelmingly performed via iterators rather than via manually incrementing array indices.
Is that a bullet point in the Rust manifesto? :) In any case, ++ has taken another meaning outside of operator loading and such some. The “Rust” branding, to this rando, implies corrosion, oxidation, decay, regardless of the true origin of the name. Swift is “quick”, Java is “caffeine”, Rust is something I need kerosene for.
Yes, it is pretty universally agreed upon that a ++ operator in Rust doesn’t make any sense. += 1 is barely longer, not special cased, and does not make users memorize odd precedence rules.