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.
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.
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.
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)
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.
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!
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.
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.
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.
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)
Did you use something like Jido or roll your own out of curiosity?
Also interested in learning more.
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.
Hologram is a joy to work with. Local first support will take it to the next level. Bart is cooking.
I feel it would be better promoted if it included more images in the doc.
Would be great for reviving LiveView Native. Perhaps Dockyard / Brian Carderella might be interested.
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!
Literally just had Mob surface from a chatgpt (or Claude I forget) session and am really intrigued.
Neat, didn't realize this existed. I'm experimenting the Rust Crux (https://github.com/redbadger/crux) for this - uses the Elm pattern.