Jeff Sonnabend in the Ecco Yahoo forum: "I remember first trying to learn Ecco 1.0. It was tough until the proverbial light went on. Then it all made sense. For me, it was simply understanding that Ecco is just a data base. So called folders are nothing more than fields in a flat-file table (like a spreadsheet). The rest is interface and implementation of various users' work or management systems in Ecco. That learning curve, to me, is the primary Ecco "weakness", at least as far as new users go."

In general, I'm unpersuaded by these arguments (learning curve is determined not just by unfamiliar syntax, but by unfamiliar semantics and APIs as well, and the frameworks in question excel at adding complexity in those areas).

Such languages may make it easier for a person without knowledge about the language to understand the code and perhaps also to learn the language.

Did you expect the temp directory to get printed? In the last example, we saw the directories ./temp and ./C/temp got printed, but not now. This is the effect of the -print option. By default, the find command prints all the files matching the criteria. However, once the -print option is specified, it will print files only on explicit print instructions. In this find command, -print is associated in the other side of the OR condition, and hence nothing will get printed from the 1st part of the condition.

Might be a little too low-level (even with GUIs) for some teams of users. GPG and Git both require some setup and experience in these tools, or the willingness to learn. Porting a GPG key from machine to machine is not trivial.

The Grid is based around ideas familiar to Bitwig Studio