aaronbwebber

your algorithm for multiplication involves doing multiplication?

| 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.

betteridge's law of headlines still undefeated

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_.

if it's not compiled in by default, then you aren't shipping the code! Somebody is downloading it and compiling it themselves!

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.

Big.

https://en.wikipedia.org/wiki/Crescent_Dunes_Solar_Energy_Pr...

How does this kind of shit get upvoted?

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.

Yes it is, it's part of the standard go toolchain as described in the first blog post in the series: https://eng.uber.com/dynamic-data-race-detection-in-go-code/

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...

https://go.dev/doc/articles/race_detector

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).

https://eng.uber.com/dynamic-data-race-detection-in-go-code/

I love Go and goroutines, but...

> 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.

This is probably the best advertisement for loki I've ever seen.

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?

There are comments suggesting that this was reported the Apache some time ago, but a CVE wasn't assigned? Getting a CVE assigned, even with hardly any details at all ("get ready to upgrade log4j") could have really helped people here.

Very important caveats from the paper review at https://mikhail.io/2020/03/infinicache-distributed-cache-on-...:

> Mind that the workload was selected to be a good match for InfiniCache properties (large objects with infrequent access).

> The hourly cost increases monotonically with the access rate, and eventually overshoots ElastiCache when the access rate exceeds 312 K requests per hour (86 requests per second).

So this is not a replacement for the most common use cases for Elasticache. It is interesting as a cache in front of S3, but if you want a cache in front of S3...just use Cloudfront?

Honestly if I was AWS I would be ecstatic if people used this, AWS probably breaks even or maybe loses a little bit on optimal usage of this, and makes an absolute killing if someone using this has a traffic spike and ends up hitting their lambda millions of times.

like PEP484 type annotations having a runtime performance hit? I would be very interested in seeing a link to this if you can dig it up.

But I don't think anybody did get fired? Who of the signees of the Harpers letter is actually being hurt? Even if they _were_ fired, why is that bad? Most of the people who signed that letter are professional writers in some form or another, and their job is to write stuff that people want to read. If people don't want to read it anymore because they write dumb stuff or sign their name to stupid letters, how is that anymore an issue of free speech than if I got fired for writing buggy code or insistently arguing that we should be coding everything in Perl 4?

You can say all kinds of dumb shit and sign your name to stupid letters and other people get to call for you to be fired, and maybe you will be! Even after that, you can continue saying dumb shit and signing your name to stupid letters, and I can go write buggy Perl 4 code, and nobody can stop us! Your dumb letters might not get published in national magazines and I probably won't get paid much for my code but in neither case is this a violation of our free speech rights.

So, it's a fine article, with lots of interesting details about Victorian food supply....but you could write more or less the exact same article replacing "cheap food" with "cheap clothes" or "cheap mobile phones" or "cheap any consumer good" and the stories about Victorian costermongers with Vietnamese sweatshop workers, or Chinese electronics factory workers, or Honduran coffee pickers, etc., and the end of the article seems to be arguing for just paying more for food?

I don't think talking about poverty in modern societies in terms of economic sectors instead of trying to address it at a societal level is particularly useful. The point of the article should not be "let's all pay more for food" it should be "give everyone a UBI and if that means food costs more because you have to pay people more to work as cooks or strawberry pickers, that's a _good thing_.

Yup! As I noted in a comment above, this is just not a common case for us - usually our inbound traffic is coming from SEO which sends you to the right place. But when I am typing it into a search box, it's real easy to forget.

I am going to look into getting those redirects cached though, there's no reason we shouldn't be able to serve them off the edge.

Well...in many cases all it really tells you is the roundtrip network latency, which may or may not be something you are interested in.

In my case it actually was sort of interesting - it definitely suggested that the redirects don't have the correct caching headers, because they clearly weren't being served off the CDN. However, this redirect is a pretty unusual case for us, because most of our traffic is either from SEO or links from notifications we send users.

I agree that you should be looking at the experience most users are going to have, but if the first experience for most users is a redirect you should probably do something about that.

Tip: if your site is going to redirect from the bare domain to something else (e.g. `https://example.com` -> `https://example.com/home/`) make sure you enter the final destination, letting it redirect means that the cost of the redirects will be included in the report, which is unlikely to be what you want.

Can anyone describe at a high level for a complete noob how this kind of thing works? Someone who is not going to be able to read a bunch of ASM and interpret it? I'm guessing that it is something along the lines of:

- the graphics "driver" reads values out of certain registers (AL and AH?) at a set interrupt (maybe every X clock cycles?) and writes one pixel to the screen of whatever color those registers had in them

- by writing values into those registers and aligning the number of operations the program does with the frequency of the interrupts, you can get animation?

Even achieving any sort of flow control so you can switch between the effects is mind-boggling to me.

It appears they have, the y-cruncher program he used does verification. Alexander Yee, who wrote the y-cruncher program (which has been used for the previous 4 world record calculations of digits of Pi), has accepted it and posted it on their site, along with screenshots of the output of the program.

http://www.numberworld.org/y-cruncher/

I would say that leaving it pointing to a vanilla Apache install is pretty on-brand for Maciej. He's currently busy with election-related journalism, but I'm guessing that this thread will eventually get his attention and he will get around to having it redirect to pinboard.in.

I call bullshit. Say what tower it was, and when it was built, and what time frame you are actually talking about so we can verify for ourselves whether it was actually empty or not, or even if it was empty whether it was empty for a good reason (e.g. not having it's habitability permit). Otherwise this is the worst kind of anecdata - not even enough detail to verify that the anecdote is true, nevermind whether it is actually a representative sample of a larger issue or just an odd case.

That's just the NICU expenses. If your baby needed any procedures (e.g. MRIs), that would likely be in addition to that. Both my kids spent ~3 weeks in NICU, bill for everything (entirely covered by insurance except for $100 co-pay!) was ~$90K for one and ~125K for the other IIRC, but a substantial fraction of those were related to the long and complicated deliveries. I think about half of those bills was the NICU and half was delivery/other procedures.