4 ms·
if you're going to write a desktop environment with widgets, buttons, list views, GL abstraction, file system explorers, image viewers, etc... you're going to r
by jcelerier 5y ago
if you're going to write a desktop environment with widgets, buttons, list views, GL abstraction, file system explorers, image viewers, etc... you're going to reimplement pretty much the whole of Qt Core / Gui / Widgets anyways
- pengaru 5y ago> if you're going to write a desktop environment with widgets, buttons, list views, GL abstraction, file system explorers, image viewers, etc... you're going to reimplement pretty much the whole of Qt Core / Gui / Widgets anyways Is this not the same basic rationalization process anyone goes through when introducing third-party dependencies to a project? You either: 1. don't include the functionality 2. implement it yourself 3. depend on something else to do it for you
- jcelerier 5y agobut when we are talking about open-source the only practical difference between 2. and 3. is the git repo in which the files are. There's no difference between depending on myself from yesterday writing pushbutton.cpp and depending someone else writing the same code 15 years ago, those are different persons than myself writing image_editor_ui.cpp today in both cases.
- pengaru 5y agoI don't see what this has to do with whether Lumina has dependencies or not, it obviously does. The rationalization process is completely orthogonal. I'm not here to debate the value of dependencies which you seem to be interested in defending.
- deleted 5y ago[deleted]