| the sunrise spread across the city on its own, on t-shirts and stickers and bike frames and beer cans
tfa appears to admit that people are actually _using_ the new Milwaukee flag. This seems like a pretty strong argument that the new flag actually is better than the old flag? It is kinda cool to have a very distinctive local flag, but if the practical upshot of that is that the flag isn't actually used anywhere except a single flagpole in front of city hall (if that), seems like the vexillology people kind of have a point?
It's not just better performance on latency benchmarks, it likely improves throughput as well because the writes will be batched together.
Many applications do not require true durability and it is likely that many applications benefit from lazy fsync. Whether it should be the default is a lot more questionable though.
It means that the action we should take in response to this article is "building more dorms with singles" rather than "we need to rethink the way that we are making accommodations for disabilities in educational contexts".
That seems like an important distinction, and makes the rest of the article (which focuses on educational accommodations) look mistaken.
I was _extremely disappointed_ not to see this meme when I clicked on the link. Will not consider using this extension until Xzibit is prominently featured.
This is an insane standard and attempting to adhere to it would mean that the CVE database, which is already mostly full of useless, irrelevant garbage, is now just the bug tracker for _every single open source project in the world_.
Great idea! Now to just find somewhere to put a billion dollars worth of solar PV in California, preferably somewhere where it doesn't ever get dark so the power will stay on at night.
it really takes about 5 seconds of thinking about this to realize why this "analysis" is stupid - he takes an INCREDIBLY expansive view of what counts as "pollution" from food production and then takes the narrowest possible view of what counts as "pollution" from driving a ICE car.
It's frankly embarrassing that econlib would even host this kind of crap which would get a failing grade in an undergraduate econ class.
At least some of these would be caught by running your tests with race detection on? I haven't read the whole article yet but as soon as I read the loop variable one I was pretty sure I have written code with that exact bug and had it caught by tests...
Edit: at the _end_ of the post, they mention that this is the second of two blog posts talking about this, and in the first post they explain that they caught these by deploying the default race detector and why they haven't been running it as part of CI (tl;dr it's slower and more resource-expensive and they had a large backlog).
> A newly minted goroutine is given a few kilobytes
a line later
> It is practical to create hundreds of thousands of goroutines in the same address space
So it's not practical to create 100s of Ks of goroutines - it's possible, sure, but because you incur GBs of memory overhead if you are actually creating that many goroutines means that for any practical problem you are going to want to stick to a few thousand goroutines. I can almost guarantee you that you have something better to do with those GBs of memory than store goroutine stacks.
Asking the scheduler to handle scheduling 100s of Ks of goroutines is also not a great idea in my experience either.
An important step here that is missing here is evaluating if your fix is going to cause other, potentially worse problems. I suspect that in this case, it's fairly unlikely that increasing the maximum POST body size to 60 MB is going to cause problems - eyeballing that Sendgrid chart, it looks like we are not dealing with very high throughput here. But it's not hard to imagine a situation where tripling the max POST body size would result in a large increase in server memory usage, which could result in things like OOM kills, which could result in a lot of people not getting their reply emails or whatever.
So don't just rush a fix out. Think about what the effects of a configuration change like this might be, and whether you are just making more problems for yourself down the line trying to fix something quickly.
Maybe I am misunderstanding how this works, but if you did that, you would no longer have a pointer with a valid metadata flag, and if you try to use it, you get a fault (at least on the Morello board that ARM has built). Perhaps you could do this on something that is just emulating CHERI, but at that point why are you doing this at all?
tfa appears to admit that people are actually _using_ the new Milwaukee flag. This seems like a pretty strong argument that the new flag actually is better than the old flag? It is kinda cool to have a very distinctive local flag, but if the practical upshot of that is that the flag isn't actually used anywhere except a single flagpole in front of city hall (if that), seems like the vexillology people kind of have a point?