No, they’re discussing the way forward and what they think makes sense. In fact, they’re even clearly stating that there will be pain, because Wayland intentionally does less than X11. And they’re encouraging people with unsolved pain points to speak up.
I don’t personally remember this whole story, obviously, but I can’t imagine how else we could’ve just walked out. I guess, another possibility would be that only our mom was visiting the relatives and our dad was taking a mighty nap.
But well, my brother and I were apparently always well-behaved children. And we could’ve always phoned them, or rang at the door of an older lady living in the same house, or walked two streets over to our grandparents or three streets over to friends of the family.
Evidently, we even knew how to walk to our relatives across town, so I do feel like that would have been enough of a support network and at least my brother old enough, so that one could start trying to leave us home alone. You do have to start at some point…
The TL;DR I was looking for: The beavers help to ‘fight fires’ in the sense that they prevent forests from drying out. Their dams will occasionally cause floodings or streams to diverge, which helps to distribute the water.
Mozilla pays for a premium subscription to Google Analytics, which allows them to opt out of data usage by Google. So, obviously Google still aggregates the data, but only for providing reports to Mozilla. Google may not use the data for their own user analysis/tracking, as they would do without the premium subscription. Otherwise, Google would be in breach of contract, which would be an easy lawsuit with high punishment for Google.
I can’t get it to decode, even after correcting the base64 padding. Firefox just shows the broken image icon. My image viewer throws out the glorious log message Image format is actually “png” not “png”, along with a bunch of checksum errors.
I guess, the checksum can’t be correct when it’s cut off, but none of my image viewing/editing software wants to look past that.
I mean, I’ve also done that at times, but it just happens so often around here. You basically can’t drive more than a few minutes on a road without having someone tailgating you…
There used to be the genre of collect-'em-ups, where the thinly-veiled end goal was to just collect various items.
For example, to complete a level in Banjo-Kazooie, you had to collect 10 puzzle pieces and 100 musical notes, and you likely gathered lots more bonus collectibles along the way.
These were essentially just numbers going up. But we do all have that gatherer instinct in us, so if you can get past the meaninglessness, it’s just one of the easiest sources of endorphins.
And I feel like modern crafting systems evolved out of that. While you still can’t think too hard about it, they are providing meaning, in that you’re now collecting 100 wood planks, because you want to craft a house.
The unfortunate side effect is that they are now part of the soup which is pretty much mandatory to include in big budget games.
Indies are perfectly capable of fleshing out individual endorphin sources these days, so AAA games need to outdo them by having multiple. And the whole collect+craft loop is an endorphin source that can be added relatively easily to many game concepts, especially if you’re also buying into the mandatory open world.
So, I guess, the moral of the story is: AAA bad, indies good.
But like, for real. AAA won’t stop using the collect+craft loop, unless we have another massive technology jump where their big budget becomes useful again (like with 2D -> 3D, back in the days).
So, if you’re tired of it, you do want to look into smaller budget games or, I guess, some of the few remaining niche AAA titles…
I used to think so, too, but on the one hand, the DOM API is absolutely massive. Going through the standardization, implementation and documentation process another time would take decades.
And on the other hand, a language-agnostic API in WebAssembly would mean specifying it WebAssembly itself. And well, it’s Assembly-like, so what’s currently a single line for calling a JS function would turn into tens of lines of low-level code.
Ultimately, you’d want code from some other high-level language to give you a summary of how you may need to call your language-specific wrapper. In practice, that’s likely even worse than translating it from JS, because the high-level call isn’t standardized.