telegramswift

Better comparison with WhatsApp instead of ancient text editor would be Telegram app [1] built with Swift and C/C++, given hypertext and rich media that is modern messaging app like Telegram, it is resembles more a subset of web browser functionality rather than text editor, so binaries for this around 235 MB in size. [1] https://github.com/overtake/TelegramSwift

While the Qt Telegram app runs fine on macOS, most Apple users opt the Swift/Cocoa client for macOS and iOS[0]. [0]: https://github.com/overtake/TelegramSwift

Meanwhile: https://github.com/overtake/TelegramSwift/issues/195

The source for the clients is available. 1. https://github.com/DrKLO/Telegram 2. https://github.com/TelegramMessenger/Telegram-iOS 3. https://github.com/overtake/TelegramSwift 4. https://github.com/telegramdesktop/tdesktop

Whoopy-fuckin'-do! More flashy junk to keep the morons happy. Meanwhile a four year old issue regarding missing scrollbars on OSX is still unaddressed: https://github.com/overtake/TelegramSwift/issues/195

Or optionally on Cocoa and UWP, which are even more “native” on their respective platforms: https://github.com/overtake/TelegramSwift/ https://github.com/UnigramDev/Unigram I’m a huge fan of Telegram’s model of releasing a cross-platform core for the community to build their own clients on top of. I wish all chat apps followed its lead.

Telegram hires excellent developers and was started by someone that had successfully run a company before. The clients for the different platforms in the case of telegram were developed by very small teams (1-2) of exceptional programmers. - macOS client: https://github.com/overtake/TelegramSwift/graphs/contributor.... Written almost single handedly by one developer. - Telegram Desktop: https://github.com/telegramdesktop/tdesktop/graphs/contribut.... Written almost single handedly by one developer, who also wrote almost all of the supporting Qt code.

This repository has been notoriously bad at doing this: https://github.com/overtake/TelegramSwift

Oops. Thanks! ...although I realized just now that I'm actually using the native client, so it should actually have been another "native" in my case. D'oh. https://github.com/overtake/TelegramSwift

I gave up tracking the delay a while ago but I think the macOS and iOS packages were lagging by six months at one point. Heck, even now the last commit with actual code [1] is over two months old yet the macOS app updated two days ago for me. Uncommented code is dumped into the GitHub repo every couple of months after enough people complain. That's not what I would call open source. [1] https://github.com/overtake/TelegramSwift/commits/master

> I have yet to see any proof of this. See https://github.com/overtake/TelegramSwift/issues/163. I don’t know too much about Signal other than the fact that it exists, so I can’t judge it in comparison to Telegram.

I’m doing the research work for you, though it’ll be a while before I can stop procrastinating for long enough to write a whole thing about it. While you wait, https://github.com/overtake/TelegramSwift/issues/163 is probably a good start.

Telegram is far from being "open-source", either–they reap the benefits of being associated with GPLv2 but fail to publish their code in a timely manner, and appear to be infringing on a number of third-party licenses: https://github.com/overtake/TelegramSwift/issues/163

Telegram for Desktop is https://github.com/telegramdesktop/tdesktop (Qt, open source stuff) Telegram is https://github.com/overtake/TelegramSwift (Swift, Core* libraries) Both are native.

> the client is open source Uh, no it’s not. The client (which happens to seemingly violate a bunch of open-source licenses) and the code posted to GitHub do not match; occasionally a source dump is posted online but there’s no indication how this relates to what they are shipping, as the released binaries differ and update much more frequently. The author is quite unresponsive about this: https://github.com/overtake/TelegramSwift/issues/163