And for what? My back end on a single host isn't pumping at 35k qps. If each request is 500 bytes, 35k qps is nearly 20mbps sustained with zero other io (in each direction). And this is using only two threads!

I think you'd be hard pressed to find an application where this is meaningfully useful versus just scaling horizontally. On a box that can run many threads in parallel, Caddy still vastly exceeds my ability to respond to pretty much any useful traffic. It's optimizing for a metric that wasn't a bottleneck in the first place.

Yes. They have a shared catalog. All of this is coordinated. It's literally the whole point of being a librarian.

This is actually a mostly-solved problem in many cases. Many librarians have great SQL skills (or at least the ones I've met) and can query this easily. Most regional library systems have a centralized catalog. And the cost of moving books on demand is fixed: a van with one book and a van with fifty books costs the same to drive between branches.

Most colleges and universities have agreements with each other for exactly these systems and they're actively used. My partner considered completing his U Chicago PhD from San Francisco by way of the Stanford library.

> I do not understand why you would buy 20 copies of one book when you could have it and 19 other books.

Easy answer. Libraries know what their clients will check out. Often, because books are requested. If fifty people wait-listed the last big Dan Brown book, the library buys enough so that those people aren't waiting months to get their turn.

And yes, it's frustrating for librarians. Nobody likes buying lots of books that are not especially good. But that's literally the whole point of the library. Providing access to books that people actually want to read.

I used to work in a library, and this was often the case. Our basement was stuffed to the gills with romance novels that nobody was reading anymore, mysteries published decades ago, and kids books that probably related to kids from a previous generation more. A yearly sale would see the collection trimmed. Almost across the board, you could still get those books through interlibrary loan. If not from the county network, from another library in the state. In my time, I never heard of anyone missing a book that had been disposed of.

I agree with the approach you are suggesting, but the reason I find these wrappers pop up: it's VERY hard to make components composable without them.

Let's say you want to have a block that adds spacing between each item within it. Easy: it's flexbox with a gap. Oh no, but a child is displayed inline, and has weird vertical alignment. And another child has an unexpected align-self. Now you get wrappers on the children.

Maybe you want a button. It's got an icon with text. You need a wrapper on the text, because without a wrapper you basically can't get anything right (you can't rather bare text with CSS).

How about a checkbox? Should be easy. You want the component to have the checkbox on the left with the text on the right. You want to allow two rows of text, with the first being in bold (the label) and the second row being a description or help text. You wrap the whole thing in a label element because you care about accessibility. But you need a dummy div to render the checkbox, because you can't reasonably style checkboxes. And each row of text needs a wrapper, because bare text. And maybe another wrapper around the two rows, because while you can use CSS grid to position the two rows above each other, lord only knows what the checkbox is inside of and whether it's flexbox or grid, and the height of the label might be weird and jack up the positioning of your text. God help you if any of the rows have text that doesn't wrap and is wider than the width of the checkbox's container.

The unfortunate truth is that you probably don't need the wrappers, but there's an element of defensive coding that just makes it infinitely easier to get things right all the time with wrappers.

Nothing about this deal is about better technology or talent. It's about an opportunity that's too juicy for Google to pass up on.

I'll look forward to more developments with Norfstjernen. What an exciting time for me browser engines!

Were we not pursuing criminal cases against these individuals previously? Or have we only just decided to make crimes be against the law now?

Edit: let's all remember, by the way, this "review" period does nothing for security. It exists to allow members of the government to trade on insider knowledge.