It seems likely biased as well unfortunately if they let teams decide on their own what to use. I would wager that teams who on their own switched to Rust are probably teams that were already productive.
I disagree that it's so simple, 10 is different because for a long time it was unclear 11 was ever going to happen, the biyearly releases were the new versions. For most of the other Windows versions they didn't stop receiving security update until well after the next version or two were out. 11 will have only been out for 4 years when support for 10 theoretically stops.
At least I attempted to looked it up, rather than everyone else who assumed it just can't happen at all while also knowing nothing about it.
No, what I'm saying is that a quick Google suggests you can get jail time for this in Colombia even if Apple is the one suing. Obviously I'm not an expert, but my point is that Apple's threat of possible jail time is not completely unfounded, you can't assume it just works like the US legal system.
I think you might be making too many assumptions about the Colombian legal system.
The irony is that it very well could have been a disadvantage for her to get picked. The incumbent advantage isn't really a thing for people appointed to the seat, and she'd be stuck doing Senate things for the next year instead of campaigning.
Keep in mind it's not an all or nothing thing, they'll assign percentages of fault. It's also important that they name name basically anybody involved because the others will try to blame Google to shift fault off of themselves.
Effectively you want to name everybody possible so that they all fight it out.
It's not quite what you're getting at, but in Bubble Bobble Revolution you can't pass level 30 because the boss doesn't spawn. It's a soft lock but there's nothing you can do to avoid it, and the game is on the DS so there's no updates to fix it :D
The only makes sense if they actually wanted to keep him that long after he tried to quit. We don't know for sure but potentially they just wanted to keep him around long enough to find a replacement (since he just told them he's quitting).
I think you're missing a detail here, which is that before streaming was a thing writers would make significant amounts of their money by getting a show syndicated on a network, that was the whole deal. Streaming is being treated differently, effectively resulting in then receiving a very large pay cut because even if they make a successful show the payout doesn't come.
And it's true they could structure things so that they don't receive a secondary payout, but their base salary was negotiated with that later payout in mind. You and I don't receive secondary payouts for our work, but our salary is also adjusted to recognize that.
Much of what she was brought on to do (negotiating with advertisers I guess) isn't really public facing, so from that respect it's not that surprising that she appears to be doing nothing. I also think she's not taking the L yet, if things get even worse Musk may blame her as an excuse to walk things back ("I was following her advice" or whatever).
Maybe, but there's a market out there for CEOs who are willing to take the blame for some unpopular decisions and then walk away. There's also something to be said that "-50%" might actually be an improvement over where it was before she was hired, and the bad decisions weren't hers.
I feel like you ignored their chief issue, which is that if your original server (IE. lemmy.world) goes down then nothing works for you. In that situation you have to switch to a new server to be able to view anything, and likely need to create a new account on that server. There's some other catches to this as well that makes it more problematic than just that.
They were definitely told the "it doesn't matter what server you choose" line when they looked at lemmy, but in reality that's not entirely true if a server isn't that stable.
Generally speaking the use case is writing tests. If your tests just call all the dependencies and new directly then it's harder to write tests for your specific component while avoiding setting up a whole bunch of stuff (to make all those other classes work). By requiring all the dependencies to be provided to the class, you can swap them out at test time for something else that's easier to work with.
That said, IMO it's a symptom of problems in language design. Using DI is only necessary because languages like C# don't make it easy to mock out new or classes used directly, so we resort to wrapping everything in interfaces and factories to avoid those features and replace them with ones that are easier to mock. If the language was designed such that those features were easy to replace during testing then DI probably wouldn't be a thing.
My point is that the data on here is purposely shared with every other federated instance, there's no semblance of privacy and your data is shared with hundreds or likely thousands of admins by the time it's done (more and more as the network grows). There's no reason to trust that every admin will keep that information private, some people are already talking about putting up services to expose all the hidden information (in the name of "transparency"). It's simply trivial for Meta or anybody else to get copies of the data because there's no real protection from it unless you're making your instance an island (and that's an island from everybody, not just one specifically known to be Meta).
Ehh, you might as well waste as much of the admins time as possible.
Fundimentally none of the data on here is private, it's not designed to be private.
I haven't used Zig myself but I think it could have its place. IMO Rust has moved too far away from C to be something many existing users will move to (and using both in the same project is messy), but Zig seems to integrate well enough that it might.