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.

Thanks :-) I understand what you mean I think, since speaking Italian I've also a strong Sicilian accent... but I tried hard to preserve it, after all it's my origin.

+1 for not forgetting your roots. I am also in a battle with my accent. Hopefully, one day, very soon, I will win it.

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.

Thanks, definitely makes sense to use Disque for messaging and Redis for caching/storage, and for messaging too when you need ephemeral messaging without guarantees, but you need to control very well the semantics, so in Redis you can build your messaging thing using its primitives. But for reliable message exchanges, with guaranteed at least once delivery, Disque is the thing to use (or other good & reliable message queues).

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.

Thanks for your feedback - getting the UI right is one of the big challenges for us given the complexity of the system. We've been experimenting internally with different approaches, one of them being a per-user preference "raw" mode that works as you described.

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.

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

Thanks, i didn't know about it. It doesn't seem to bring relationnal, sql, and joins though ( which may be useful in certain cases).

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.

I suspect the translations cost too much to have much of a free Tier

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.

Most products I know in this space (souce, worked for one years and years ago) were hand translated.

So it was: User types stuff.. stuff goes in a database... a translator gets notified that there is new work.. and he would do it and insert back into the database.. which would eventually make it out to a site.

Google translate style is OK for google results, but not for a professional website.

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.

Thanks. I developed and used it as a utility in a bigger library that worked heavily with types, but later exported it to its own project so I could share it, after I realized how useful it was, even stand-alone.

It is very highly optimized, as performance was of critical importance.