Dolphin, to me, is the model open-source project: constant improvements, total developer transparency, detailed documentation, and a lively community. It is the most reliable and most professional emulator out there, for any platform.
Also, that hybrid ubershader thing was pretty clever.
Seems to me that classes generally replace structs in such languages. I know they're not the same thing, but classes have the features of structs (and much more) at the cost of performance.
A lot of people (my whole company, for sure) are using namedtuples essentially just as immutable structs. This is a case where classes aren't sufficing. To be fair, it's at least a little bit the functional-programming, immutability bandwagon, but either way it's helping maintain large python apps with many devs.
Python36 gradual typing also helps here though, and am definitely interested to see if that changes the game a bit
> classes have the features of structs (and much more) at the cost of performance.
Not true; C++ classes have zero performance overhead over C/C++ structs (because they're just another word for the same thing).
Of course Python classes have a lot of costly features that C++ classes don't have, but the notion of a "class" (with methods, constructors etc) is not one of them.
And also makes them look more complicated with more syntax. C++ has all those features that I will never know without adding performance. But people don't use Python for performance but ease of use.
In C++ ease of use is given up for the sake of performance. In python it is the other way.
vtable is always "hidden". It's only there when there is at least one virtual member defined. Sole difference between class and struct in C++ is default visibility.
class A {
int a; // private
}
struct A {
int a; // public
}
Even if the article is outdated with respect to LIGO, it's mostly still relevant. Quantum gravity is a major unsolved problem in physics, and one that we have no idea how to solve.
Seems to me this can be handled the way the open-source community always handles such drama: fork the repo a bunch of times. I'll probably start keeping local copies of filter lists as well.
I have no major gripe with NPM, but it does seem like the programmers who favor it don't even think about what they're calling. The way I see it, the more code you write yourself, the more code you understand easily.
