How the experiment is going so far

Bosque was born from an investigation paper based on the idea of questioning the causes of accidental complexity and proposing a solution that tries to eliminate this from the design of a new language. This paper exposed an interesting setting about how we could improve productivity, have clearer, more legible code, and, in turn, have a smaller margin for committing errors during the development process – all of which can be done by eliminating the causes of complexity.

Later, the language was published as an open source project on GitHub, ready to receive support and community contributions. During this stage, Bosque ceased to be a prototype or experimental language for starting a roadmap to complete its development. It did this by implementing many of the basic characteristics, which turned it into a language for developing applications. However, at the time of writing this book, version 1.0 has not been released yet.

In this process, elements such as commentaries, core libraries, and tools were added that simplify the curve of its adoption by new developers. A series of characteristics were also added for its possible applications. If we're ready to sacrifice things that haven't been implemented yet to adopt regularized programming and to start to change our ways of thinking and solving problems, Bosque is a good choice.

What next?

According to the imminent implementations roadmap that should pop up in the next few months, the following will be coming next:

• Memoization and singleton pragmas
• Module/package support
• Improvements to the core collection libraries
• Earlier microframeworks, to simplify the development and adoption process
• N-API native modules so that we can use Bosque via Node.js
• Integration with the Morphir Project
• Multiple file compilation

Let's look at some cases where regularized programming and the Bosque approach might be more suitable than other languages.