"The Deck" is an open-source, cross-platform card game engine built using Flutter. It provides a framework for developers to create and deploy their own digital card games across various platforms, including desktop, mobile, and web. The engine offers features such as networking for multiplayer gameplay, a customizable UI system for designing card visuals and game boards, and a scripting system using Lua for defining game logic and rules. This allows developers to focus on the unique aspects of their game design rather than the underlying technical implementation, accelerating development time and facilitating rapid prototyping. The project aims to be a versatile and accessible tool for both hobbyist and professional game developers.
Libmodulor is a TypeScript library designed for building cross-platform applications with a strong focus on developer experience and maintainability. It leverages a modular architecture, promoting code reuse and separation of concerns through features like dependency injection, a unified event bus, and lifecycle management. The library aims to simplify complex application logic by providing built-in solutions for common tasks such as state management, routing, and API interactions, allowing developers to focus on building features rather than boilerplate. While opinionated in its structure, libmodulor offers flexibility in choosing UI frameworks and targets web, desktop, and mobile platforms.
HN commenters generally express skepticism about the value proposition of libmodulor, particularly regarding its use of TypeScript and perceived over-engineering. Several question the necessity of such a library for simple projects, arguing that vanilla HTML, CSS, and JavaScript are sufficient. Some doubt the touted "multi-platform" capabilities, suggesting it's merely a web framework repackaged. Others criticize the project's apparent complexity and lack of clear advantages over established solutions like React Native or Flutter. The focus on server components and the use of RPC are also questioned, with commenters pointing to potential performance drawbacks. A few express interest in specific aspects, such as the server-driven UI approach and the developer experience, but overall sentiment leans towards cautious skepticism.
Summary of Comments ( 45 )
https://news.ycombinator.com/item?id=42983699
Hacker News users generally expressed positive interest in The Deck, praising its cross-platform compatibility via Flutter, open-source nature, and potential for customization. Some questioned the long-term viability of maintaining such a project, and the choice of Flutter for a game engine. Several commenters suggested alternative technologies or approaches, such as Godot, Bevy, or a web-based implementation. A few users shared their own experiences with game development in Flutter, offering both encouragement and cautionary tales about performance and complexity. There was a brief discussion around monetization strategies and the difficulty of standing out in the crowded mobile gaming market.
The Hacker News post titled "The Deck: An Open-Source Cross-Platform Multiplayer Card Game Engine in Flutter" sparked a discussion with several interesting comments.
Some users praised the project's potential and ambition. One commenter expressed excitement about the possibility of easily creating and sharing custom card games, envisioning a future where players could effortlessly design and distribute their own unique card game experiences. Another appreciated the cross-platform nature facilitated by Flutter, highlighting the broad reach this provides to potential players across different devices. The open-source nature of the project was also lauded, with a comment emphasizing the benefits of community involvement and the potential for collaborative development.
Technical aspects were also discussed. One user inquired about the networking solution employed by The Deck, specifically asking about the use of a client-server architecture or a peer-to-peer approach. This prompted a response from the project's creator, xajik, confirming the use of a client-server model. They further clarified that although currently centralized, the server could theoretically be self-hosted, offering more control and flexibility to users. Another technical point raised concerned the handling of game logic and validation. A user questioned whether these aspects were handled client-side or server-side. This sparked a discussion about the trade-offs between client-side validation (for responsiveness) and server-side validation (for security and cheat prevention), with suggestions for implementing both to achieve a balance.
Beyond technical details, there was a discussion about existing similar projects and potential integrations. One commenter mentioned existing tabletop simulator platforms like Tabletop Simulator and Cockatrice, suggesting potential interoperability or inspiration from these established platforms. Another user brought up the potential for integration with existing card game databases or APIs, specifically mentioning Scryfall, a popular Magic: The Gathering card database.
Finally, there was a brief discussion about licensing. One user asked for clarification on the licensing of assets used in the demo, highlighting the importance of clear licensing for open-source projects.
Overall, the comments reflect a generally positive reception of The Deck, with users acknowledging its potential while also engaging in constructive discussions about technical implementation, existing alternatives, and potential future developments.