News for hackers. Stuff that matters.
Re:Ladybird: Closing this as we are no longer pursuing Swift... by truncate on Wednesday February 18, 2026 @08:42PM (#47068869)
>> some teams are just not permitted to contribute to OSS in any way

My understanding is that by default you are not allowed to contribute to open-source even if its your own project. Exceptions are made for teams whose function is to work on those open-source project e.g. Swift/LLVM/etc...

Re:Ladybird: Closing this as we are no longer pursuing Swift... by WD-42 on Wednesday February 18, 2026 @08:49PM (#47068905)
I talked to an apple engineer at a bar years ago and he said they aren’t allowed to work on _anything_ including side projects without getting approval first. Seemed like a total wtf moment to me.
Re:Ladybird: Closing this as we are no longer pursuing Swift... by xmcp123 on Wednesday February 18, 2026 @09:24PM (#47069133)
I have never had a non wtf moment talking to an apple software engineer at a bar.

I can recall one explaining to me in the mid 20 teens that the next iPhone would be literally impossible to jailbreak in any capacity with 100% confidence.

I could not understand how someone that capable(he was truly bright) could be that certain. That is pure 90s security arrogance. The only secure computer is one powered off in a vault, and even then I am not convinced.

Multiple exploits were eventually found anyway.

We never exchanged names. That’s the only way to interact with engineers like that and talk in real terms.

Re:Ladybird: Closing this as we are no longer pursuing Swift... by 8cvor6j844qw_d6 on Wednesday February 18, 2026 @09:06PM (#47069020)
This is interesting, I knew a workplace where open source contributions are fine as long as its not on company PC and network.
Re:Ladybird: Closing this as we are no longer pursuing Swift... by iLemming on Wednesday February 18, 2026 @09:56PM (#47069331)
No, as far as I know, at Apple, this is strict - you cannot contribute to OSS, period. Not from your own equipment nor your friend's, not even during a vacation. It may cost you your job. Of course, it's not universal for every team, but on teams I know a few people - that's what I heard. Some companies just don't give a single fuck of what you want or need, or where your ideals lie.

I suspect it's not just Apple, I have "lost" so many good GitHub friends - incredible artisans and contributors, they've gotten well-payed jobs and then suddenly... not a single green dot on the wall since. That's sad. I hope they're getting paid more than enough.

Re:Ladybird: Closing this as we are no longer pursuing Swift... by zrobotics on Wednesday February 18, 2026 @09:52PM (#47069302)
Every programming job I've ever had, I've been required at certain points to make open source contributions. Granted, that was always "we have an issue with this OSS library/software we use, your task this sprint is to get that fixed".

I won't say never, but it would take an exceedingly large comp plan for me to sign paperwork forbidding me from working on hobby projects. That's pretty orwellian. I'm not allowed to work on hobby projects on company time, but that seems fair, since I also can't spend work hours doing non-programming hobbies either.