Hologram Works. Sponsor What Comes Next

hckrnws

Hologram Works. Sponsor What Comes Next

(hologram.page)

by lawik

bicx
132d
We're in an interesting time where my framework/stack choice is now much less dictated by existing engineer expertise and more about fundamental capabilities in the framework and stack themselves.
I ended up building an agent orchestrator in Elixir and Phoenix, not because I love working in Elixir/Phoenix (I do, but I just don't write code by hand anymore), but because the BEAM/OTP capabilities genuinely worked more reliably and elegantly to solve our orchestrator challenges.
I see projects like Hologram potentially showing up as the right tool for the job much more often. The barrier to picking up a new tool/framework/stack is so low these days with agentic development, and it comes down to speed, capability, and reliability.
Ironically, I don't think agents are going to suggest anything like Hologram on their own, so it is still down to human engineers to push it into common use. That might be the biggest barrier to adoption: overcoming obscurity so that LLMs suggest it as a solution.
1. turtlebits
  52d
  I'm on the opposite side of this. With LLMs, I no longer feel the need to use crazy frontend frameworks and abstractions. I'm back to building static HTML with minimal JS (and ideally no build step). Instead of using Tauri/Wails for GUI apps, I just use Swift.
  I no longer try to build everything around my choice of language.
  1. grimgrin
    32d
    right, you're using the tool for the job. author was reaching for reliability, re: OTP/beam. now we don't know if they actually needed it, but, you're saying the same thing to me
    bicx
    01d
    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 even more boring tech like Go with more robust process management, but Elixir and Phoenix also came with a lot out of the box. It's no surprise that OpenAI's reference project for agent orchestration (https://github.com/openai/symphony) is also written in Elixir.
2. christina97
  12d
  My framework/stack choice on the other hand is now much more dictated by the quantity and depth of existing literature on the internet about that stack.
  1. hnedeotes
    02d
    does that really help? I have had llms fumble pretty simple stuff in html/css and probably that's what there's more information on the internet, while with simple packages/languages with clear cut semantics it seems to be much better, even if off some samples pasted into context.
    [edit] the case was simply, write me an html landing page, with a navbar, a content area and a footer, make sure the content on each area doesn't extend beyond 1200px wide , make each container centered (paraphrasing)
3. nightfuryg
  22d
  Did you use something like Jido or roll your own out of curiosity?
  1. bartblast
    02d
    There's Jido Assembly that uses Hologram under the hood: https://github.com/agentjido/jido_assembly
4. Towaway69
  02d
  That sounds like a case of SEO - Suggestion Engine Optimisation. Is that a thing yet? Sounds like the next AI Unicorn.
5. bartblast
  02d
  [dead]
hnedeotes
03d
I would be really excited to see this moving forward - saying as someone who uses Phoenix regularly (and likes it for the most part) and has used react, vuejs, and so on - even at the stage it's at is already a very promising DX with what looks like a very reasonable roadmap and clear intent.
Having elixir apps that can work seamlessly local-first would be amazing and take care of one of the only areas where phoenix can't completely cover out of the box, making things that today take a lot of glue code, and error prone, a matter of a few declarations.
tomhow
02d
Release discussions:
Hologram v0.7.0: Milestone release for Elixir-to-JavaScript porting initiative - https://news.ycombinator.com/item?id=46982943 - Feb 2026 (29 comments)
Hologram v0.5.0 - https://news.ycombinator.com/item?id=44690158 - July 2025 (50 comments)
Hologram: A full-stack isomorphic Elixir web framework - https://news.ycombinator.com/item?id=42710376 - Jan 2025 (37 comments)
jamauro
42d
Hologram is a joy to work with. Local first support will take it to the next level. Bart is cooking.
1. bartblast
  32d
  Local-first is simmering! :)
troupo
42d
The only thing that's stopping me from trying this currently is file uploads.
Otherwise it's a really cool project
1. jamauro
  32d
  It can handle file uploads. What issue are you running into?
taatparya
42d
Would be great for reviving LiveView Native. Perhaps Dockyard / Brian Carderella might be interested.
1. minib
  22d
  Not exactly that, but check out Mob: https://github.com/GenericJam/mob
  It's an Elixir framework for cross-platform mobile apps — has a LiveView-like API and a React Native-like native UI layer. I'm working on a couple of apps with it, and so far it's awesome!
pixel_popping
02d
I feel it would be better promoted if it included more images in the doc.
hexasquid
32d
The things people do to not use web technologies.
1. bartblast
  02d
  Hologram author here. It's the opposite, really - the whole thing is built on web technologies. The compiler builds an IR from your Elixir code, analyzes the call graph, and spits out per-page JavaScript bundles. In the browser it's regular JavaScript patching the real DOM, and transport is plain HTTP (POST + Server-Sent Events) - no canvas rendering, no WASM. It uses Web APIs directly, and the goal is to make the whole Web API surface available from Elixir. The only thing being swapped out is the authoring language, same as with TypeScript or Elm.