#leptos — Public Fediverse posts

So I have read some more about the whole #dioxus vs #tauri plus #leptos plus #axum for a #rust #rustlang #desktop app.

From what I read by now, I would say that I will try the tauri route next. I would still prefer if Dioxus would just work, but what makes me wary about whether Dioxus would be a sustainable choice is that there's a lot of issues in the Dioxus repository that do not even have a reply by a maintainer. My own issues (which are relatively young!) have only little interaction. I get that this is an open source project and maintainer overload and so on, sure. But there's also something about Dioxus being funded? So there are full-time devs (plural!) working on it? What can I say? This makes me wary.

Going down that tauri route would mean that I would need to build the whole thing myself. That could work, but is more than I would have liked to do. I want to develop my app functionality, not set up a GUI development environment.

I could also go for a TUI first, but tbh, I would rather like to have a GUI first, with a clean API that I can then reuse to build a TUI on top of it. Not sure why, the other way around would probably work as well 🤔.

Either way, I would then try leptos as framework for the app, because it looks rather good from what I can read from its documentation, and I can use axum in the backend, which I think fits my needs as well. (Btw developing this with ratatui with a axum backend would also be possible, but that's not the "native way" for a ratatui app, but much more for a leptos app as I understand it, so I expect less headaches here).

I hope I can get a MVP fast, so I can get back to developing my core application stuff, because there's sooo much missing still.

So I have read some more about the whole #dioxus vs #tauri plus #leptos plus #axum for a #rust #rustlang #desktop app.

From what I read by now, I would say that I will try the tauri route next. I would still prefer if Dioxus would just work, but what makes me wary about whether Dioxus would be a sustainable choice is that there's a lot of issues in the Dioxus repository that do not even have a reply by a maintainer. My own issues (which are relatively young!) have only little interaction. I get that this is an open source project and maintainer overload and so on, sure. But there's also something about Dioxus being funded? So there are full-time devs (plural!) working on it? What can I say? This makes me wary.

Going down that tauri route would mean that I would need to build the whole thing myself. That could work, but is more than I would have liked to do. I want to develop my app functionality, not set up a GUI development environment.

I could also go for a TUI first, but tbh, I would rather like to have a GUI first, with a clean API that I can then reuse to build a TUI on top of it. Not sure why, the other way around would probably work as well 🤔.

Either way, I would then try leptos as framework for the app, because it looks rather good from what I can read from its documentation, and I can use axum in the backend, which I think fits my needs as well. (Btw developing this with ratatui with a axum backend would also be possible, but that's not the "native way" for a ratatui app, but much more for a leptos app as I understand it, so I expect less headaches here).

I hope I can get a MVP fast, so I can get back to developing my core application stuff, because there's sooo much missing still.

So I have read some more about the whole #dioxus vs #tauri plus #leptos plus #axum for a #rust #rustlang #desktop app.

From what I read by now, I would say that I will try the tauri route next. I would still prefer if Dioxus would just work, but what makes me wary about whether Dioxus would be a sustainable choice is that there's a lot of issues in the Dioxus repository that do not even have a reply by a maintainer. My own issues (which are relatively young!) have only little interaction. I get that this is an open source project and maintainer overload and so on, sure. But there's also something about Dioxus being funded? So there are full-time devs (plural!) working on it? What can I say? This makes me wary.

Going down that tauri route would mean that I would need to build the whole thing myself. That could work, but is more than I would have liked to do. I want to develop my app functionality, not set up a GUI development environment.

I could also go for a TUI first, but tbh, I would rather like to have a GUI first, with a clean API that I can then reuse to build a TUI on top of it. Not sure why, the other way around would probably work as well 🤔.

Either way, I would then try leptos as framework for the app, because it looks rather good from what I can read from its documentation, and I can use axum in the backend, which I think fits my needs as well. (Btw developing this with ratatui with a axum backend would also be possible, but that's not the "native way" for a ratatui app, but much more for a leptos app as I understand it, so I expect less headaches here).

I hope I can get a MVP fast, so I can get back to developing my core application stuff, because there's sooo much missing still.

So I have read some more about the whole #dioxus vs #tauri plus #leptos plus #axum for a #rust #rustlang #desktop app.

From what I read by now, I would say that I will try the tauri route next. I would still prefer if Dioxus would just work, but what makes me wary about whether Dioxus would be a sustainable choice is that there's a lot of issues in the Dioxus repository that do not even have a reply by a maintainer. My own issues (which are relatively young!) have only little interaction. I get that this is an open source project and maintainer overload and so on, sure. But there's also something about Dioxus being funded? So there are full-time devs (plural!) working on it? What can I say? This makes me wary.

Going down that tauri route would mean that I would need to build the whole thing myself. That could work, but is more than I would have liked to do. I want to develop my app functionality, not set up a GUI development environment.

I could also go for a TUI first, but tbh, I would rather like to have a GUI first, with a clean API that I can then reuse to build a TUI on top of it. Not sure why, the other way around would probably work as well 🤔.

Either way, I would then try leptos as framework for the app, because it looks rather good from what I can read from its documentation, and I can use axum in the backend, which I think fits my needs as well. (Btw developing this with ratatui with a axum backend would also be possible, but that's not the "native way" for a ratatui app, but much more for a leptos app as I understand it, so I expect less headaches here).

I hope I can get a MVP fast, so I can get back to developing my core application stuff, because there's sooo much missing still.

So I have read some more about the whole #dioxus vs #tauri plus #leptos plus #axum for a #rust #rustlang #desktop app.

From what I read by now, I would say that I will try the tauri route next. I would still prefer if Dioxus would just work, but what makes me wary about whether Dioxus would be a sustainable choice is that there's a lot of issues in the Dioxus repository that do not even have a reply by a maintainer. My own issues (which are relatively young!) have only little interaction. I get that this is an open source project and maintainer overload and so on, sure. But there's also something about Dioxus being funded? So there are full-time devs (plural!) working on it? What can I say? This makes me wary.

Going down that tauri route would mean that I would need to build the whole thing myself. That could work, but is more than I would have liked to do. I want to develop my app functionality, not set up a GUI development environment.

I could also go for a TUI first, but tbh, I would rather like to have a GUI first, with a clean API that I can then reuse to build a TUI on top of it. Not sure why, the other way around would probably work as well 🤔.

Either way, I would then try leptos as framework for the app, because it looks rather good from what I can read from its documentation, and I can use axum in the backend, which I think fits my needs as well. (Btw developing this with ratatui with a axum backend would also be possible, but that's not the "native way" for a ratatui app, but much more for a leptos app as I understand it, so I expect less headaches here).

I hope I can get a MVP fast, so I can get back to developing my core application stuff, because there's sooo much missing still.

@dcz @slint OK, something I tries in #Leptos.

You need to follow some examples or implement something based on `GridLayout`. Oliver gave some hints in https://github.com/slint-ui/slint/discussions/5147

@dcz @slint OK, something I tries in #Leptos.

You need to follow some examples or implement something based on `GridLayout`. Oliver gave some hints in https://github.com/slint-ui/slint/discussions/5147

@dcz @slint OK, something I tries in #Leptos.

You need to follow some examples or implement something based on `GridLayout`. Oliver gave some hints in https://github.com/slint-ui/slint/discussions/5147

@dcz @slint OK, something I tries in #Leptos.

You need to follow some examples or implement something based on `GridLayout`. Oliver gave some hints in https://github.com/slint-ui/slint/discussions/5147

@dcz @slint OK, something I tries in #Leptos.

You need to follow some examples or implement something based on `GridLayout`. Oliver gave some hints in https://github.com/slint-ui/slint/discussions/5147

For clarity, #money I don't have as I still haven't found #job. This #Leptos app is supposed to be a tool to manage job #applications. Potentially someone in #FediHire would be interested in one. (#Rust) 2/2

For clarity, #money I don't have as I still haven't found #job. This #Leptos app is supposed to be a tool to manage job #applications. Potentially someone in #FediHire would be interested in one. (#Rust) 2/2

For clarity, #money I don't have as I still haven't found #job. This #Leptos app is supposed to be a tool to manage job #applications. Potentially someone in #FediHire would be interested in one. (#Rust) 2/2

I gave #agentic #vibe coding a go today.🤔

Free Copilot models are useless, beyond repair...

Had chance to run GPT 5.2 Extended... once (burnt my free credits with one prompt). I got 70% of what I wanted in #Leptos, but it created doubtful code I need to understand. It needed good several minutes to generate. I fixed one slop already - unnecessary nested complication in view implementation, it looks there's more to look after.

I'd like to check #Claude #Opus, but I don't want burn #money. 1/2

I gave #agentic #vibe coding a go today.🤔

Free Copilot models are useless, beyond repair...

Had chance to run GPT 5.2 Extended... once (burnt my free credits with one prompt). I got 70% of what I wanted in #Leptos, but it created doubtful code I need to understand. It needed good several minutes to generate. I fixed one slop already - unnecessary nested complication in view implementation, it looks there's more to look after.

I'd like to check #Claude #Opus, but I don't want burn #money. 1/2

I gave #agentic #vibe coding a go today.🤔

Free Copilot models are useless, beyond repair...

Had chance to run GPT 5.2 Extended... once (burnt my free credits with one prompt). I got 70% of what I wanted in #Leptos, but it created doubtful code I need to understand. It needed good several minutes to generate. I fixed one slop already - unnecessary nested complication in view implementation, it looks there's more to look after.

I'd like to check #Claude #Opus, but I don't want burn #money. 1/2

Decoupling from Linktree. Cultivating my own atelier for signal convergence and #Leptos prototypes, forged in #Rust.

Decoupling from Linktree. Cultivating my own atelier for signal convergence and #Leptos prototypes, forged in #Rust.

Decoupling from Linktree. Cultivating my own atelier for signal convergence and #Leptos prototypes, forged in #Rust.

Decoupling from Linktree. Cultivating my own atelier for signal convergence and #Leptos prototypes, forged in #Rust.

Decoupling from Linktree. Cultivating my own atelier for signal convergence and #Leptos prototypes, forged in #Rust.

There's #ratatui #dioxus #yew #leptos and so on and so forth...

You know what I wonder? Why are there no libraries for full views for any of those? Like... A complete thing I can import to have a view to analyze the logging of my app (there's only one for Ratatui, but I haven't found something like that for the others).

Or a View for analyzing traces, something like Tracy, that I can import and embed in my app.

Or a view that I can embed to have a full WYSIWYG editor?

For all of these, there are only some component libraries for dropdown elements or whatever, but nothing that gives me a whole view of something.

#rust #rustlang

There's #ratatui #dioxus #yew #leptos and so on and so forth...

You know what I wonder? Why are there no libraries for full views for any of those? Like... A complete thing I can import to have a view to analyze the logging of my app (there's only one for Ratatui, but I haven't found something like that for the others).

Or a View for analyzing traces, something like Tracy, that I can import and embed in my app.

Or a view that I can embed to have a full WYSIWYG editor?

For all of these, there are only some component libraries for dropdown elements or whatever, but nothing that gives me a whole view of something.

#rust #rustlang

There's #ratatui #dioxus #yew #leptos and so on and so forth...

You know what I wonder? Why are there no libraries for full views for any of those? Like... A complete thing I can import to have a view to analyze the logging of my app (there's only one for Ratatui, but I haven't found something like that for the others).

Or a View for analyzing traces, something like Tracy, that I can import and embed in my app.

Or a view that I can embed to have a full WYSIWYG editor?

For all of these, there are only some component libraries for dropdown elements or whatever, but nothing that gives me a whole view of something.

#rust #rustlang

There's #ratatui #dioxus #yew #leptos and so on and so forth...

You know what I wonder? Why are there no libraries for full views for any of those? Like... A complete thing I can import to have a view to analyze the logging of my app (there's only one for Ratatui, but I haven't found something like that for the others).

Or a View for analyzing traces, something like Tracy, that I can import and embed in my app.

Or a view that I can embed to have a full WYSIWYG editor?

For all of these, there are only some component libraries for dropdown elements or whatever, but nothing that gives me a whole view of something.

#rust #rustlang

There's #ratatui #dioxus #yew #leptos and so on and so forth...

You know what I wonder? Why are there no libraries for full views for any of those? Like... A complete thing I can import to have a view to analyze the logging of my app (there's only one for Ratatui, but I haven't found something like that for the others).

Or a View for analyzing traces, something like Tracy, that I can import and embed in my app.

Or a view that I can embed to have a full WYSIWYG editor?

For all of these, there are only some component libraries for dropdown elements or whatever, but nothing that gives me a whole view of something.

#rust #rustlang

🦀🌱 We continue to work on ArkSync and the grid collision detection.

We're building an environmental monitoring and regulation system.

https://www.twitch.tv/indiedevcasts

#indiedev #rustlang #tauri #leptos

🦀🌱 We continue to work on ArkSync and the grid collision detection.

We're building an environmental monitoring and regulation system.

https://www.twitch.tv/indiedevcasts

#indiedev #rustlang #tauri #leptos

🦀🌱 We continue to work on ArkSync and the grid collision detection.

We're building an environmental monitoring and regulation system.

https://www.twitch.tv/indiedevcasts

#indiedev #rustlang #tauri #leptos

@stu hey thanks! It's actually statically generated into HTML! But I was experimenting with rust+leptos as a way to learn rust 😅. Definitely nice to have small pure html+css sites for most things though.

#rustlang #leptos

@stu hey thanks! It's actually statically generated into HTML! But I was experimenting with rust+leptos as a way to learn rust 😅. Definitely nice to have small pure html+css sites for most things though.

#rustlang #leptos

@stu hey thanks! It's actually statically generated into HTML! But I was experimenting with rust+leptos as a way to learn rust 😅. Definitely nice to have small pure html+css sites for most things though.

#rustlang #leptos

@stu hey thanks! It's actually statically generated into HTML! But I was experimenting with rust+leptos as a way to learn rust 😅. Definitely nice to have small pure html+css sites for most things though.

#rustlang #leptos

Overkill as a service: лендинг на Rust вместо конструктора

Tilda раздражала, JS пугал, а Rust манил… В итоге я переписал лендинг на Rust + Leptos - просто потому что «а почему бы и нет?». Под катом: немного боли, пара побед, сравнение с конструктором и вывод о том, что заниматься фигнёй иногда очень полезно.

https://habr.com/ru/articles/968782/

#rust #leptos #tilda

Overkill as a service: лендинг на Rust вместо конструктора

Tilda раздражала, JS пугал, а Rust манил… В итоге я переписал лендинг на Rust + Leptos - просто потому что «а почему бы и нет?». Под катом: немного боли, пара побед, сравнение с конструктором и вывод о том, что заниматься фигнёй иногда очень полезно.

https://habr.com/ru/articles/968782/

#rust #leptos #tilda

Overkill as a service: лендинг на Rust вместо конструктора

Tilda раздражала, JS пугал, а Rust манил… В итоге я переписал лендинг на Rust + Leptos - просто потому что «а почему бы и нет?». Под катом: немного боли, пара побед, сравнение с конструктором и вывод о том, что заниматься фигнёй иногда очень полезно.

https://habr.com/ru/articles/968782/

#rust #leptos #tilda

Overkill as a service: лендинг на Rust вместо конструктора

Tilda раздражала, JS пугал, а Rust манил… В итоге я переписал лендинг на Rust + Leptos - просто потому что «а почему бы и нет?». Под катом: немного боли, пара побед, сравнение с конструктором и вывод о том, что заниматься фигнёй иногда очень полезно.

https://habr.com/ru/articles/968782/

#rust #leptos #tilda

My @protonprivacy colleguages in #Barcelona are organizing another #BcnRust meetup: https://www.meetup.com/bcnrust/events/311787736/. This time about:

*- *Trade-offs in IoT Applications by Grzegorz Krasoń

-* *Going Full Stack in Rust with Leptos by @martsec

#rust #rustlang #iot #baremetal #leptos #wasm

My @protonprivacy colleguages in #Barcelona are organizing another #BcnRust meetup: https://www.meetup.com/bcnrust/events/311787736/. This time about:

*- *Trade-offs in IoT Applications by Grzegorz Krasoń

-* *Going Full Stack in Rust with Leptos by @martsec

#rust #rustlang #iot #baremetal #leptos #wasm

My @protonprivacy colleguages in #Barcelona are organizing another #BcnRust meetup: https://www.meetup.com/bcnrust/events/311787736/. This time about:

*- *Trade-offs in IoT Applications by Grzegorz Krasoń

-* *Going Full Stack in Rust with Leptos by @martsec

#rust #rustlang #iot #baremetal #leptos #wasm

My @protonprivacy colleguages in #Barcelona are organizing another #BcnRust meetup: https://www.meetup.com/bcnrust/events/311787736/. This time about:

*- *Trade-offs in IoT Applications by Grzegorz Krasoń

-* *Going Full Stack in Rust with Leptos by @martsec

#rust #rustlang #iot #baremetal #leptos #wasm

My @protonprivacy colleguages in #Barcelona are organizing another #BcnRust meetup: https://www.meetup.com/bcnrust/events/311787736/. This time about:

*- *Trade-offs in IoT Applications by Grzegorz Krasoń

-* *Going Full Stack in Rust with Leptos by @martsec

#rust #rustlang #iot #baremetal #leptos #wasm

Created my first #leptos ActionForm just now…it worked first time…I’m grinning like there’s a coat hanger stuck in my mouth

Created my first #leptos ActionForm just now…it worked first time…I’m grinning like there’s a coat hanger stuck in my mouth

"Lazy" #Leptos Update announcement

https://youtube.com/watch?v=w5fhcoxQnII

Web applications minimize initial load times by splitting your application code into multiple bundles, which can be lazily loaded as you navigate.

This long-awaited feature allows to split-up Leptos #WASM binaries!

#rustlang #webdev

"Lazy" #Leptos Update announcement

https://youtube.com/watch?v=w5fhcoxQnII

Web applications minimize initial load times by splitting your application code into multiple bundles, which can be lazily loaded as you navigate.

This long-awaited feature allows to split-up Leptos #WASM binaries!

#rustlang #webdev

"Lazy" #Leptos Update announcement

https://youtube.com/watch?v=w5fhcoxQnII

Web applications minimize initial load times by splitting your application code into multiple bundles, which can be lazily loaded as you navigate.

This long-awaited feature allows to split-up Leptos #WASM binaries!

#rustlang #webdev

"Lazy" #Leptos Update announcement

https://youtube.com/watch?v=w5fhcoxQnII

Web applications minimize initial load times by splitting your application code into multiple bundles, which can be lazily loaded as you navigate.

This long-awaited feature allows to split-up Leptos #WASM binaries!

#rustlang #webdev

"Lazy" #Leptos Update announcement

https://youtube.com/watch?v=w5fhcoxQnII

Web applications minimize initial load times by splitting your application code into multiple bundles, which can be lazily loaded as you navigate.

This long-awaited feature allows to split-up Leptos #WASM binaries!

#rustlang #webdev

In case anyone was wondering, yes my project Wordforge is effectively abandoned. I graduated and got a job last year and haven't had the time to work on it. It's a shame really since I really wanted to see something like this on the fediverse, but such is life.

If anyone wants to take over, feel free.

https://codeberg.org/grafcube/wordforge

#wordforge #opensource #foss #fediverse #activitypub #rust #leptos