Zangoose

Have you had issues setting hotkeys in KDE? I'm using NixOS on my laptop and for some reason the shortcuts I add all reset on logouts/shutdowns

Hey look it worked!

Chat is he being serious?

Edit: Chat, look at his comment history, he was being serious

Suyu is technically still being developed but whether or not anything comes out of that is a completely different story. The few devs left are unfamiliar with the code (all the yuzu contributers left out of legal fear) and have super ambitious goals (they want to do a rewrite because the original code was allegedly based off of a leaked Nintendo SDK) so it's unlikely it's going to get anywhere.

I'm hoping Ryujinx forks that pop up after this have more success. I am glad that Citra survived the Yuzu crossfire though, Lime3DS seems to be doing well.

There are a few libraries we're using that stopped being developed after Angular ~9-10 and one we use extensively with breaking changes between 10-12. Updating to 8 wasn't too bad but for some reason Angular's update tool didn't actually do anything so I had to update the package.json manually and fix stuff by hand (luckily the only change was fixed with a bulk find/replace)

To me at least angular makes a bit more sense than React's way of doing things does. React tries to be functional with its components and yet it seems like they end up basically trying to mimic classes with useState and useEffect. To me Angular's class-based approach makes a bit more sense (though I am primarily interested in backend development more than frontend so that could be why)

It does kind of fall into a lot of the traps of Object-Oriented programming though so I can see why a lot of people don't like it

Don't come at me like that 😭

You know neovim can use the exact same LSPs (Language Server Protocol) for intellisense as VS Code right? There's intellisense, git integration, code-aware navigation, etc. Neovim can be everything VS code is (they're both just text editors with plugins), except Neovim can be configured down to each navigation key so it's possible to be way more efficient in Neovim. It's also faster and more memory ~~edficient~~ efficient because it isn't a text editor built on top of a whole browser engine like VS Code is.

I use a Neovim setup at home (I haven't figured out how to use debugger plugins with Neovim and the backend I work on is big enough that print debugging endpoints would drive me insane) and I can assure you I have never given variable names one letter unless I'm dealing with coordinates (x, y, z) or loops (i, j) and usually in the latter scenario I'll rename the variable to something that makes more sense. Also, we don't do it to seem hardcore, it's because there are actual developer efficiency benefits to it like the ones I listed above.

By your own logic you "can't be bothered" to learn how to edit a single config file on a text editor that has existed in some form for almost 50 years (vi). Stop making strawman arguments.

I was trying to look more into game dev crunch at Nintendo and the most recent articles I could find were about Mario 64, Ocarina of Time, Majora's Mask (all for the Nintendo 64) and Metroid Prime (for the GameCube). From what I can tell all of their recent games have been delayed instead of forcing crunch.

That being said the difference in work culture means they probably still have longer hours but they aren't giving their developers actual PTSD like EA and Activision. It is really sad that the bar for AAA game devs is not having devs hospitalized from overworking. Hopefully more game dev and software dev companies can meaningfully unionize to combat that.

My bad, that's on me, it looks like the C++ libraries I found use either templates or boost's reflection. There might be a way to do it with macros/metaprogramming but I'm not good enough at C/C++ to know.

I'm learning rust and C at the same time and was mixing up rust's features with C's. Rust's answer to reflection is largely compile-time macros/attributes and I mistakenly assumed C's attributes worked similarly since they have the same name.

See my other comment for more detials but it kind of destroys the type safety of the language. In Java for example, it lets you modify private/protected fields and call private/protected methods.

It's also slower than accessing a field normally since you need to do a string lookup (but slightly faster than a hashmap/dictionary) so if you use it over a large enough list it'll cause slowdowns.

Most use cases for it in Java/C# revolve around testing, serialization, and dynamic filtering/sorting. And most of those cases can be handled more safely using macros/attributes (EDIT: and templates as well, though those are also pretty painful to deal with) because that gets handled at compile-time in C/C++.

It's pretty cool when you use it right but it's also really easy to shoot yourself in the foot with, even by C++ standards. For example, in other languages (I'm coming from Java/C# which both have it) it lets you access private/protected fields and methods when you normally wouldn't be able to.

There's also a noticeable performance penalty over large lists because you're searching for the field with a string instead of directly accessing it.

For the times it is necessary (usually serialization-adjacent or dynamic filtering/sorting in a table) to use reflection, it's faster at runtime than converting an object to a dictionary/hashmap. However, 99% of time it's a bad call.