The recent Iran-Hormuz oil shock notwithstanding, the major affordability issue in recent years has been housing, and that's more of a land-use policy issue.
Not arguing with your point about Google, but isn't Apple very often accused of forced obsolescence through updates to their phones? Is there any truth to the accusations of "running slower and dying faster" after a new model releases?
Nothing at all like what Google has done for the Pixel 4a and 6a. They intentionally make the battery life so short after 400 charge cycles (maybe a year's worth of charging?) that it only lasts a few hours. They'll replace the battery only "in eligible locations and while battery supplies last."
For Apple, each iOS release is more demanding than the last. Then compound that with batteries produce less current as they age. So, the CPU can't run quite as fast because it can't draw as high of current for older batteries. The alternative is to let the CPU try to ramp to max and cause the CPU to error/crash. It was mostly a messaging failure, and the battery health info/settings got significantly improved because of it.
Not every church is associated with a large international community. My girlfriend is an avid churchgoer and her church has 46 members I believe. They aren't Catholic and not associated with a broader group. They're called "Primitive Methodist" so I guess there's a broader denominational link to other churches, but they don't get orders from anyplace above them or anything.
It sounds nice to someone like me who doesn't do any organized religious stuff, because the money and things donated there go back to their little community or for maintaining the building and things like that. I see firsthand how that kind of church drastically helps her have a sense of community in an increasingly digital-first world.
I used to work for a company that did GIS mapping of guard rails, lines, and road signs. Part of what we always ended up doing was massaging the data we received from the Lidar mapping to line things up to exact locations for clients. If this map is accurate, I salute whoever spent the time fixing the details.
I don't have much experience with lidar, but I do with machine learning based approaches with photographic data. There has been a massive explosion in the last 5-10 years in filtering and processing algorithm advances that can more readily clean up false positives and insignificant noise. I would assume the barriers to high quality data are quite a bit lower now.
It's an issue with Godot on the web unfortunately, when you're dropping frames the audio starts clipping and crackling. Judging by the other comment, the lua integration must be doing some heavy work.
Same for me, when the code is not correct, the music is much slower and very crackly. Once the code gives the correct solution, the music speeds up and the crackles go away.
I got "Negociate" after like 20 tries, the spelling of which I've never seen. I ended up using the hints to figure it out. When I clicked on the link of the word it took me to a "No results found for negociate!" page on Dictionary.com. Pretty frustrating, might want to double check your word list.
I suggest having two lists: a small handpicked list of 1500 possible goal words, and a copy of /usr/share/dict/words with common misspellings added as acceptable guesses
