{"slug": "love2d", "name": "Love2D", "category": "dev-libs", "category_name": "Libraries and frameworks", "description": "", "recommenders": 2, "commenters": 2, "warners": 0, "score": 1.723, "rising": -0.65, "first": "2026-03-09", "latest": "2026-03-10", "why": "anything with strong conventions and heavy LLM training data (Godot, Phaser, Love2D) will work better", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 2, "neutral": 0, "compare": 0, "warn": 0}, "spark": [0, 0, 0, 0, 2, 0, 0, 0, 0, 0, 0, 0], "listed": false, "loved": [], "caveat": "", "short_quote": "anything with strong conventions and heavy LLM training data (Godot, Phaser, Love2D) will work better", "icon": false, "domain": null, "github_repo": null, "official_url": "", "pricing": "", "aliases": ["Love2D"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 757128562, "item_id": 47320535, "url": "https://news.ycombinator.com/item?id=47320535", "by": "nachocoll", "date": "2026-03-10", "stance": "recommend", "quote": "anything with strong conventions and heavy LLM training data (Godot, Phaser, Love2D) will work better", "excerpt": "Interesting question that highlights a broader challenge with vibe coding in any domain: the choice of framework matters less than having clear architectural boundaries that guide what the AI generates. The comment about games needing play-testing and visualization is spot on. What's worth adding is that this is actually a general principle \u2014 vibe coding works best when you have explicit architecture upfront constrai", "context": "", "use_case": "vibe coding games", "switched_from": "", "story": "Ask HN: What game engine would you recommend for vibe coding?"}, {"id": 757091921, "item_id": 47318245, "url": "https://news.ycombinator.com/item?id=47318245", "by": "vunderba", "date": "2026-03-09", "stance": "recommend", "quote": "Love2D, Phaser, etc., would all be solid options.", "excerpt": "Just a heads up, it's highly unlikely you're going to be able to get away with pure vibe coding (as defined by Karpathy) for game dev. There's just no way around the fact that games need a lot of play-testing and visualization, all of which is difficult to capture discrete unit tests. Many of the games I've released using an agentic CLI (OpenCode) would have been absolutely impossible to vibe code. That being the cas", "context": "has released games", "use_case": "vibe-coded game development", "switched_from": "", "story": "Ask HN: What game engine would you recommend for vibe coding?"}]}], "caveats": [], "who": [{"by": "vunderba", "context": "has released games", "url": "https://news.ycombinator.com/item?id=47318245", "date": "2026-03-09"}], "tags": [], "use_cases": ["vibe coding games", "vibe-coded game development"], "compared": [{"slug": "phaser", "name": "Phaser", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=47318148", "title": "Ask HN: What game engine would you recommend for vibe coding?", "mentions": 2}], "sentiment_by_month": {"2025-11": {}, "2025-12": {}, "2026-01": {}, "2026-02": {}, "2026-03": {"recommend": 2}, "2026-04": {}, "2026-05": {}, "2026-06": {}, "2026-07": {}, "2026-08": {}, "2026-09": {}, "2026-10": {}}, "quotes": [{"id": 757128562, "item_id": 47320535, "url": "https://news.ycombinator.com/item?id=47320535", "by": "nachocoll", "date": "2026-03-10", "stance": "recommend", "quote": "anything with strong conventions and heavy LLM training data (Godot, Phaser, Love2D) will work better", "excerpt": "Interesting question that highlights a broader challenge with vibe coding in any domain: the choice of framework matters less than having clear architectural boundaries that guide what the AI generates. The comment about games needing play-testing and visualization is spot on. What's worth adding is that this is actually a general principle \u2014 vibe coding works best when you have explicit architecture upfront constrai", "context": "", "use_case": "vibe coding games", "switched_from": "", "story": "Ask HN: What game engine would you recommend for vibe coding?"}, {"id": 757091921, "item_id": 47318245, "url": "https://news.ycombinator.com/item?id=47318245", "by": "vunderba", "date": "2026-03-09", "stance": "recommend", "quote": "Love2D, Phaser, etc., would all be solid options.", "excerpt": "Just a heads up, it's highly unlikely you're going to be able to get away with pure vibe coding (as defined by Karpathy) for game dev. There's just no way around the fact that games need a lot of play-testing and visualization, all of which is difficult to capture discrete unit tests. Many of the games I've released using an agentic CLI (OpenCode) would have been absolutely impossible to vibe code. That being the cas", "context": "has released games", "use_case": "vibe-coded game development", "switched_from": "", "story": "Ask HN: What game engine would you recommend for vibe coding?"}]}