What jumps out from that thread you linked is the casualness of the gamers. So not only did Google find a tiny market, but that market wasn't terribly motivated.
Neither Pokemon nor Animal Crossing strike me as casual. I think of Candy Crush and all the games like that. Not games with a story that start off with a tutorial.
I disagree with this use of metric completely. I game a lot, and I own multiple devices on your list above yet subscribe to 0 of the subreddits. People subscribe to the subreddits of _games_. You didn't even count /r/nintendo instead. If anything, I think the fact that these subreddits have so many people is actually a point against what you're arguing about the size of the casual market. I do agree with you on the larger point though, stadia had no product/market fit
This looks cool but I would expect a big section on the home page about why I should trust you and upload my bank statements on your website.
I don't doubt that it works but I'm frankly amazed that people have paid for this service and happily uploaded such sensitive documents without any kind of reassurance (hell even just some plain old marketing)
I agree with you on that, a few customers have called me up to make sure I'm not a criminal. It doesn't seem to be an issue for 99% of my users though. I don't do anything with the documents or data in them, they get deleted quickly and automatically as well.
I'm building a simple page. Ok let's do simple html. Now I need popup for email capture, ok add a bit of hacky js. Now add a menu, could potentially be done with css only.
Now add responsive images. Good luck. You need to process then on server side, then handle them on client side etc...
Now add some customer area...
Add a few more features and it becomes complex.
Why would you want to now throw away all this and rewrite in react when you could just start with react.
In addition I can even migrate my old app to the new one and sometimes I can just copy paste certain components and css styles (thanks to css in Js) and it just works.
Honestly I don’t want to write responsive images manually. I just wrote a system once, now any app reuses the same thing. Same for other stuff. Plus I only need to know react and I can build anything.
You telling me now to learn htmlx syntax and use it sometimes, then use react other times just because… it’s simpler. The benefit is minimal, but now I need to know 2 worlds: react and htmlx.
Not meant as a criticism, but if this is the way you build websites, you are doing it wrong. If you are building a website in a way where you can not anticipate beforehand what will be needed a few steps later because you skip the one most essential step — the planning phase — you are gonna have a bad time.
Of course customers change their mind constantly, which is why you anticipate this in you choice of architecture to leave some wiggle room. The scenario you described tho: I never even remotely had a situation where it bit me in the arse that I wrote HTML with JS sprinkled in. For more complex stuff I have flask, django, websockets, htmx, custom REST-APIs I can built in any other language interacting with custom JS on that webpage (most of the software I write is server side). Or I could just take something like Grav CMS and write a custom Theme and some plugins for it. What is a good starting point depends on the kind of website.
There is so many ways to skin the cat it is not even funny. And if you don't know what cat it is beforehand it is your fault for not asking.