{"slug": "phoenix-liveview", "name": "Phoenix LiveView", "category": "dev-libs", "category_name": "Libraries and frameworks", "description": "", "recommenders": 8, "commenters": 25, "warners": 2, "score": 9.341, "rising": -2.62, "first": "2025-12-02", "latest": "2026-08-12", "why": "I use Phoenix/LiveView for most of my stuff, and it works phenomenally well", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 9, "neutral": 14, "compare": 1, "warn": 2}, "spark": [0, 0, 2, 2, 0, 1, 0, 3, 1, 0, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "I use Phoenix/LiveView for most of my stuff, and it works phenomenally well", "kind": "", "icon": true, "domain": "hexdocs.pm", "github_repo": null, "official_url": "https://hexdocs.pm/phoenix_live_view/", "pricing": "", "aliases": ["Phoenix LiveView"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 784383632, "item_id": 49023977, "url": "https://news.ycombinator.com/item?id=49023977", "by": "bicx", "date": "2026-07-23", "version": null, "stance": "recommend", "quote": "there was the out-of-the-box live UI with Phoenix/LiveView that was really appealing", "excerpt": "It was the BEAM process/actor model that fit much better for managing agents, and then there was the out-of-the-box live UI with Phoenix/LiveView that was really appealing. I had started the project in Typescript/Node (because that's my company's primary stack choice), but it hit a plateau in reliably managing multiple independent long-lived agent processes (not really what Node is designed for). I could have used an", "context": "", "use_case": "Live server-rendered UI", "switched_from": "", "story": "Hologram works. Elixir runs in the browser"}, {"id": 776456929, "item_id": 48528558, "url": "https://news.ycombinator.com/item?id=48528558", "by": "paradox460", "date": "2026-06-14", "version": null, "stance": "recommend", "quote": "Super happy to have it incorporated into mainline live view", "excerpt": "Years ago I used surface ui's colocated css to great effect. Super happy to have it incorporated into mainline live view", "context": "", "use_case": "web development", "switched_from": "", "story": "Phoenix LiveView 1.2 Released"}, {"id": 776410241, "item_id": 48525640, "url": "https://news.ycombinator.com/item?id=48525640", "by": "lwouis", "date": "2026-06-14", "version": null, "stance": "recommend", "quote": "I like this familly of technologies. Having an SPA-type app that's mostly backend.", "excerpt": "I like this familly of technologies. Having an SPA-type app that's mostly backend. Recently i've redone my app website (https://alt-tab.app), and I implemented a minimal spa.js that has a similar approach. I find the end result blazing fast, simple to maintain / reason about, few moving pieces. I used Early Hints, compressed every single thing, inlined CSS, etc. I don't know how i could even make it faster. I recomme", "context": "", "use_case": "server-driven web apps", "switched_from": "", "story": "Phoenix LiveView 1.2 Released"}, {"id": 776398288, "item_id": 48524893, "url": "https://news.ycombinator.com/item?id=48524893", "by": "cpursley", "date": "2026-06-14", "version": null, "stance": "recommend", "quote": "LiveView is such a breath of fresh air", "excerpt": "LiveView is such a breath of fresh air, especially over the vibe coded NextJS rats nests that have become the norm (that need specialized hosting, are dog slow and require a ton of proprietary paid services bolted on like caching, background workers and even auth which Elixir and Phoenix provide out of the box). https://elixirisallyouneed.dev", "context": "", "use_case": "", "switched_from": "", "story": "Phoenix LiveView 1.2 Released"}, {"id": 762781408, "item_id": 47673838, "url": "https://news.ycombinator.com/item?id=47673838", "by": "rkangel", "date": "2026-04-07", "version": null, "stance": "recommend", "quote": "Phoenix LiveView (the inspiration) defaults to using WebSockets because it's much more efficent", "excerpt": "Keeps saying \"no websocket required\" like it's a good thing. The JS client (https://github.com/anzellai/sky/blob/main/docs/design/sky-live.md) seems to rely on long polling. Phoenix LiveView (the inspiration) defaults to using WebSockets because it's much more efficent, but falls back to Long polling if not available.", "context": "", "use_case": "", "switched_from": "", "story": "Sky \u2013 an Elm-inspired language that compiles to Go"}]}], "caveats": [{"label": "", "summary": "", "quotes": [{"id": 754307298, "item_id": 47144206, "url": "https://news.ycombinator.com/item?id=47144206", "by": "h4ch1", "date": "2026-02-24", "version": null, "stance": "warn", "quote": "when I have to do something moderately complicated I have to reach out for a darn js library", "excerpt": "I see this sort of maximalism a lot where people are just turned off js and say f it I'll use HTMX or LiveView or Alpine or whatever promises that you won't have to write js, and that's fine; as long as you're building generic dashboards and/or the same repetitive UI patterns. And even then you're basically writing JS just in a worse way. I use Liveview and Elixir for 2-3 home-lab related frontend services; but when ", "context": "", "use_case": "", "switched_from": "", "story": "How we rebuilt Next.js with AI in one week"}, {"id": 747059426, "item_id": 46691214, "url": "https://news.ycombinator.com/item?id=46691214", "by": "curtisblaine", "date": "2026-01-20", "version": null, "stance": "warn", "quote": "Livewire, Phoenix LiveView and all the others are a couple levels removed from the browser and you have to suffer the whole indirection chain when something goes wrong.", "excerpt": "No, you're right. Livewire, Phoenix LiveView and all the others are a couple levels removed from the browser and you have to suffer the whole indirection chain when something goes wrong. React is a good compromise - it still has indirection, but not so much, and it's much easier to use at scale than state managing and direct DOM manipulation.", "context": "", "use_case": "", "switched_from": "", "story": "The Overcomplexity of the Shadcn Radio Button"}]}], "who": [], "tags": [], "use_cases": ["web framework", "web app framework", "web dashboard", "project template", "live server-rendered ui", "hobby project"], "compared": [{"slug": "next-js", "name": "Next.js", "co": 5, "switched_from": 0, "switched_to": 0}, {"slug": "claude", "name": "Claude", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "clickhouse", "name": "ClickHouse", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "claude-code", "name": "Claude Code", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "codex", "name": "Codex", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "tailwind-css", "name": "Tailwind CSS", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "figma", "name": "Figma", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [{"id": 773875729, "item_id": 48367233, "url": "https://news.ycombinator.com/item?id=48367233", "by": "josecodea", "date": "2026-06-02", "version": null, "stance": "recommend", "quote": "shipped patches to Ecto, Phoenix LiveView, PostGraphile, and PowerSync", "excerpt": "Location: Costa Rica (GMT-6) Remote: Yes Willing to relocate: No Technologies: TypeScript, Elixir, Rust, Node.js, React, GraphQL, PostgreSQL, NixOS, Docker, AWS R\u00e9sum\u00e9/CV: contact for full CV, portfolio with OSS contributions at https://josecodea.com Email: look into my portfolio above Freelance developer and consultant. I contribute to the frameworks your stack runs on \u2014 shipped patches to Ecto, Phoenix LiveView, Po", "context": "", "use_case": "", "switched_from": "", "story": "Ask HN: Who wants to be hired? (June 2026)"}], "threads": [{"url": "https://news.ycombinator.com/item?id=48524293", "title": "Phoenix LiveView 1.2 Released", "mentions": 5}, {"url": "https://news.ycombinator.com/item?id=47142156", "title": "How we rebuilt Next.js with AI in one week", "mentions": 3}, {"url": "https://news.ycombinator.com/item?id=46527950", "title": "Creators of Tailwind laid off 75% of their engineering team", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=49275335", "title": "HTML over WebSockets: real-time SPAs with barely any JavaScript", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49233423", "title": "Ask HN: What are you working on? (August 2026)", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49161518", "title": "LLMs reward expertise", "mentions": 1}], "sentiment_by_month": {"2025-11": {}, "2025-12": {"neutral": 2}, "2026-01": {"recommend": 2, "warn": 1}, "2026-02": {"recommend": 2, "neutral": 1, "warn": 1}, "2026-03": {}, "2026-04": {"recommend": 1, "neutral": 2}, "2026-05": {"neutral": 1}, "2026-06": {"neutral": 3, "recommend": 3}, "2026-07": {"neutral": 2, "recommend": 1, "compare": 1}, "2026-08": {"neutral": 3}, "2026-09": {}, "2026-10": {}}, "versions": [], "version_unnamed": 0, "quotes": [{"id": 788518225, "item_id": 49282389, "url": "https://news.ycombinator.com/item?id=49282389", "by": "mcintyre1994", "date": "2026-08-12", "version": null, "stance": "neutral", "quote": "", "excerpt": "Something else that I think is interesting here is the new HTML streaming APIs in Chrome: https://developer.chrome.com/blog/declarative-partial-updates#out-of-order_streaming These mean that you can for example have a websocket serve just the new HTML, and then let native browser code figure out inserting it into the DOM, without any dependency. I\u2019m guessing things like LiveView could eventually migrate to this if it", "context": "", "use_case": "", "switched_from": "", "story": "HTML over WebSockets: real-time SPAs with barely any JavaScript"}, {"id": 787763105, "item_id": 49235194, "url": "https://news.ycombinator.com/item?id=49235194", "by": "shintoist", "date": "2026-08-09", "version": null, "stance": "neutral", "quote": "The backend is Elixir, with a Phoenix LiveView dashboard.", "excerpt": "I'm building an uptime monitoring service, in Elixir, called https://larm.dev. It's a tough field because for some reason people vibe coding apps think this is very easy to do, and there are new apps coming out pretty much every day. I'm still figuring out how to effectively stand out in the noise. I really enjoy working on the app though. The backend is Elixir, with a Phoenix LiveView dashboard. I've got a cluster o", "context": "", "use_case": "Web dashboard", "switched_from": "", "story": "Ask HN: What are you working on? (August 2026)"}, {"id": 786651521, "item_id": 49165720, "url": "https://news.ycombinator.com/item?id=49165720", "by": "RileyJames", "date": "2026-08-04", "version": null, "stance": "neutral", "quote": "We use Phoenix / liveview.", "excerpt": "I\u2019ve been curious on how to close this loop between engineering and design/product. We don\u2019t use react, which Claude design seems to trend towards. We use Phoenix / liveview. We have a shared design system, which keeps the visual elements in line. And then just prototype on design, collab, discuss and arrive at what we want to ship. And then engineering take over and rebuild via hand / claude code. But the tools aren", "context": "", "use_case": "web framework", "switched_from": "", "story": "LLMs reward expertise"}, {"id": 785846481, "item_id": 49115405, "url": "https://news.ycombinator.com/item?id=49115405", "by": "techpression", "date": "2026-07-30", "version": null, "stance": "neutral", "quote": "my Phoenix LiveView template project (which I use for starting new projects)", "excerpt": "I spent 30min with Opus 5 generating some CSS and components for my Phoenix LiveView template project (which I use for starting new projects). Then I spent around 5 hours parsing and cleaning up the output. I could of course not have done that, but since it's my spare time project I can care about the code and quality. I did get wins for sure (and I did save time), and I'm sure most people wouldn't even spend five mi", "context": "", "use_case": "project template", "switched_from": "", "story": "2x, not 10x: coding with LLMs in 2026"}, {"id": 785212226, "item_id": 49075764, "url": "https://news.ycombinator.com/item?id=49075764", "by": "gchamonlive", "date": "2026-07-27", "version": null, "stance": "compare", "quote": "Borrows from Elixir Phoenix's Liveview", "excerpt": "In the realm of Server-Side rendered pages and replacing bits of the DOM, I'd recommend https://pyview.rocks/. Borrows from Elixir Phoenix's Liveview and works really nice and patches are light to apply.", "context": "", "use_case": "", "switched_from": "", "story": "Removing React.js from the codebase and adapting Htmx for UI interactivity"}, {"id": 784383632, "item_id": 49023977, "url": "https://news.ycombinator.com/item?id=49023977", "by": "bicx", "date": "2026-07-23", "version": null, "stance": "recommend", "quote": "there was the out-of-the-box live UI with Phoenix/LiveView that was really appealing", "excerpt": "It was the BEAM process/actor model that fit much better for managing agents, and then there was the out-of-the-box live UI with Phoenix/LiveView that was really appealing. I had started the project in Typescript/Node (because that's my company's primary stack choice), but it hit a plateau in reliably managing multiple independent long-lived agent processes (not really what Node is designed for). I could have used an", "context": "", "use_case": "Live server-rendered UI", "switched_from": "", "story": "Hologram works. Elixir runs in the browser"}, {"id": 780591937, "item_id": 48786996, "url": "https://news.ycombinator.com/item?id=48786996", "by": "webpraktikos", "date": "2026-07-04", "version": null, "stance": "neutral", "quote": "Ash, LiveView, Tailwind CSS", "excerpt": "SEEKING WORK | Europe (and available in USA time zones) | Remote Product/UI Designer and Full-Stack Developer seeking work; I can work as a designer, developer, or both. Stack: Elixir, Phoenix, Ash, LiveView, Tailwind CSS, Rails, web servers, AI agents, research Design: typography, color, branding, UX, minimalism, photo editing, Figma, Affinity Photo My r\u00e9sum\u00e9, portfolio, and contact email: https://resume.webpraktiko", "context": "", "use_case": "", "switched_from": "", "story": "Ask HN: Freelancer? Seeking freelancer? (July 2026)"}, {"id": 776477696, "item_id": 48529856, "url": "https://news.ycombinator.com/item?id=48529856", "by": "moritzwarhier", "date": "2026-06-14", "version": null, "stance": "neutral", "quote": "I'll give this a try next time I feel like coding for a hobby.", "excerpt": "Thanks a lot! I'll give this a try next time I feel like coding for a hobby. I've tried exactly this \"project idea\" in a half-assed way some time ago with next.js, Postgres and Prisma before I was out of free-time-in-front-of-computer. Then abandoned it again it when I started coding for a living again. It was exactly the \"modest RT capabilities\" thing when I abandoned it. Because I started using Firebase (2023, Supa", "context": "", "use_case": "hobby project", "switched_from": "", "story": "Phoenix LiveView 1.2 Released"}, {"id": 776471056, "item_id": 48529441, "url": "https://news.ycombinator.com/item?id=48529441", "by": "IAmGraydon", "date": "2026-06-14", "version": null, "stance": "neutral", "quote": "Worth checking out... https://phoenix.new/", "excerpt": "Worth checking out... https://phoenix.new/", "context": "", "use_case": "", "switched_from": "", "story": "Phoenix LiveView 1.2 Released"}, {"id": 776456929, "item_id": 48528558, "url": "https://news.ycombinator.com/item?id=48528558", "by": "paradox460", "date": "2026-06-14", "version": null, "stance": "recommend", "quote": "Super happy to have it incorporated into mainline live view", "excerpt": "Years ago I used surface ui's colocated css to great effect. Super happy to have it incorporated into mainline live view", "context": "", "use_case": "web development", "switched_from": "", "story": "Phoenix LiveView 1.2 Released"}, {"id": 776410241, "item_id": 48525640, "url": "https://news.ycombinator.com/item?id=48525640", "by": "lwouis", "date": "2026-06-14", "version": null, "stance": "recommend", "quote": "I like this familly of technologies. Having an SPA-type app that's mostly backend.", "excerpt": "I like this familly of technologies. Having an SPA-type app that's mostly backend. Recently i've redone my app website (https://alt-tab.app), and I implemented a minimal spa.js that has a similar approach. I find the end result blazing fast, simple to maintain / reason about, few moving pieces. I used Early Hints, compressed every single thing, inlined CSS, etc. I don't know how i could even make it faster. I recomme", "context": "", "use_case": "server-driven web apps", "switched_from": "", "story": "Phoenix LiveView 1.2 Released"}, {"id": 776398288, "item_id": 48524893, "url": "https://news.ycombinator.com/item?id=48524893", "by": "cpursley", "date": "2026-06-14", "version": null, "stance": "recommend", "quote": "LiveView is such a breath of fresh air", "excerpt": "LiveView is such a breath of fresh air, especially over the vibe coded NextJS rats nests that have become the norm (that need specialized hosting, are dog slow and require a ton of proprietary paid services bolted on like caching, background workers and even auth which Elixir and Phoenix provide out of the box). https://elixirisallyouneed.dev", "context": "", "use_case": "", "switched_from": "", "story": "Phoenix LiveView 1.2 Released"}, {"id": 774245664, "item_id": 48390354, "url": "https://news.ycombinator.com/item?id=48390354", "by": "OkayPhysicist", "date": "2026-06-03", "version": null, "stance": "neutral", "quote": "There's a guide in the LiveView docs that walks you through the security model.", "excerpt": "[1] https://phoenix-live-view.hexdocs.pm/security-model.html There's a guide in the LiveView docs that walks you through the security model. To be clear, you need to always assume that the user can send you anything. That's a fact of any networked system: Clients need to be assumed to be completely under the control of an evil user, because at the end of the day it is impossible to know whether you're talking to the ", "context": "", "use_case": "", "switched_from": "", "story": "Elixir v1.20 released: now a gradually typed language"}, {"id": 769661168, "item_id": 48103823, "url": "https://news.ycombinator.com/item?id=48103823", "by": "malloryerik", "date": "2026-05-11", "version": null, "stance": "neutral", "quote": "I use it in LiveView all the time", "excerpt": "Well in a recent project I tried TypeScript thinking, OK, LLMs, huge training corpus! massive adoption! api for everything already set up! swim with the current! and I tried various frameworks and so on, but for me reasoning about things and being able to make systems that I could adapt and pivot it was honestly inferior compared to niche Elixir and Clojure. But it's not like I hate JS; I use it in LiveView all the t", "context": "", "use_case": "Server-rendered web UI", "switched_from": "", "story": "If AI Writes Your Code, Why Use Python?"}, {"id": 765953665, "item_id": 47872104, "url": "https://news.ycombinator.com/item?id=47872104", "by": "konovalov-nk", "date": "2026-04-22", "version": null, "stance": "neutral", "quote": "Pivot to Elixir Phoenix LiveView is real!", "excerpt": "Pivot to Elixir Phoenix LiveView is real! There's even agentic framework for this: https://jido.run/blog/jido-2-0-is-here If you think about it, OTP makes perfect sense for always-on, reachable agents. And agents want to reach any service, aka \"call\" it: remote services, web, DBs, messaging. I was planning to make something like this: https://github.com/konovalov-nk/synaptra/blob/main/docs/architecture/high-level-ove", "context": "", "use_case": "", "switched_from": "", "story": "All your agents are going async"}, {"id": 763971490, "item_id": 47748218, "url": "https://news.ycombinator.com/item?id=47748218", "by": "joladev", "date": "2026-04-12", "version": null, "stance": "neutral", "quote": "Phoenix LiveView dashboard", "excerpt": "https://larm.dev, an uptime monitoring service with a focus on reliability and reduction in false positives. I\u2019ve been building it for myself really but I figure it\u2019s worth sharing it with people in case someone else finds it useful too. It\u2019s also a lot of fun to work on. Phoenix LiveView dashboard, go probes running on 4 continents, connected to the backend using websocket tunnels. Clickhouse for reporting. Even did", "context": "", "use_case": "", "switched_from": "", "story": "Ask HN: What Are You Working On? (April 2026)"}, {"id": 762781408, "item_id": 47673838, "url": "https://news.ycombinator.com/item?id=47673838", "by": "rkangel", "date": "2026-04-07", "version": null, "stance": "recommend", "quote": "Phoenix LiveView (the inspiration) defaults to using WebSockets because it's much more efficent", "excerpt": "Keeps saying \"no websocket required\" like it's a good thing. The JS client (https://github.com/anzellai/sky/blob/main/docs/design/sky-live.md) seems to rely on long polling. Phoenix LiveView (the inspiration) defaults to using WebSockets because it's much more efficent, but falls back to Long polling if not available.", "context": "", "use_case": "", "switched_from": "", "story": "Sky \u2013 an Elm-inspired language that compiles to Go"}, {"id": 754307298, "item_id": 47144206, "url": "https://news.ycombinator.com/item?id=47144206", "by": "h4ch1", "date": "2026-02-24", "version": null, "stance": "warn", "quote": "when I have to do something moderately complicated I have to reach out for a darn js library", "excerpt": "I see this sort of maximalism a lot where people are just turned off js and say f it I'll use HTMX or LiveView or Alpine or whatever promises that you won't have to write js, and that's fine; as long as you're building generic dashboards and/or the same repetitive UI patterns. And even then you're basically writing JS just in a worse way. I use Liveview and Elixir for 2-3 home-lab related frontend services; but when ", "context": "", "use_case": "", "switched_from": "", "story": "How we rebuilt Next.js with AI in one week"}, {"id": 754302177, "item_id": 47143886, "url": "https://news.ycombinator.com/item?id=47143886", "by": "cpursley", "date": "2026-02-24", "version": null, "stance": "recommend", "quote": "", "excerpt": "see also: https://dashbit.co/blog/why-elixir-best-language-for-ai", "context": "", "use_case": "", "switched_from": "", "story": "How we rebuilt Next.js with AI in one week"}, {"id": 754302081, "item_id": 47143880, "url": "https://news.ycombinator.com/item?id=47143880", "by": "cpursley", "date": "2026-02-24", "version": null, "stance": "recommend", "quote": "migrate off of the Next.js and other JS SSR rats nets to Elixir and Phoenix LiveView", "excerpt": "Or just skip/migrate off of the Next.js and other JS SSR rats nets to Elixir and Phoenix LiveView - Claude and Codex are both very good with Elixir now: https://elixirisallyouneed.dev", "context": "", "use_case": "Web apps", "switched_from": "", "story": "How we rebuilt Next.js with AI in one week"}, {"id": 754006689, "item_id": 47125418, "url": "https://news.ycombinator.com/item?id=47125418", "by": "mendrugory", "date": "2026-02-23", "version": null, "stance": "neutral", "quote": "It\u2019s built entirely with Phoenix LiveView", "excerpt": "Hi, I built Naiply, a browser-based multiplayer platform for traditional Spanish card games like Brisca and Tute. It\u2019s built entirely with Phoenix LiveView \u2014 no SPA frontend, minimal JavaScript. All game state lives on the server. Some interesting challenges: Handling real-time turn synchronization Preventing race conditions in trick resolution Designing the bidding (puja) AI for Tute Subastado Managing latency witho", "context": "", "use_case": "Web app framework", "switched_from": "", "story": "Naiply \u2013 Real-time multiplayer Spanish card games built with Phoenix LiveView"}, {"id": 749522225, "item_id": 46845139, "url": "https://news.ycombinator.com/item?id=46845139", "by": "mirai75", "date": "2026-02-01", "version": null, "stance": "recommend", "quote": "LiveView made the real-time review dashboard easy", "excerpt": "I built this because AI kept messing up my document summaries. I was generating contract summaries, and the AI would constantly get things wrong, missing party names, wrong dates, invented clauses. I'd retry 3-4 times per document until it finally worked. Annoying and expensive (all those API calls add up). So I started writing validation rules to auto-reject the bad ones. But hardcoding rules meant redeploying every", "context": "", "use_case": "real-time review dashboard", "switched_from": "", "story": "Show HN: Check Your AI Human Review API for AI Generated Content"}, {"id": 747059426, "item_id": 46691214, "url": "https://news.ycombinator.com/item?id=46691214", "by": "curtisblaine", "date": "2026-01-20", "version": null, "stance": "warn", "quote": "Livewire, Phoenix LiveView and all the others are a couple levels removed from the browser and you have to suffer the whole indirection chain when something goes wrong.", "excerpt": "No, you're right. Livewire, Phoenix LiveView and all the others are a couple levels removed from the browser and you have to suffer the whole indirection chain when something goes wrong. React is a good compromise - it still has indirection, but not so much, and it's much easier to use at scale than state managing and direct DOM manipulation.", "context": "", "use_case": "", "switched_from": "", "story": "The Overcomplexity of the Shadcn Radio Button"}, {"id": 744456273, "item_id": 46528517, "url": "https://news.ycombinator.com/item?id=46528517", "by": "ZeroConcerns", "date": "2026-01-07", "version": null, "stance": "recommend", "quote": "", "excerpt": "I just had a more-detailed look, and I'm not sure where I'd find the pure-HTML stuff? From https://tailwindcss.com/plus/templates/pocket#pricing: \"Our website templates are built using Next.js, so all of the markup is written using React\" And the individual components that make up these templates don't seem to have pricing attached, nor non-React usage examples?", "context": "", "use_case": "Web framework", "switched_from": "", "story": "Creators of Tailwind laid off 75% of their engineering team"}, {"id": 744453696, "item_id": 46528356, "url": "https://news.ycombinator.com/item?id=46528356", "by": "freedomben", "date": "2026-01-07", "version": null, "stance": "recommend", "quote": "I use Phoenix/LiveView for most of my stuff, and it works phenomenally well", "excerpt": "It's not React only. It has pure/regular HTML, React, and Vue. I have mainly only used the pure HTML personally as I use Phoenix/LiveView for most of my stuff, and it works phenomenally well and is very copy/paste friendly. The UI/console they provide is also top notch. For others who do use React, the React stuff also worked well too for one project I did that was a SPA. It's well worth the money IMHO.", "context": "", "use_case": "Web app development", "switched_from": "", "story": "Creators of Tailwind laid off 75% of their engineering team"}, {"id": 740462577, "item_id": 46278911, "url": "https://news.ycombinator.com/item?id=46278911", "by": "cyan-indigo", "date": "2025-12-15", "version": null, "stance": "neutral", "quote": "Building this with Elixir/Phoenix LiveView.", "excerpt": "Working on Tenderlane: https://tenderlane.app/ Freight forwarders spend days or sometimes even weeks understanding and answering tenders without even knowing if they'll win the bid! With Tenderlane, they can now upload the entire tender spec and get an overview of what the customer wants in minutes instead. One key learning for this project is that I'm using Excel as the \"frontend\" as this is what our users are most ", "context": "", "use_case": "Web app framework", "switched_from": "", "story": "Ask HN: What Are You Working On? (December 2025)"}, {"id": 737979463, "item_id": 46123716, "url": "https://news.ycombinator.com/item?id=46123716", "by": "advisador", "date": "2025-12-02", "version": null, "stance": "neutral", "quote": "We are 100% Elixir and Phoenix LiveView on the backend", "excerpt": "Hey HN, I'm Ben from https://MisfitLabs.vc \u2014 small team that\u2019s been building healthcare software together for the last 12+ years. We built CodeBake because we were frustrated with the \"flexibility trap\" of traditional PM tools. After 30 years of using Jira, Asana, and Linear, I realized we were spending more time managing the tool than doing the work. We've been using CodeBake internally for most of 2025 (eating our ", "context": "", "use_case": "", "switched_from": "", "story": "Show HN: CodeBake \u2013 so that PM tasks aren't extra work"}]}