As long as you have capacity to keep it mostly empty, it's fine. When requests backup, at least some people will still get quick responses, instead of making everyone suffer.
For a queue, a backup means that every request (from "now" on, until the end of time) is delayed.
For a stack, a backup means that some requests are informally forgotten, and although they still appear to be open, they will not complete until the end of time.
That's worse. It's a better match to the behavior you want, except for the part where the old requests still appear to be open. You need to actually close them.
You might also want to consider how requesting behavior will change when requests are stacked instead of queued. As soon as people have learned that you keep requests in a stack, the correct way to make a request is to make it, wait for a very small amount of time, and then, if your request hasn't already succeeded, repeat it.
> You might also want to consider how requesting behavior will change when requests are stacked instead of queued. As soon as people have learned that you keep requests in a stack, the correct way to make a request is to make it, wait for a very small amount of time, and then, if your request hasn't already succeeded, repeat it.
It would be very hard to learn this so long as the queue is a very small fraction of the total throughput. If the queue depth is 100, and you receive 10,000qps, but process 9,900 qps, the queue will get full, and roughly 97 calls will go unanswered. Ideally you should have another mechanism to time these out, which most systems do. Whatever queue type you pick, you are going to reject 1% of the inbound, but with a FIFO queue, you will also delay 100% of the responses. Do that at several layers, and you can even end up with the client timing out even though their request wasn't even rejected at any stage.
They will listen to anyone who tells them what they like to hear. They will not listen to anyone who tells them what they don't like to hear. They shop around for truths they prefer like they're items at Costco.
People’s preferences tend very strongly toward whatever requires the least action on their part. If the problem is with someone else, then you never have to be part of the solution
It’s political preferences, not laziness. People aren’t listening to Rogan or whoever and ignoring the CDC because of laziness. They are doing that because they follow what their social and/or political community thinks and does.
Feels like this whole thread is trying to pin this on individual preferences or whatever. But it’s a social effect, and individual personalities or intelligence have very little to do with it. If you lived in these communities, unless you are neurodivergent, you would be doing the same thing.
>If you lived in these communities, unless you are neurodivergent, you would be doing the same thing.
As someone who grew up in one of these communities, this has not been my experience. Many, many people move away, and for varied reasons. What you're left with are people who stay in economically declining areas and want to blame everyone else for it. It's selection bias, and it is absolutely based on personal choice.
Seconded. My Silhouette is great. I even emailed them and received a copy of the GPGL docs one time. It wasn't full on support, but they were willing to give me a start.
The first thing I programmed was having it draw a hilbert curve and it worked great!
Why is that stupid? They did get lucky. They are acknowledging that, had they used that, they would have had problems. And now they will work to be more prepared.
Acknowledging that one still has risks and that luck plays a factor is important.
I feel like saying that is supports AI players, but not having a simple, already hosted example is a disservice. Even tic tac toe, or go fish would be a nice hook to help people understand what it actually delivers.
It's worth clicking through and reading details on each one before you commit. Most of them are quite complete, but some only support a handful of devices or features. You can also get a sense if the control is local (i.e. no internet connection) or cloud based.
Nah. I live in Boston. I strongly prefer public transit, but I'll take driving here over most other cities, any day of the week.
The _road layout_ is awful, but drivers are pretty cooperative on the whole. Certainly more than my years driving in DC, for instance.
Granted, you need to be commmital here: if you put on your turn signal, drivers will generally make space for you to get in - briefly - but you need to be quick to take advantage of the gap. I could see Waymo being too slow to the draw for this, based on what I've seen online.
As long as you have capacity to keep it mostly empty, it's fine. When requests backup, at least some people will still get quick responses, instead of making everyone suffer.
reply