And sometimes, it finds what you want, but before you can select it, it decides that it has found something better, and places that in the place where you wanted to select, causing you to select the wrong thing. And then it thinks that because you selected this, it must be what you want, and starts to push it to the top…

Search is definitely frustrating.

This is the challenge of extreme weather, it's either drought or floods, and wild swings from the one to the other. As a kid growing up in Australia, we heard many such stories, especially if the rains came on too suddenly, since then the ground can't absorb the water, and you get flash floods.

As if being a farmer isn't already tough enough.

Not saying it can't be fun, but you can live in a country town almost anywhere, if I just want a permanent base hours from any airport, and they all tend to be a lot cheaper than living in the "big smoke".

Basically JEP401 guarantees that just adding "value" to the class won't change behaviour, which also means that you are not allowed to see object tearing, which requires atomic operations on the field.

Relaxing that would break safe publication rules, at least for Java.

How to get customers to make poor financial decisions? How to sell more phones to people that can't really afford them?

Seriously, what is the problem that is being solved?

Especially not when gp said that they expected the department head to brush it under the rug. If reporting things "up the chain of command" was really expected to root corruption out, and this fraud is 100% a form of corruption, then whistle blowing simply wouldn't be needed.

They covered their own ass, which is fine, in that later the head can't say they didn't know about it. But they didn't blow the whistle.

The current code will help with `Integer[]`, `Char []`, etc, as well as combinations of `byte`, `char`, and `int`. Past that it doesn't really help much.

It would be fantastic if we could also flatten something like `Pair` or `Tuple`. However, even with compressed pointers, that is 64 bits, so that, plus the `null` bit, means it can't be flattened, which is a real shame. For various reasons, I have `List` in numerous places in my code, It would be great if that could also be flattened. However, since a Long is 64 bits, it _also_ can't be flattened. https://openjdk.org/jeps/8316779 would go a long way to to helping here, since then at least the null bit could be thrown away, which would allow more things to be flattened.

And then, if you want to go Wishlist land, something that would allow SSO (Small String Optimisation) would also be awesome, but that would require something akin to unions in Java, which we can _kind_ of do with sealed classes, but, since String is a final class, can't be retrofitted back into the language.

Does anyone know if Valhalla will flatten "simple" sealed classes, where every sealed class is small enough to be flattened? Since that would also be a powerful example to share.

> The documentation should open with something like this:

>> The callback function must perform its work quickly without blocking. If you need to do complex work or synchronize with other threads or processes, do the work asynchronously, such as by using System Worker Threads.

A change was made, but not the change that Raymond thinks would explain why the list is there anyway.

> Bypassing Browser Constraints: Modern browsers aggressively throttle autoplay videos, and ad-blockers restrict traditional media frames. To the browser, ASCILINE is simply "JavaScript updating a canvas"—completely invisible to media restrictions.

Depending on the how pelicans are created, it is entirely possible to indirectly kill "somebody" due to the externalised costs of global warming etc.

You see this in all sorts of places, for example, stealing an EV charging cable. To a thief, a $500 charging station is just $10 worth of copper waiting to be melted down. They don't care about the $490 deficit they left behind because that’s the victim's problem. Social media platforms, and apparently now car manufacturers, look through the exact same lens.

What is different now, is twofold: 1. Bigger financial impact of having a child, both through less government support, and because more women are working. This combined means that to have a child, often, one of the parents needs to stop working, which severely impacts SoL. 2. Less social impact of not having a child. It is far more common to not have children than it used to be, and so it becomes much more of a choice as to whether to make that SoL sacrifice or not.

Then the load during the working days makes those ripples larger and into outages.

Part of this is communication overheads, and as op points out, the need, and ability, to specialise in a larger organisation.

Tying this back to your first point, the revealed preference is that people would rather fill their own gas tank, rather than be forced to wait for someone to come and fill it for them.

Bagging groceries is different, however the revealed preference is that people would prefer the lower price/lower service supermarket, and those that need the help have to ask for it.

You are correct that everyone needs to earn a living, I think that most people would prefer that others can earn a living doing a somewhat meaningful job, in a somewhat safe manner.

The reason that much of this isn't automated has nothing to do with ensuring that jobs exist, but rather that the cost of automation is higher than the cost of labour. This is what op is talking about.

[1] https://en.wikipedia.org/wiki/Revealed_preference