One Million Checkboxes VS cppq

• Simple and engaging concept
  One Million Checkboxes has an incredibly simple premise — a shared page with one million checkboxes that anyone can check or uncheck. This minimalist design makes it instantly accessible and intriguing, requiring no instructions or onboarding.
• Shared social experience
  All checkboxes are shared globally in real-time, meaning every visitor sees and interacts with the same set of checkboxes. This creates a unique communal experience where strangers collaborate (or compete) anonymously, fostering a sense of collective participation.
• Emergent creativity and community
  Despite its simplicity, the project inspired remarkable emergent behavior, including users encoding hidden images, messages, and art within the checkbox grid. Communities formed around coordinating efforts, showcasing human creativity even within extreme constraints.
• Interesting technical achievement
  Managing real-time state synchronization of one million checkboxes across potentially thousands of concurrent users is a non-trivial engineering challenge. The project serves as an impressive demonstration of web technologies, real-time databases, and scalable architecture.
• Nostalgia and internet art appeal
  The project evokes the spirit of classic internet experiments and web art projects, reminiscent of initiatives like Reddit's r/Place. It captures a playful, exploratory ethos of the early web that many users find refreshing and charming.

Possible disadvantages

• Limited long-term engagement
  Once the novelty wears off, there is very little reason to return. The experience lacks depth, progression, or meaningful goals, meaning most users will visit once or twice and never come back, leading to a short-lived lifespan.
• Vulnerability to bots and abuse
  The open and anonymous nature of the project makes it highly susceptible to automated scripts and bots that can rapidly check or uncheck massive numbers of boxes, undermining genuine human interaction and frustrating users trying to participate organically.
• No persistent individual impact
  Since anyone can undo anyone else's actions at any time, individual contributions feel impermanent and potentially meaningless. Users may feel frustrated that their effort to check boxes can be immediately reversed by others.
• Performance and scalability issues
  With high traffic, the site can experience lag, slow loading times, or synchronization delays. Rendering and tracking the state of one million checkboxes in a browser is resource-intensive and can strain both server infrastructure and client devices.
• Lack of accessibility and purpose
  The project offers no clear purpose, narrative, or outcome, which can feel pointless to many users. Additionally, a grid of one million tiny checkboxes presents significant accessibility challenges for users with visual impairments or those using assistive technologies.

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

• Encoding Jake Gyllenhaal into one million checkboxes

  Omcb is available but only in single player mode now: https://onemillioncheckboxes.com/. - Source: Hacker News / over 1 year ago

• One Million Chessboards

  Nope, just like his original site, one million checkboxes https://onemillioncheckboxes.com/. - Source: Hacker News / over 1 year ago

• Show HN: One Million and One Checkboxes. Running on Elixir and Mithril.js

  Hello! As soon as I saw eieio's https://onemillioncheckboxes.com/, I knew I wanted to try it out using Elixir. The original was created using Python and Redis (later Go and Redis) but this one is using just one Elixir server and HAProxy... - Source: Hacker News / about 2 years ago

View more

Tracking cppq since Nov 2022.