- There is a lot of hardcode in the Telegram coding and no constants. There are no system constants, and the app itself has no constants. Other open source Telegram dangers include:
- Magic numbers for int values that are provided as flag values, such as 42540. T Magic numbers for int values, such as 42540, which are passed as flag values, sprang to mind. The code of elegram is obfuscated, although this isn't the case.
- If-Else sentences are too long, and there are some methods that are quite long (i.e. 300 lines of code in one method). Furthermore, you can't locate documentation for these methods (or there is some that is incomprehensible), and you can't support such code. You might spend up to a month changing, disabling, or adding a new feature if you wish to do so.
- There's a spaghetti code. Telegram's code is dense and difficult to read, so just understanding its design might take days. We have yet to meet a programmer that enjoys spaghetti in their code.
What's wrong with Telegram’s open-source code?
Asked 29-Jan-2022
Updated 29-Jan-2022
Viewed 423 times
What's wrong with Telegram’s open-source code?