Hot take: YAML isn't a configuration language or a configuration language format, it's a serialization format. Is de-serializing some data structures the best way to configure a program? Maybe not. (Probably not. Mostly not.)

Like programming languages, all configuration systems communicate with both the computer and other people. But most are designed only for the computer to consume, not to be clear when people read it. De-serializing your live data structures is an extreme example of this.

LanguageTool is a free proofreading tool for English, German, Spanish, Russian, and more than 20 other languages.

written by Walter Bright

My career has been all about designing programming languages and writing compilers for them. This has been a great joy and source of satisfaction to me, and perhaps I can help others with some observations about what you’re in for if you decide to design and implement a professional programming language. Of course, this is a book length topic, so I’ll just hit on a few highlights here, and avoid topics well covered elsewhere.

Rob Pike, the co-author of the Go programming language, speaks about a career spanning four decades, and the evolution of Go over the last ten years.

I was very excited when I first used YAML, but some real-world usage showed it's not so great after all

Gherkin uses a set of special keywords to give structure and meaning to executable specifications. Each keyword is translated to many spoken languages; in this reference we’ll use English.

Ballerina is an open source programming language and platform for cloud-era application programmers to easily write software that just works.

The Odin programming language is designed with the intent of creating an alternative to C with the following goals: simplicity, high performance, built for modern systems, joy of programming.

The language borrows heavily from (in order of philosophy and impact): Pascal, C, Go, Oberon.

Niklaus Wirth and Rob Pike have been the programming language design idols throughout this project.

C∀ (C-for-all) is an open-source project extending ISO C with modern safety and productivity features, while still ensuring backwards compatibility with C and its programmers. C∀ is designed to have an orthogonal feature-set based closely on the C programming paradigm (non-object-oriented) and these features can be added incrementally to an existing C code-base allowing programmers to learn C∀ on an as-needed basis. In many ways, C∀ is to C as Scala is to Java, providing a research vehicle for new typing and control-flow capabilities on top of a highly popular programming language allowing immediate dissemination.

Reason lets you write simple, fast and quality type safe code while leveraging both the JavaScript & OCaml ecosystems.

As used to author Heaven's Vault, 80 Days and Sorcery!: produce interactive scripts by writing in pure-text with ink markup.

Pike is a dynamic programming language with a syntax similar to Java and C. It is simple to learn, does not require long compilation passes and has powerful built-in data types allowing simple and really fast data manipulation.

Pike is a general purpose programming language, which means that you can put it to use for almost any task. Its application domain spans anything from the world of the Net to the world of multimedia applications, or environments where your shell could use some spicy text processing or system administration tools. Your imagination sets the limit, but Pike will probably extend it far beyond what you previously considered within reach.

The non-repetitive alternative to YAML...

Dhall is programmable, but NOT Turing-complete.

Dhall supports comments, multi-line string literals and string interpolation with non-technical users in mind.

Awk is a very nice language with a very strange name. In this first article of a three-part series, Daniel Robbins will quickly get your awk programming skills up to speed. As the series progresses, more advanced topics will be covered, culminating with an advanced real-world awk application demo.

Simple, fast, safe, compiled programming language.

Nice approach. Still not mature.

I marker this article as "funny" since I can not believe it is serious. Or at least I'm missing something...

Choosing a programming language for a project is a compromise over what you what you need, what you have, what you know and what you like. This post is just my thought process when selecting the implementation language for packnback.

What we need

• High performance, we will hopefully be dealing with large volumes of data.
• High security, the whole purpose is to protect data from attackers.
• Stability, software needs to be usable well into the future.
• Simplicity, the less complicated something is, the less that can go wrong.
• Popularity, this is mainly to help with marketing, libraries and community support.
• High bus factor, will sudden unexpected events destroy the language prospects.
• Fun, something we enjoy using or evaluating.