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.

Ehh, you might as well waste as much of the admins time as possible.

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

Does Twitter Blue show ads? I guess I assumed if you're paying you don't have to see those, but that would make too much sense 🤦‍♂️

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.

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.

He still owns the company so it doesn't matter who the CEO is, he is their boss. If he wants to continue making big business decisions then he still can, and if the CEO doesn't agree he can either fire them or just go over their head.

Fundimentally none of the data on here is private, it's not designed to be private.

Are we sure on that? I've seen conflicting reports on whether they actually started paying or not (Ex. Engadget article from a week ago says they are). It's not public information so it's hard to verify.

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 totally agree with you that a typical CEO would not put up with this at all, but then I don't think this is a very typical situation :D I would assume she knew what she was getting into. He named himself CTO so it's not like he's no longer involved in the company, and the CEO can't really 'overrule' him on any product decisions or anything else since he's technically also her boss.

Now, if he's smart he will hopefully at least take her opinions/guidance into consideration, but 🤷

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.

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.

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.

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.

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.

Starting with Gameboy might be a bit daunting but if you're reasonably comfortable with C then I don't think it's too bad. If you're not too familiar with the hardware side of it then that might be a challenge, but the advantage with the Gameboy is that there's tons of documentation and tutorials out there which can probably help you work though the details. Really the big thing is to just be ready to do lots of reading XD You need to get a base-level of understanding of the system before you start coding. git says it took me around a year to get it functional and playing most ROMs, but that was with some big breaks in-between.

Also, that's a very good question. For performance, it was never an issue. I started it with a focus on keeping the code clean vs. worry about performance and it turned out fine, I've run it on a cheap 1.6GHz machine and it didn't even reach 25% CPU usage, so IMO I wouldn't worry about it. This also doesn't vary that much ROM to ROM.

For the ROMs I tested, for the most part every ROM tended to uncover something new, but the Gameboy has a pretty nice progression of "easy" to "hard" ROMs if you just sort by the MBC type, and also the BIOS is a pretty good test of basic functionality. Additionally there are a few different test suite ROMs out there that are fantastic, they'll run through every instruction or piece of functionality and check for the correct results, they saved me tons of time.

Lol the funny thing is that this isn't even close to my longest project :P I have one with a first commit close to 10 years ago (and I of course started it a while before the first commit). It's my favorite just for how fun the result is. IMO the best projects tend to be ones you actually like to use when you're done.

That said I also wouldn't put too much stock in that 1 year, I think I worked on it a lot for about a month and then moved onto other things after having trouble with it. I came back about a year later and managed to more or less finish it. It's definitely a long time to devote to a project, but if you stayed focused on it you could do it in a couple months I think.