For twelve years, think-cell had been a Windows-only software company and their codebase of approximately 700k lines of code had accumulated many unintentional platform dependencies. Six years ago, the company decided to port their application to the Mac. This change has affected every part of the development process: the project organization, build system, and the way they program in C++ today.
The commonly used cross-platform libraries such as Qt and boost were good tools to build on, but by themselves were not enough. For many concepts, such as mutexes, semaphores, or shared memory, they only offer a common interface to platform-specific objects with very different semantics and lifetimes. The team wanted light-weight, platform-independent C++ abstractions with identical semantics for rendering, internationalization, file I/O, mouse event handling, RPC calls, and error reporting. Developing these was challenging, firstly, because they had to define which semantics application needed and, secondly, the team had to implement them on each platform. This was not an easy process but Sebastian would argue it has improved the quality of code very much.
By now, think-cell has moved on to the next challenge and has started to move some functionality to web applications. They wanted to reuse the existing code-base of course, and that meant writing web applications in expressive, type-safe C++. Definitely an advantage in the book! They have built web applications using emscripten, but thanks to a student intern, they generate type-safe C++ bindings, beyond those provided by emscripten, from any TypeScript interface definition.
In this talk, Sebastian will give you an overview of the C++ abstractions think-cell have implemented, focusing on the cross-platform problem areas where common semantics were hard to define due to limitations of either one of the operating systems, and of course, Sebastian will show you tools that let the company write a web application in C++.
Почему этот доклад в программе
Чем хорош спикер: Себастьян работает в компании с момента её основания, поэтому как никто может подробно и в деталях рассказать не самую простую тему опираясь на примеры из собственного опыта.
Чем хороша тема: Интересная тема в 2к20: что может пойти не так когда создаешь ПО под разные платформы, пусть даже на одном железе.
Кому будет полезно: Разработчикам кросс-платформенных продуктов (а это может случиться с каждым).
Почему здесь и сейчас: