![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
The lack of a return type declaration makes this sooo good.
The lack of a return type declaration makes this sooo good.
You know the problem but not the set of reasonable or practical solutions.
Anyways I and l look identical too in many fonts. Should we make them the same letter?
Again you do not because the world consists of more than your interests and job description.
In cases where something looks stupid but your knowledge on it is almost zero it’s entirely possible that it’s not.
The people that maintain Unicode have put a lot of thought and effort into this. Might be helpful to research why rather than assuming you have a better way despite little knowledge of the subject.
You’ve clearly never used ACA. It is helping many millions of people and was recently expanded.
Most of the time. Sometimes it can lead to code that is ambiguous and ASI picks the wrong way to interpret it.
Re: Coding in binary. It makes no difference. Your assembly is binary, just represented in a more human readable form when writing it in assembly.
Re: Manual interaction. Sure there’s plenty of old computers where you can flip switches to input instructions or manipulate registers (memory on the cpu). But this is not much different from using assembly instructions except you’re doing it live.
You can also create purpose built processors which might be what you mean? Generally this isn’t too useful but sometimes it is. FPGAs are an example of doing this type of thing but using software to do the programming of the processor.
I cannot read. Even better.