I wrote a blog post that kind of summarizes a lot of this thread but also framework decisions made, etc.
GenericJam
GenericJam
GenericJam
manhvu
GenericJam
Define stable 
It’s growing by a lot but it pairs with native code. I haven’t changed much of what I’ve written so whatever you build is likely future compatible. I think most of the historical decisions were well thought out enough I haven’t had to revisit but we need more performance metrics I guess. I don’t see many breaking changes coming. Mostly just fleshing out the framework to be on parity with other platforms.
I suspect whatever code you already wrote you could roll the version forward and it would still work.
This release optimization code is already released in the latest batch if you go get latest mob_dev.
0
manhvu
Recently, I tried it, but the Mob app crashed, and I didn’t have much time to trace the issue, so I postponed creating a new app with Mob.
Oh, I have a question: why don’t you use the Rustler library to communicate with native code?
0
GenericJam
It wouldn’t give us anything apart from another layer. There’s no multithreading going on or anything in the NIF. I can’t really get away from using what is there already and if we used Rust it would be Rust using what’s already there and it would have to be marked unsafe anyway. There’s no way that I’m aware of for Rust to interact with the view tree on its own.
The crashing can happen because you have another BEAM app already running and they conflict on the port. Kill off any other apps made with mob so they don’t conflict. Sometimes epmd doesn’t start (nix users).
If you have issues you can report them to github and I’ll try to figure it out.
The app starting is the only point I’ve had crashes. If the app starts it doesn’t crash after that. So I need to make that more reliable. If you encounter issues please file them with a description of how / what / release / etc.
manhvu
Hi, I forked your repo and converted the C NIF to Rust (yes, I prefer working with Rust over C/C++). I’m also trying to apply a new declarative UI style like this:
Each screen:
screen :home_screen do
mount do
assign(:count, 0)
end
column padding: :space_md, gap: 8 do
text text: "Welcome to Dala!", text_size: :xl
text text: "Count: #{assigns.count}"
button text: "Increment", on_tap: :increment do
# Inline handler - generates handle_info clause automatically
assign(socket, :count, socket.assigns.count + 1)
end
button text: "Go to Detail", on_tap: :navigate do
push_screen(socket, MyApp.DetailScreen)
end
end
end
# You can still add a generic handle_info outside
handle_info(_message, socket), do: {:noreply, socket}
Home screen:
defmodule MyApp do
use Dala.App
screens do
screen :home_screen, module: MyApp.HomeScreen
screen :detail_screen, module: MyApp.DetailScreen
end
def on_start do
{:ok, _pid} = Dala.Screen.start_root(MyApp.HomeScreen)
:ok
end
end
I’ll come back and share more later.