mh-cx

Non-native speaker here. To me in spoken language both "unicorn" and "hour" have a combination of 2 vowels in the beginning. Let me transcribe them as "ee-oo" and "aa-oo" here.

Why is the aa-oo combination at the beginning of "hour" considered a vowel but the ee-oo in "uniform" is a consonant?

As a German I wonder why was this treasure given away to a US museum? Also what is the legal status of ownership of all this? Would have been interesting to read more about this.

My main complaint with conventional commits always was that they don't include an issue number in the commit title. It's not even mentioned in their standards as optional or something.

To me this is almost the most important information in a commit message. I don't know how often in the last 15 years I was cross checking the issue description referenced by some old commit to get the full context of a change. I also felt that this habit is kind of standard - until i had to learn about "conventional commits".

I never got the hype.

You might like

The Dream Machine: J.c.r. Licklider and the Revolution That Made Computing Personal by M. Mitchell Waldrop

Not really about a company, though.

Can someone explain what this is? The page has almost no information (on mobile) and I don't want to install just to find out.

Exactly this. In our case we went so far to cache all static assets. Putting them into a directory with a hash in the name made them still easy to bust.

  # Cache static files
  location ~* \.(ico|css|js|gif|jpe?g|png|svg|woff|woff2)$ {
    expires 365d;
    add_header Pragma public;
    add_header Cache-Control "public";
    proxy_pass http://127.0.0.1:9000;
  }

I wonder why the article doesn't mention utilizing the browser cache for your static CSS and JS assets instead of introducing a service worker as first measure.

Few years ago I built a shopping site MPA this way and the page transitions were almost not noticable.

Even if it's obvious: I was missing a "How to use" section in the README that demonstrates how this tool can be invoked.

EDIT: Ok, there's something in the "Working with STDIN and STDOUT" section. But TBH I'd find it more helpful to have the different use cases collected at the top. To me it wasn't even clear how the command is called.

Hmm, he lost me on page nine where "complete" is explained.

> Complete means that every sequence of vectors |a1>, |a2>, ... satisfying lim ...

How are the elements of this sequence related? And why are we only interested in the elements where the index n/m goes to infinity? What does that even mean if the sequence is arbitrary?

That's probably why I also can't make sense of this:

> Loosely speaking, saying that a Hilbert space is complete means that it contains all of its limits.

> We then ask the primary database for a snapshot, a list of all past primary database transactions whose effects are visible to our new transaction.

I wonder what happens for records with many changes during their lifetime. Wouldn't the size of such a snapshot grow infinetely for them?