{"slug": "pico-css", "name": "Pico CSS", "category": "dev-libs", "category_name": "Libraries and frameworks", "description": "", "recommenders": 2, "commenters": 4, "warners": 0, "score": 2.442, "rising": 0.67, "first": "2025-12-04", "latest": "2026-10-30", "why": "We also moved away from Tailwind \u2014 Pico CSS. It feels like a breath of fresh, modern CSS air.", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 2, "neutral": 2, "compare": 0, "warn": 0}, "spark": [0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 1], "listed": false, "loved": [], "caveat": "", "short_quote": "We also moved away from Tailwind \u2014 Pico CSS. It feels like a breath of fresh, modern CSS air.", "icon": false, "domain": "picocss.com", "github_repo": null, "official_url": "https://picocss.com", "pricing": "", "aliases": ["Pico CSS"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 804974400, "item_id": 50310900, "url": "https://news.ycombinator.com/item?id=50310900", "by": "valiant55", "date": "2026-10-30", "stance": "recommend", "quote": "it was praised for how intuitive and easy to use it was which was in large part due to how easy it was to build something beautiful with Pico", "excerpt": "This saddens me, thank you for Pico. As a backend engineer I used Pico for an internal tool used by dozens of people at my company and it was praised for how intuitive and easy to use it was which was in large part due to how easy it was to build something beautiful with Pico.", "context": "backend engineer", "use_case": "internal tool UI", "switched_from": "", "story": "Pico CSS is no longer maintained"}, {"id": 770599344, "item_id": 48162459, "url": "https://news.ycombinator.com/item?id=48162459", "by": "anydigital", "date": "2026-05-16", "stance": "recommend", "quote": "We also moved away from Tailwind \u2014 Pico CSS. It feels like a breath of fresh, modern CSS air.", "excerpt": "We also moved away from Tailwind \u2014 Pico CSS. It feels like a breath of fresh, modern CSS air. We actually loved it so much that we\u2019ve taken over maintenance of a fork, and just released our Pico successor candidate: https://blades.ninja/", "context": "team that took over a Pico fork", "use_case": "CSS framework", "switched_from": "Tailwind", "story": "Moving away from Tailwind, and learning to structure my CSS"}]}], "caveats": [], "who": [{"by": "valiant55", "context": "backend engineer", "url": "https://news.ycombinator.com/item?id=50310900", "date": "2026-10-30"}, {"by": "anydigital", "context": "team that took over a Pico fork", "url": "https://news.ycombinator.com/item?id=48162459", "date": "2026-05-16"}], "tags": [], "use_cases": ["css framework", "internal tool ui", "custom css generation"], "compared": [{"slug": "blades", "name": "Blades", "co": 4, "switched_from": 0, "switched_to": 1}, {"slug": "tailwind-css", "name": "Tailwind CSS", "co": 1, "switched_from": 1, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=50298964", "title": "Pico CSS is no longer maintained", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=48158400", "title": "Moving away from Tailwind, and learning to structure my CSS", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46153116", "title": "Django 6", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {"neutral": 1}, "2026-01": {}, "2026-02": {}, "2026-03": {}, "2026-04": {}, "2026-05": {"recommend": 1}, "2026-06": {}, "2026-07": {}, "2026-08": {}, "2026-09": {}, "2026-10": {"neutral": 1, "recommend": 1}}, "quotes": [{"id": 804974400, "item_id": 50310900, "url": "https://news.ycombinator.com/item?id=50310900", "by": "valiant55", "date": "2026-10-30", "stance": "recommend", "quote": "it was praised for how intuitive and easy to use it was which was in large part due to how easy it was to build something beautiful with Pico", "excerpt": "This saddens me, thank you for Pico. As a backend engineer I used Pico for an internal tool used by dozens of people at my company and it was praised for how intuitive and easy to use it was which was in large part due to how easy it was to build something beautiful with Pico.", "context": "backend engineer", "use_case": "internal tool UI", "switched_from": "", "story": "Pico CSS is no longer maintained"}, {"id": 804788224, "item_id": 50299264, "url": "https://news.ycombinator.com/item?id=50299264", "by": "psadri", "date": "2026-10-30", "stance": "neutral", "quote": "Hmm. I use pico.", "excerpt": "Hmm. I use pico. They could use an agent to modernize it!", "context": "", "use_case": "CSS framework", "switched_from": "", "story": "Pico CSS is no longer maintained"}, {"id": 770599344, "item_id": 48162459, "url": "https://news.ycombinator.com/item?id=48162459", "by": "anydigital", "date": "2026-05-16", "stance": "recommend", "quote": "We also moved away from Tailwind \u2014 Pico CSS. It feels like a breath of fresh, modern CSS air.", "excerpt": "We also moved away from Tailwind \u2014 Pico CSS. It feels like a breath of fresh, modern CSS air. We actually loved it so much that we\u2019ve taken over maintenance of a fork, and just released our Pico successor candidate: https://blades.ninja/", "context": "team that took over a Pico fork", "use_case": "CSS framework", "switched_from": "Tailwind", "story": "Moving away from Tailwind, and learning to structure my CSS"}, {"id": 738480020, "item_id": 46155001, "url": "https://news.ycombinator.com/item?id=46155001", "by": "HiPhish", "date": "2025-12-04", "stance": "neutral", "quote": "we also generate the custom CSS from Pico[1]", "excerpt": "That's just for the HTML content though. What if you want to add some non-trivial Javascript or generated CSS? Or maybe you want to integrate a frontend tool like Storybook[0] even if your HTML is rendered server-side? Maybe add some tests for your frontend code? There is much more between raw hand-rolled HTML/CSS/JS and a full-blown SPA. At my day job we use Django with HTMX and Alpine, but we also generate the cust", "context": "", "use_case": "custom CSS generation", "switched_from": "", "story": "Django 6"}]}