HTML is NoCode

CSS

Then, CSS was added to go beyond the original nocode definition.

Scripts

Then, <script>s (JavaScript) were added to nocode, to go further beyond the limitations of nocode.

Scripts put code back into nocode.

Limitations of the Nocode Approach

Nocode can only provide a nocode solution to problems that have already been solved satisfactorily.

Nocode cannot address known unknowns nor can it address unknown unknowns, because, by defintion, we don't already know how to solve them.

Some languages let programmers explore unknown problems.  These are usually code-based solutions, e.g. 3GLs and assemblers.

Known Unknowns

Obvious problems that need to be solved:

• Multi-tasking is considered to be a "hard" problem.  Why?  My suggestion - drop the accidental complexities of time-sharing, memory-sharing, fairness, priorities, etc., etc.  Look at closures.

• Architecture tends to be wound deeply into code.  I call this spaghetti architecture.  Why are code and architecture conflated?
• 
  

Unknown Unknowns

I don't know.  

Let's see what the future brings.