This sounds like a possible explanation for why I keep getting recommended different AWS client libraries from the boss to "solve instability" of a service that works 99.8% except for when the S3 endpoint (backblaze) has brief mystery issues.
May I humbly recommend Godot? It has webgl export as well as plenty of others and is fully open source, lots of language bindings as well if you don't want to learn gdscript (syntactically similar to python and honestly is pretty darned easy to work with) https://godotengine.org/
This reminds me of the time I was dealing with a REST API that exposed an image thumbnail.. except the response contained a file path, and the response completed before the file was actually written to disk.
They were paying me to work with this, yet they couldn't be bothered to fix this on their end.
I always considered self directed learning to be less like forcing a child to learn in a vacuum and more like letting the child drive the educatiomobile while you help with the maps.
> They all seem to have a kind of “us versus them” mentality against traditional schooling.
Well, watching a retired public school teacher get huffy and start chomping at your mother about how she's ruining her child can be a polarizing experience.
My mom was a high school art teacher (masters in art ed.) before she home-schooled me, and one of the reasons she'd often bring up was how she felt much of the time spent in traditional education consists of shuffling kids around from one room to the next, and she wanted something better for me.
As for socialization, that was more than likely the most commonly voiced concern I would encounter. I'd get a lot of "but don't you wish you were with other kids?", and I would think "who the heck wants to be stuck with a bunch of kids?"
As a senior dev, doing remote work for a team that seems to be mostly junior devs has been some of the most frustrating things I've ever had to deal with in my dozen or so years of software development. The project manager asks for phone calls (never less than 45 minutes long) 3 or 4 times a day, all throughout the day for status updates and to discuss plans (which mostly consists of me listening to people talk over each other about things they don't understand). All this on top of a project deadline that was just on the edge of being impossible to meet. It felt like a death march, (I was told it wasn't crunch at one point, so they were trying to gaslight me as well) and it would have been so much better for everyone if they would have just let me work.
I've also been on on-site teams where only one or two junior devs work remotely. This always seems to work out poorly, but based on my observations it's usually due a combination of only being willing to only pay entry level rates, and failing to set deadlines for them. When we waited 4 months on a remote while he apparently just spun his tires on a simple bug, even after I explained the fix to him (it was ~4 lines, I basically said "try looking in X file on line Y, if you fozz the frob, does it fix it?") and he just like, could not. Also he'd have "internet issues" practically every day. Now the company is skittish about remote workers, even though it was obviously their own incompetence in managing him.
I know I personally do my best work when working remote, provided I'm not being pestered constantly. I just wonder if the "remote workers are bad" thing because it seems that many people seeking remote dev work are just starting out in programming or trying to transition from other jobs thinking those high paying computer programming jobs sound easy.
With 100 threads running like that, not only do you have the overhead of the OS scheduling 100 threads to run on ~8 or whatever cpu cores, but also I would assume these threads are all running different code, so there would be some overhead with context switching / cache. Presumably these threads communicate, so they're likely using some form of synchronization primitives.