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.
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.
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.
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.
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.
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 🤷
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.
I few years back I wrote a Gameboy emulator in C, it was definitely one of the most fun projects I’ve done. The Gameboy is simple enough that you can make an emulator for it without crazy amounts is effort, and the result is very satisfying. A lot of the simpler systems people recommend writing emulators for aren’t that interesting IMO simply because after you write it the games you can run aren’t that great.
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.
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 🤦♂️
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.