IssueRaiser

[v3] New major release discussion thread

### TL;DR I'm planning a major update for Caesium and need your honest feedback on what you like—and what you don't—about the current version to help shape the new one. ### Overview Caesium v2 brought significant improvements over v1, particularly in code quality and features. Since January 2022, the software has processed around 2.3 billion images, compressing roughly 4.6 petabytes down to about 1.3 petabytes. Despite these successes, the growing number of issues and feature requests indicates that a new major version is needed. ### Background I started Caesium in 2009, right after high school, using C++ and Qt, which were my go-to technologies at the time. Over the years, as I became a Full Stack Web Developer, I integrated new technologies—like Rust for the core library—to keep the project alive while professionally focusing on completely different languages and technologies. Although web-based UIs and Electron were popular choices, I stuck with Qt because of familiarity and its multiplatform capabilities. ### Current Concerns #### My personal concerns about Qt: - Using C++ (which isn’t my strongest language) makes maintenance harder. - Qt Widgets can look outdated, especially on macOS, and often lag behind in adopting modern OS features like Windows 11 Dark Mode. - The auto-update system is clunky and relies on third-party tools (Sparkle/WinSparkle). - The build and release process is cumbersome, requiring the full Qt framework and complex packaging. #### Mainten

Posted by Lymphatus on Mar 8, 2025, 12:44 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments

reliability (SaaS)

[v3] New major release discussion thread

LymphatusMar 8, 2025, 12:44 PM

### TL;DR I'm planning a major update for Caesium and need your honest feedback on what you like—and what you don't—about the current version to help shape the new one. ### Overview Caesium v2 brought significant improvements over v1, particularly in code quality and features. Since January 2022, the software has processed around 2.3 billion images, compressing roughly 4.6 petabytes down to about 1.3 petabytes. Despite these successes, the growing number of issues and feature requests indicates that a new major version is needed. ### Background I started Caesium in 2009, right after high school, using C++ and Qt, which were my go-to technologies at the time. Over the years, as I became a Full Stack Web Developer, I integrated new technologies—like Rust for the core library—to keep the project alive while professionally focusing on completely different languages and technologies. Although web-based UIs and Electron were popular choices, I stuck with Qt because of familiarity and its multiplatform capabilities. ### Current Concerns #### My personal concerns about Qt: - Using C++ (which isn’t my strongest language) makes maintenance harder. - Qt Widgets can look outdated, especially on macOS, and often lag behind in adopting modern OS features like Windows 11 Dark Mode. - The auto-update system is clunky and relies on third-party tools (Sparkle/WinSparkle). - The build and release process is cumbersome, requiring the full Qt framework and complex packaging. #### Mainten

Comments (0)

No comments yet. Start the discussion.

Comment on this issue