ie

Swell merchants could technically make this available since it’s part of the storefront API

I am a native english speaker (born/raised in California) and also very self conscious about the way I sound for different reasons. I suspect many of us have this kind of internal battle, even if it seems relatively insignificant to other people.

FWIW, I think your accent is interesting and enjoyable to hear.

Understood everything no problem. Having recently implemented a job queue system using Redis I am excited to see Disque.

I wonder if it makes sense to use Disque in the same environment as Redis, since we have use cases for both a key-value store as well as a job queue.

I am interested in the concept, however I feel like the mix of GUI and code editors is too complex. I'd rather see it all in a code editor without the GUI.

I'm working on a cloud platform that does this, with a schema layer to enforce types, validation, links, and other meta properties.

It's not publicly announced yet, but if you're very interested in playing with it, ping me at eric at schema.io.

Aren't they just records in a database? Assuming Localize has a scalable architecture, it shouldn't be too hard to support sites with little traffic and few phrases.

TokuMX brought ACID to Mongo a couple years ago, and it's pretty solid.

It's a convincing pitch and got me to spend some time on your web site. I suggest you consider adding a small free tier to give people more time to get accustomed to the product before committing money.

I appreciate the approach of managing translations outside your backend code, but I wonder about whether the translated content can be indexed by search engines.

This looks incredibly useful and I appreciate the focus on performance. I often avoid writing helpers for type checking edge cases due to performance concerns, but you've done the hard work for me. Thank you.