go-i18n VS natscli

Thanks for sharing, from a quick read this looks easier to maintain than nicksnyder/go-i18n.

I am using Nick Snyder's go-i18n for translations. I am also building a go library intented to be imported by either by other libraries or cli executables. All of the documentation I have seen about supporting i18n assume this is being used in an app, but don't cover the scenario where this is being implemented in a library.

On a different note you may consider exploring nicksnyder/go-i18n as well, it simplifies things a bit.

I am trying to get to grips with i18n in Go but finding that most articles on the subject are either inadequate or geared towards web applications. This query is specifically for cli applications and libraries. The kind of articles I've looked at so for are i18n managing translations and internationalization i18n go. I have also investigated using Nick Snyder's go-i18n, but the more I learn, the more I'm coming to the conclusion that it's not necessary for my needs.

What you are looking for is I18N like https://github.com/nicksnyder/go-i18n

This article will show you how to prepare your Go project for localization using a very popular go-i18n package.

I've looked at many packages for this operation (including the one built into the Go core), but nicksnyder/go-i18n was the only one I enjoyed working with in my projects. We will create our demo application using this particular package.

Nats provides a nice CLI that can help with debugging: https://github.com/nats-io/natscli

Besides that I'm also working on a UI solution, that will help to get better overview of your cluster: https://qaze.app/

You should just use the `nats` CLI tool (https://github.com/nats-io/natscli/) instead.

This cli is used by NATS cli which itself needs to use json schema to drive it and so shows the concept of using data to drive itself at https://github.com/nats-io/natscli

In this article, we’ll take a look at NATS CLI and learn some basics commands. In my opinion NATS CLI is quite underrated, it offers many features and can help eliminate most of the manual scripts used to manage a NATS server.

Now let’s use the NATS CLI and do a simple benchmark to generate some publish/subscribe events.

Next, we will need the NATS CLI. We can simply install it for Linux from the GitHub releases page.

NATS CLI

While running nats server using cli or docker container is usually the preferred way but in some instances, it can be unnecessary, one such example is testing. While testing, it’s often cumbersome to spin up new instances for external services, this can be completely avoided by using an in-memory server. Luckily, NATS server package provides this functionality out of the box!