jgoyvaerts

What about moving the connector to the table declaration, similar to dbcontext in .net?

Something like Q.table(definition, connector), which would then allow you to just write users.filter(user => user.id.eq(42).fetch()

I've applied twice to one of your open positions but never even received a reply, how come?

He says it's hundreds of gigabytes of traffic. I don't know the prices but sounds more than a few pennies

You left out the part where the requests are coming from Cloudflare IPs.

No serious user should still be using LastPass in 2021.

On a previous project the company I joined used LastPass as their password solution, we had 2 root admins, me and a senior colleague.

One day my senior colleague tries to log in to check/change a password and is unable to log in to his account. Account recovery/password lost doesn't work either. I log in to verify if his account is blocked or disabled in anyway, and I can't even find his account. The account was completely GONE. I checked the audit logs of the account (which should include user creation, deletion, logins, etc) and there is no mention of the account ever being deleted, it's like it never existed.

We contacted their support but never got a serious reply to this behavior, so we moved over to 1Password the next day and never looked back.

Stay away from LastPass, they just lose data out of nowhere and their support sucks.

It's a combination of various factors. The games definitely play a role (PS3 has more exclusives, Xbox360 is mainly Halo and even that has been remastered on PC now).

Another factor is how the projects are maintained and managed. The maintainers of RPCS3 are more active and pull requests get feedback and merged relatively quickly.

On Xenia side, pull requests can remain open for months even though they should be merged, and this has caused multiple (potential) contributors to stop making pull requests.

Source: I'm a contributor on Xenia