Tombstone Engine VS cppq

• Cross-Platform Support
  Tombstone Engine supports various platforms, including Windows, macOS, Linux, and game consoles, making it versatile for developers targeting multiple systems.
• Advanced Graphics
  The engine offers advanced rendering capabilities with support for features such as physically based rendering, volumetric effects, and dynamic shadows.
• C++ Based
  Users familiar with C++ can leverage their existing knowledge for efficient development and access to low-level system functions.
• Customizable Workflow
  Tombstone provides a flexible and customizable workflow, allowing developers to tailor tools and features to suit specific project needs.
• Efficient Performance
  The engine is designed for high performance, providing optimized code paths and efficient memory management suited for resource-intensive applications.

Possible disadvantages

• Limited User Community
  Compared to more popular engines, Tombstone has a smaller user base, which may result in fewer community resources and third-party support.
• Steeper Learning Curve
  Due to its C++ foundation and advanced features, beginners may find it challenging to learn and navigate compared to engines with more straightforward interfaces.
• Less Frequent Updates
  Tombstone Engine may not receive updates and new features as regularly as some of its competitors, potentially lagging behind in industry trends.
• Smaller Ecosystem
  With fewer plugins and extensions available, developers may need to implement custom solutions for specific needs.
• Licensing Costs
  For larger commercial projects, the costs associated with licensing could be higher compared to free or open-source alternatives.

• Lightweight C++ implementation
  cppq is written in modern C++ and designed to be a minimal, efficient task queue library, making it a good fit for performance-sensitive applications where the overhead of scripting language runtimes is undesirable.
• Redis-backed reliability
  Built on top of Redis as the message broker, cppq benefits from Redis's persistence, atomic operations, and wide adoption, giving the queue system durability and the ability to survive process restarts.
• Inspired by proven design (asynq)
  The library's architecture mirrors the popular Go asynq task queue, so it inherits a well-thought-out API design for task enqueueing, retries, and worker processing patterns that have already been validated in production systems.
• Native integration for C++ projects
  For teams already working in a C++ codebase, cppq allows adding background job processing without needing to introduce a separate service written in another language (like Go or Python), simplifying the technology stack.
• Open source and inspectable
  Being open source on GitHub, developers can review the source code, modify it for custom needs, and contribute improvements, which offers transparency not available with closed-source queueing solutions.

Possible disadvantages

• Limited maturity and battle-testing
  Compared to established task queue libraries like Sidekiq, Celery, or asynq itself, cppq is a newer and smaller project with less real-world production usage, which may translate into undiscovered bugs or edge cases.
• Smaller community and ecosystem
  Because it has far fewer users and contributors than mainstream task queue systems, finding community support, third-party tutorials, or pre-built integrations is more difficult.
• Documentation gaps
  As a smaller project, cppq may have less comprehensive documentation compared to major task queue frameworks, requiring developers to read source code directly to understand advanced features or edge-case behaviors.
• C++ build and dependency complexity
  Using cppq requires managing C++ build toolchains and dependencies (such as a Redis client library), which can be more cumbersome than installing a package via pip or npm in other ecosystems.
• Fewer built-in features and tooling
  cppq likely lacks the extensive ecosystem tooling of more mature queues, such as web-based monitoring dashboards, extensive metrics/observability integrations, or advanced scheduling features found in more established solutions.

No analysis of Tombstone Engine yet.

• making a commercial game without a game engine

  For c++ engines that arent unreal, I would check out c4 engine: https://c4engine.com/ Or Open 3D Engine: https://www.o3de.org/ I personally havnt used either, but next home/indie project I do targeting modern hardware I will most... Source: about 4 years ago

• Starting GameDev

  Foundations of Game Engine Development. There are only two books out in the series. But Eric Lengyel has really good math books. He has some older books but I think the math book in the Foundation series is excellent. He is also the... Source: over 5 years ago

Tracking cppq since Nov 2022.