Yeah, it looks pretty bad from that list. It may not be quite as bad in practice - some of them may have their name attached because, for instance, they co-own a production company where only person is involved but all three co-owners get their names on the credits. And some of them may be involved on the technical side, some for the story side, some just for financing, etc.
But even so, that looks like far too many names to have any kind of coherent vision.
In EA's defence, I think that moment was a turning point for them. That's not to say their games since then have been perfect - they certainly haven't, and most of them don't appeal to me anyway - but I think most of the flaws with their games since then have been developer-related issues rather than anything to do with publisher meddling.
I use the "boost" feature to save posts for now :)
Funnily enough, I don't care too much about apps because kbin's mobile web version (and, by extension, its PWA) is pretty nice as is. But I agree that most mobile websites have terrible UX.
I think the majority of "Marvel burnout", for me at least, is on Marvel's side. I still want to enjoy Marvel's releases, it's just that their quality has dropped so much that I can't do that right now. And it's something Marvel has acknowledged, so it's something they'll likely improve on in future projects that haven't entered production yet, at least.
But yeah, I'm personally still in the "I want more good MCU" camp.
I've been finding ChatGPT increasingly useful lately, both because ChatGPT is useful and because Google search feels like it's been in decline.
I'm not a coder. At all. I probably have slightly better understanding than the average non-coder, but looking at code tends to make my eyes glaze over. I'm typically good with the logic of what I want to happen, but the syntax and simply knowing what functions are available are things I really struggle with.
A few days ago, I decided I wanted to make a somewhat simple script. I spent several hours trying things, googling for solutions to the problems I encountered, and ultimately I got nowhere. Yesterday, I decided I should give ChatGPT a go. Not only did I get ChatGPT to write the entire script for me, with me just giving it prompts on what I wanted it to do, but it managed to explain pretty much everything it was doing - with answers tailored to my exact code. When things didn't work, it could speculate on why it might not have worked, and try alternative solutions.
It was a fairly collaborative process. There were points where I could see things that ChatGPT hadn't caught, like certain lines of code that had become unnecessary after iterating, or that variables hadn't been defined properly, and I could point then out and it'd fix them.
Using ChatGPT isn't entirely the same as googling for information, but I think you have to take a fairly similar approach with how you use both. Your language has to be precise and clear, you need to have an understanding of what output you want, and how to tailor your input to achieve that output. And you need to understand how to use the output it gives you - sometimes it'll be wrong, or only partial. Sometimes it'll require further steps to get the final result you're looking for.
That's a good reason!
I'm curious: why are you using Mastodon when you're a kbin user already? Why not just use the microblogging aspect of kbin? It's even federated with Mastodon!
That isn't fun at all :(
It's more aesthetically pleasing and rolls off the tongue better than "regurgitated xcrement"
Or two overlapping lines of cocaine!
About 20 yeses ago - pre-smartphones - my sister lost a phone to water damage. It was in a backpack pocket during a camping/hiking trip and the backpack got rained on a lot. Everyone else's phone was fine because they were kept either in waterproof backpack compartments or in trouser/waterproof coat pockets.
Around the same time, I also had a friend whose phone was broken when we were rafting and the raft capsized. The rest of us on the raft had left our phones at home because _why would you risk bringing a mobile phone on a homemade raft?!_
Those are the only two instances I know of personally where someone's phone has been destroyed by water damage and it hasn't just been an "oops I dropped it in the toilet" situation (I'm still not sure how people manage that). And even the second example was still due to stupidity, I think - there's a reason the rest of us didn't rake our phones on the raft. My sister's phone being damaged in the backpack is the only one that didn't feel preventable, and where a water resistance phone would genuinely have been a good thing.