I would carefully consider which of these actually help address hardware issues (e.g. bit data types) and which are just your own idea of a nice programming language (e.g. braces for block delimiters, lack of reserved words...).OK so I have a draft initial list of bullet points that a new hardware oriented language could consider based on this thread and a few others:
Note that even "pointers" presupposes a particular kind of memory model which may not be correct for all hardware (e.g. content addressable memory).