codys

> So in this case, the plastic straw issue does _not_ necessarily appear to be related to the redesign.

Another article [1] indicates that the new design was deployed on January 8th, 2009, and Tropicana announced a return to the old design on February 23rd, 2009.

A quick search shows an article [2] indicating around 2018 was when the panic around plastic straws began (with, for example, Seattle banning plastic straws starting in July 2018).

So in this case, the plastic straw issue does necessarily appear to be related to the redesign.

1: https://www.thebrandingjournal.com/2015/05/what-to-learn-fro...

2: https://www.eater.com/2018/7/12/17555880/plastic-straws-envi...

These days I use meson mostly, but I would love to see a complete build system really get into parallelizing platform checking and merge it into the normal build process.

- A post about a C++ ABI break being voted against: https://cor3ntin.github.io/posts/abi/

I would not be surprised if google (or others in favor of breaking the ABI for the c++ standard library) would refocus on their alternate non-std std-replacement-ish library implementations (like abseil) instead given the lack of willingness to fix things in std proper from the committee.

It notes that the Kingston, Sonnet, and others are rebrands of the Goodway DBD1100.

`sys/queue.h` has it's pointers to the next element rather than the next list_node, while `ccan` and `linux` have pointers to the next list_node, which then are adjusted if needed to obtain the containing element.

In practice, this means that `sys/queue.h` is entirely macros, while linux & ccan's lists can use normal functions for most operations (with primarily obtaining the element pointer being handled by macros). Whether or not this is useful is somewhat dependent on compile time costs for macros vs code, and how small the list operations are in code size (ie: are they always inlined, or is it useful to be able to have a single instance of them). With the linux model, this can be determined at any time (by the compiler, or by the linked list library by changing it a bit), with the bsd model it is somewhat more difficult to make work (one could possibly do this by passing in the offset of the list_node structure to functions).

Compared to the linux kernel's intrusive lists, it also tracks the offset of the list_node within the structure contained by the list, which eliminates another class of problems. It does still have the "using the iterator after the for loop is over" issue discussed in this article, but it also already tracks the types as Linus proposed doing in the article to resolve the issue.

These were single disk systems, no raid at all.

There may be a way to thoughtfully discuss this issue, but this article is a poor attempt at it.

1: https://cen.acs.org/research-integrity/ethics/Essay-criticiz...

This also informs your second question. If new optional fields in json are added, unless you tell serde to complain about them, it won't, and you can add the new Option at your leisure.

- current versions of zfs (ie: openzfs) error (unless forced) when adding non-redundant devices to a redundant pool, and have device removal to handle the case where someone bypasses the error.

- pools can grow in zfs (ie: the things one allocates storage out of). what is probably being referenced here is that one can't reshape a zraid vdev to add more disks to it (basically the reshape operation in classic raid setups). This does make expanding in some cases less flexible that old-style raid setups.

Also, I really have to agree that ARC behavior is still not great under load, and I don't think that's that much of an edge case.

Some testing seems to indicate even ext4 is more reliable in the face of hard power cycles.

(while on linux one can use the docker command line tool without any docker desktop thing, on mac docker desktop wraps together running a linux vm to run the docker daemon & containers inside, making it the most straight forward way of running docker on mac)

It sounds like you have an anecdote about some people you know working on these projects, but the details that seem intended to imply that it's unlikely that _any_ people working these projects are Chinese prisoners actually imply the opposite.

That said: some folks didn't really get the memo, because there are important details that are sometimes included in non-doxygen comments in Apple's headers and thus aren't reproduced into Apple's generated/published docs.

In particular, the headers (sometimes) include annotations for specific types included in CF containers for return values.

My best experiences with packaging on linux have been gentoo ebuilds & arch pkgbuilds. These keep the build model pretty straight forward if the goal is to "just build a package".

That said: creating a dpkg is not an impossible thing to do. It's just more painful than it needs to be

`str`'s data layout happens to be `[u8]`, but it's type provides additional guarantees about the structure of the data within it's internal `[u8]` (for example, forbidding sequences of u8 that don't encode valid utf-8).

For example: determining that interrupts were being routed to FIQ. It's unclear how one would have figured that was occurring. Or that there was an special AIC (apple interrupt controller) that needed talking to, and how to talk to it. It feels like there's a lot of "reverse engineer some Apple kernel bits" that's potentially being elided over.

Edit: or alternately, some debug interface that isn't being mentioned (swd/jtag/itm).

- do you have a finer grained (month by month, for example) break down to support your assertion of the correlation in timing of the NYPD disbanding the "anti-crime" units and the homicide rate?

- if so, is there something indicating there is causation rather than a coincidence?