hashi

The common example of hashi (bridge) and hashi (chopsticks) demonstrates that.

IBM probably wants to bundle hashi products as part of their cloud offerings and can milk other cloud providers in licensing fees.

I just haven't seen a meaningful level of reaction compared to the community outcry when Hashi changed to BSL.

While it had some quirks at the time, it (and the rest of the Hashi stack) were lightweight, nicely integrated, and quite pleasant.

How often are you listening to your own native language and you are confused by two words that sounds similar (like 'hashi' in Japanese for bridge/chopsticks)?

Chord, the Click Modular Router (super big deal to me), RON (also a big deal to me), Vivaldi (which made its way into the Hashi products).

Now contrast this with the japanese hashi (chopsticks).

There are exceptions when rendaku does not happen, but typically whenever a word like hashi becomes a part of a compound word it will be voiced to -bashi.

Actually my name literally translate to 'Big Bridge' O - hashi:) If you're a talented guy, I am sure finding work isn't a problem.

My understanding is that most Hashi shops would federate workloads of our size/global distribution; it would be weird to try to run one big cluster to capture everything.

I lived in Japan for nearly 6 years and found that concern for faux pas such as these for hashi (chopsticks) are way way overblown.

I was recently diagnosed with low thyroid (not specifically hashi's but, again, probably) and had 100% of those symptoms (and many others) for my entire life.

For example 箸 (chopsticks) and 橋(bridge) are both "hashi" but with a different pitch accent.

Any thoughts on CSPs making money from open source projects while the open source developers (e.g., Redis, Mongo, Hashi) suffer)?

Hashi is chopsticks and bashi is the voiced form of it.

Former-Hashi employee here: there's a clear prioritization of enterprise products.