This software was suppose to be "reliable" and presumably bug free, but there are already 2,222 bugs against it. Obvivously it is a complete failure.
I think the only solution is a complete rewrite of all the code from scratch, and this time pay better attention to the overall design.
With that bug, it made 2223
I would argue that all issues are "as designed" as they reference no code at all, and that we are indeed discussing the success of the project, since all references to code involve the absence of it.
I don't buy it. If these issues really were "as designed" then the maintainer would have closed these bugs ages ago. The fact these bugs are still open proves that they must be very difficult to resolve, and as such we need a rewrite in order to simplify the design.
https://github.com/kelseyhightower/nocode/issues?q=is%3Aopen+is%3Aissue+label%3Abug
none of the issues are reported as "bugs" therefore nocode has nobugs.
as per Contributing.md, please explain how it is possible for nocode to have a bug, which would be a necessary premise for any consideration of a re-write.
In fact by definition if you have no code you cannot re-write it, and therefore this re-write which you propose must already have been done an infinite number of times resulting in this most purely refined state of nocode.

:trollface:
Most helpful comment
I don't buy it. If these issues really were "as designed" then the maintainer would have closed these bugs ages ago. The fact these bugs are still open proves that they must be very difficult to resolve, and as such we need a rewrite in order to simplify the design.