Frankly, this article might be better because it's very short and encourages you to go out and put it into practice immediately. Which is arguably more valuable than reading an entire book to make the same point.
I wouldn't say that this article and the book just "make the same point". Zerubavel devotes an entire chapter to explain how to get a good estimate of the time required to complete the project, another chapter provides tips about how to track progress efficiently, etc.
I used Nim in several projects in the past. The language has much to love, but the tooling is awful. If you're fine coding using JOE/Nano/Pico, then I would say: go for it, you'll surely enjoy the experience! But if you are accustomed to IDEs to do refactoring/automatic formatting/test execution/logging/etc., it's better to look somewhere else. Even basic functionalities in the VSCode extension are buggy.
My wife is Romanian, and we visit the country once every year. There are plentiful of things to visit in Romania; the most beautiful cities are Sibiu, Sighișoara, Brașov, Timișoara… We have still to visit the famous painted monasteries in Bucovina, which seem to be amazing.
macOS and Linux too though? As far as I'm aware, most Linux distros need the build-esssentials (or equivalent) package installed, and on macOS the Apple Clang toolchain also isn't pre-installed. Both is quite similar to installing the "MSVC Build Tools" (MSVC command line toolchain without the Visual Studio IDE).
I use Kitty, which is extremely fast, and I often avoid calling `tail` to print the end of a long log file: the terminal is so fast in displaying it that it's useless.
Another case is when you mistakenly invoke a command that produces a lot of output. With Kitty, terminal output is so fast that the output ended before I could reach Ctrl+C.
Does this really define a new range-checked type? I never used in_range, but it seems a function [1] that you must call whenever you want to do the check on one variable, while in Pascal all the checks are injected automatically every time you modify a variable of that type.
If I understand correctly the other comments, they just say it's possible to do in c++ with templates/operator overloading/constexpr. It's not an existing type of the standard library. This type could work in simple situations but will probably not be as good as a native type in more complex situations.
The fact that slurs and grouping must be appended after the note hasn't always been so. I have been a user since its first versions, and at the beginning you would write a legato scale like this:
(c d e f g a b c)
which indeed looks more natural because resembles the way parentheses are used in mathematics and programming.
If I remember correctly, the change happened ~20 years ago because it made the notation more consistent: everything related to the note happens after the note name (durations, staccato, marcato, slurs, etc.). I remember that it took me several months to get acquainted with the new syntax.
reply