Transitous VS cppq

• Free and Open Source
  Transitous is a fully free and open-source community project for public transit routing, meaning anyone can use, modify, and contribute to it without licensing fees or vendor lock-in.
• Privacy-Friendly
  Unlike commercial transit routing services from Google or Apple, Transitous does not track users or collect personal data, making it a strong choice for privacy-conscious individuals and organizations.
• Community-Driven and Decentralized
  Transitous is built and maintained by a community of volunteers and contributors, reducing dependence on any single corporation and fostering collaborative development across transit agencies and regions.
• Based on Open Data Standards
  Transitous leverages open data formats like GTFS and GTFS-RT, making it interoperable with existing transit data ecosystems and easy to integrate with other open-source tools and platforms.
• Pan-European and Growing Coverage
  The project aims to aggregate transit data across many regions, particularly in Europe, providing a unified routing service that spans multiple countries and transit agencies rather than being limited to a single city or provider.

Possible disadvantages

• Limited Coverage Compared to Commercial Alternatives
  Transitous does not yet have the global coverage that services like Google Maps or Apple Maps offer. Many regions, especially outside of Europe, may have incomplete or missing transit data.
• Dependent on Volunteer Effort
  As a community-driven project, development pace and reliability depend on volunteer contributions, which can be inconsistent and may lead to slower feature development or bug fixes compared to well-funded commercial products.
• Less Polished User Experience
  The user interface and overall experience may not be as refined or feature-rich as commercial transit apps, which invest heavily in design, accessibility, and user testing.
• Data Quality Variability
  Since Transitous relies on openly published transit data from various agencies, the quality, accuracy, and timeliness of that data can vary significantly between regions, potentially leading to inaccurate routing results.
• Limited Real-Time Information
  Real-time transit updates such as delays, cancellations, and service disruptions may not be as comprehensive or reliable as those provided by commercial platforms that have direct partnerships with transit agencies.

• 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.

• My phone detects going on a run as "someone snatching my phone and running off"

  Depending on where you live there is Transitous: https://transitous.org/ It's a FOSS public transport routing engine. In the options you can select what type and how much time you want to spend on the first and last "mile" (even... - Source: Hacker News / 3 months ago

Tracking cppq since Nov 2022.