HN2new | past | comments | ask | show | jobs | submitlogin

Sometimes the technology "background" changes so much that the codebase you have just becomes irrelevant.

We live in a world with WebRTC, embedded agents and digital telephony. The platforms, OSes, infrastructure are so different from how they were in 2009. Does having your own, 500 kloc C++ real time video chat stack make sense any more?

What I don't get is how MS couldn't use the Teams stack to power Skype as a consumer brand. Probably there was some effort but something got in the way. It might even have been a cultural barrier - Skype was an acquisition, and acquired codebases generally fossilise



So the answer can change over time. You have to periodically re-assess the benefits of a rewrite.


> Does having your own, 500 kloc C++ real time video chat stack make sense any more?

Yes, if it is less bloated than Electron-based. See Jami, which is a native app and it's distributed and open source.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: