One of the reasons is that the Red community is very small and entrenched. They know everything that comes out of the language, and
to them everything is easy and understandable.
They will fight you to the death if you even try to say that "english-like syntax with no parantheses" is the opposite of readable or understandable when you don't know the system.
Go into any of Red's source files and you will end up looking at dozens to hundreds of lines of code with no comments and which often look like this:
return old-gradient-pen DC cmds start tail cmd sym catch?
OS-draw-brush-pattern DC size crop-1 crop-2 word as red-block! cmd sym = fill-pen
_read opfd hash alg-digest-size type
etc. These are obviously impossible to look up and find.
The whole development is haphazard as well. Everything hinges on two may be three people who know Red internals wihch frantically move from subsystem to subsystem developing features and patching wholes.
Patching wholes are usually like this:
- issue is raised on GitHub
- it's acknowledge
- a fix is written (with zero comments even for the complex issues) and merged
- the issue is closed with a "tested" label [1]
About 0.001% of "tested" issues contain any tests. The majority of fixes are apparently only fixed and manually tested against the reported issue.
etc. etc.
https://github.com/red/red/issues?q=is%3Aissue+is%3Aclosed+l...
They will fight you to the death if you even try to say that "english-like syntax with no parantheses" is the opposite of readable or understandable when you don't know the system.
Go into any of Red's source files and you will end up looking at dozens to hundreds of lines of code with no comments and which often look like this:
etc. These are obviously impossible to look up and find.The whole development is haphazard as well. Everything hinges on two may be three people who know Red internals wihch frantically move from subsystem to subsystem developing features and patching wholes.
Patching wholes are usually like this:
- issue is raised on GitHub
- it's acknowledge
- a fix is written (with zero comments even for the complex issues) and merged
- the issue is closed with a "tested" label [1]
About 0.001% of "tested" issues contain any tests. The majority of fixes are apparently only fixed and manually tested against the reported issue.
etc. etc.
https://github.com/red/red/issues?q=is%3Aissue+is%3Aclosed+l...