Every day, or every few days at the least, somebody comes on /r/golang and asks something along the lines of “Which framework is the best?”. I think we should attempt to ask this question, at least in a way that’s easy to understand. You shouldn’t use a framework.
Writing elegant or readable code is a driving force for some programmers that have been around long enough to know that less code is usually better than more. We also know that less code is usually also less efficient than more, for various reasons. Depending on how you like your cat skinned, there are several ways to do things.
Parsing strings would arguably be one of the more basic operations that one can do in any language. Sometimes, this may mean comma separated values from an user input on a web page, it may mean parsing application arguments from os.Args, or parse some line based input like lines from an IRC chat, Slack, Discord or some other chat system for a bot.
If you’ve been following along, you know that I’ve been developing Pendulum editor as part of the #100DaysOfCode challenge, where one commits to writing code at least one hour per day. Pendulum is a web based editor which is great for editing simple text and Markdown files.
Slices are tricky. If you have been using Go for a while now, you may be aware that a slice is basically a triplet consisting of a:
This makes working with slices also a bit different than working with structs.
Viper is a popular configuration library that’s designed with 12 factor applications in mind.
Viper is a complete configuration solution for go applications including 12 factor apps. It is designed to work within an application, and can handle all types of configuration needs and formats. Viper can be thought of as a registry for all of your applications configuration needs.
Let’s use it to provide configuration for a typical application.
