deadcream

Most of those servers are dead though (including some nitter instances). You will need to manually disable those that don’t work and it’s pain in the ass.

Are they still trash in terms of performance (I know that all smart tvs have weak hardware but my experience with Sony was even worse than average)?

Sounds like they didn’t test what happens with their apps when token is reset on server 🤔 should be reported to the apps devs. Thankfully with lemmy this is easier to fix than with proprietary services because you can self-host it and check various edge cases.

How much data is pushed through ActivityPub? Unless it is at least tens of thousands of requests/events (i’m not familiar with how it works) per second I doubt that the choice of language would have big impact. PHP is made specifically for web backends after all.

I played it by myself and it was fine up until the last fight in Lucien’s tomb (or whatever it’s called) where you need to sit through 50 enemy turns before you are killed after barely making a few steps. I just enabled cheats and finished the game, all the good parts of it were before that anyway.

Now it looks like it’s hiding something.

Yeah I hated how they shrunk Lan’s shoulders and made him look soft.

I don’t use it myself, but I don’t have a strong opinion on that. My beef if with deduced return types, especially with templates. It is typical in modern C++ code to see such function:

template<typename ~whatever~>
auto foo(~some arguments which types are deduced from nested templated conditional using declarations that you don't understand~) {
    return ~call to other template function that's 10 levels deep and is also conditional on properties of template parameters with some ifdefs for fun~;
}

That makes it absolutely impossible to figure out what types function takes as parameters and what type it returns until you hit 10-page compiler error that will explain everything (which is also will force you to read through implementation details of this function to figure out how to fix it). And often IDEs can’t help you either.

That’s how they do it. They send their “proposal” and immediately implement it in Chrome (with work on that being started long before “proposal” is made public obviously). Then they start using it on their own websites (with compatibility for now) and start propaganda campaign to push webdevs to use it too (which they do of course). Then they start complaining that other browsers’ developers are slow to implement this new “standard” (at this stage they won’t call it a “proposal” anymore) and are “stifling development of the web” or being actively malicious because they are jealous of Chrome or something. Then compatibility mode on their websites is first subtly broken so that users once again will witness how Chrome is superior browser and then removed outright. Boom, we have a new web standard!

You mean AVIF?