Elixir Pack: Embed a complete Elixir OTP runtime directly in your iOS app
1–4 of 4 posts
Re: Elixir Pack: Embed a complete Elixir OTP runtime directly in your iOS app
#2This is another extraction from the project that I discussed in this HN thread: https://news.ycombinator.com/item?id=44651539#44652356
tldr; we're building a headless browser in Elixir that will embed on device, communicate to the native 1st class rendering engine (i.e. SwiftUI, Jetpack Compose, WinUI3, etc...) via disterl, and allow for web-like ergonomics to build truly native SSR applications.
The README for Elixir Pack is a bit focused on the LiveView Native project but that documentation will soon be updated to remove mention of it.
Re: Elixir Pack: Embed a complete Elixir OTP runtime directly in your iOS app
#3This is another extraction from the project that I discussed in this HN thread: https://news.ycombinator.com/item?id=44651539#44652356 tldr; we're building a headless browser in Elixir that will embed on device, communicate to the native 1st class rendering engine (i.e. SwiftUI, Jetpack Compose, WinUI3, etc...) via disterl, and allow for web-like ergonomics to build truly native SSR applications. The README for Elixi…
Can you explain a bit of the workflow you expect for offline support?
Like would I have one set of LiveViews that run on device and a database wrapper that handles online vs offline queries? Do you envision all view code running on device then?
Either way, super cool to see!
Re: Elixir Pack: Embed a complete Elixir OTP runtime directly in your iOS app
#4This is another extraction from the project that I discussed in this HN thread: https://news.ycombinator.com/item?id=44651539#44652356 tldr; we're building a headless browser in Elixir that will embed on device, communicate to the native 1st class rendering engine (i.e. SwiftUI, Jetpack Compose, WinUI3, etc...) via disterl, and allow for web-like ergonomics to build truly native SSR applications. The README for Elixi…
I don't understand why this headless browser should be in Elixir and why it should communicate via disterl/BERT? Although disterl is native to Erlang/OTP/BEAM VM, it should be implemented in native rendering engines.
Don't get me wrong, I prefer writing in Elixir to JS/TS or native (Swift/Kotlin etc.)
> to build truly native SSR applications
Why do you still call it SSR if it is rendered on the client device?
Is there a long-form article about this project, preferably with visuals/diagrams?