#tauri — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #tauri, aggregated by home.social.
-
I have been quiet a while, but now I'm showing why:
First public beta of Entracte is out today 🎬
A cross-platform break reminder I've been building — for anyone whose desk job has them staring at a screen too long without realising.
→ https://entracte.drmowinckels.io
#LMM #Claude #Tauri #Rust #breakReminder #DeveloeprWellbeing
-
Shine — C++ Фреймворк для десктоп приложений с использованием React
Краткий обзор и представление фреймворка Shine для разработки десктоп приложений используя C++ и React.
-
Configuración de NextJS con Tauri
NextJS es un framework de React que permite la creación de aplicaciones web modernas y optimizadas, mientras que Tauri es una herramienta que permite construir aplicaciones de escritorio con tecnologías web.
https://norvik.tech/news/configuracion-nextjs-tauri
#Technology #Nextjs #Tauri #DesarrolloWeb #AplicacionesLigeras #NorvikTech #DesarrolloSoftware #TechInnovation
-
»#Tauri is an alternative cross-platform, open-source framework for building desktop and mobile apps using web technologies while leveraging #Rust on the back-end. In replacing #Electron with Tauri, the #Lemonade SDK is now "10x smaller" than before. The pre-built macOS and Windows binaries for example were 101~107 MB with Lemonade 10.2 and are now 7~9 MB with Lemonade 10.3.«
-
»#Tauri is an alternative cross-platform, open-source framework for building desktop and mobile apps using web technologies while leveraging #Rust on the back-end. In replacing #Electron with Tauri, the #Lemonade SDK is now "10x smaller" than before. The pre-built macOS and Windows binaries for example were 101~107 MB with Lemonade 10.2 and are now 7~9 MB with Lemonade 10.3.«
-
»#Tauri is an alternative cross-platform, open-source framework for building desktop and mobile apps using web technologies while leveraging #Rust on the back-end. In replacing #Electron with Tauri, the #Lemonade SDK is now "10x smaller" than before. The pre-built macOS and Windows binaries for example were 101~107 MB with Lemonade 10.2 and are now 7~9 MB with Lemonade 10.3.«
-
»#Tauri is an alternative cross-platform, open-source framework for building desktop and mobile apps using web technologies while leveraging #Rust on the back-end. In replacing #Electron with Tauri, the #Lemonade SDK is now "10x smaller" than before. The pre-built macOS and Windows binaries for example were 101~107 MB with Lemonade 10.2 and are now 7~9 MB with Lemonade 10.3.«
-
»#Tauri is an alternative cross-platform, open-source framework for building desktop and mobile apps using web technologies while leveraging #Rust on the back-end. In replacing #Electron with Tauri, the #Lemonade SDK is now "10x smaller" than before. The pre-built macOS and Windows binaries for example were 101~107 MB with Lemonade 10.2 and are now 7~9 MB with Lemonade 10.3.«
-
I've started sketching out an app I want to develop and as I want it to have Windows, Mac and Linux builds I was starting down the Electron route but then noticed Tauri. Given this apps usage, amount of data it sometimes processes and possible later uses of the code Rust might have some advantages. Anyone on here used both?
-
YAKE! вместо нейросети: как мы заменили 600 МБ ONNX-реранкера на 400 строк статистики
В Yttri мы изначально использовали ONNX-реранкер bge-reranker-v2-m3 для RAG-поиска. Качество было хорошим, но цена для local-first desktop-приложения оказалась слишком высокой: около 600 МБ модели, до 1.8 ГБ RAM в пике и ощутимая нагрузка на CPU. В статье разбираю, как мы заменили тяжёлый нейросетевой реранкер на собственную реализацию YAKE! на Rust: без модели, без прогрева, без внешних сервисов и с латентностью порядка микросекунд. Показываю механику алгоритма, интеграцию в RAG, автотегирование, ограничения подхода и главный архитектурный вывод: не каждая AI-задача требует ещё одной нейросети. Иногда лучший AI-компонент - это тот, который удалось удалить.
https://habr.com/ru/articles/1027726/
#Rust #Tauri #RAG #SQLite #Localfirst #NLP #YAKE #Embeddings #Desktop
-
YAKE! вместо нейросети: как мы заменили 600 МБ ONNX-реранкера на 400 строк статистики
В Yttri мы изначально использовали ONNX-реранкер bge-reranker-v2-m3 для RAG-поиска. Качество было хорошим, но цена для local-first desktop-приложения оказалась слишком высокой: около 600 МБ модели, до 1.8 ГБ RAM в пике и ощутимая нагрузка на CPU. В статье разбираю, как мы заменили тяжёлый нейросетевой реранкер на собственную реализацию YAKE! на Rust: без модели, без прогрева, без внешних сервисов и с латентностью порядка микросекунд. Показываю механику алгоритма, интеграцию в RAG, автотегирование, ограничения подхода и главный архитектурный вывод: не каждая AI-задача требует ещё одной нейросети. Иногда лучший AI-компонент - это тот, который удалось удалить.
https://habr.com/ru/articles/1027726/
#Rust #Tauri #RAG #SQLite #Localfirst #NLP #YAKE #Embeddings #Desktop
-
YAKE! вместо нейросети: как мы заменили 600 МБ ONNX-реранкера на 400 строк статистики
В Yttri мы изначально использовали ONNX-реранкер bge-reranker-v2-m3 для RAG-поиска. Качество было хорошим, но цена для local-first desktop-приложения оказалась слишком высокой: около 600 МБ модели, до 1.8 ГБ RAM в пике и ощутимая нагрузка на CPU. В статье разбираю, как мы заменили тяжёлый нейросетевой реранкер на собственную реализацию YAKE! на Rust: без модели, без прогрева, без внешних сервисов и с латентностью порядка микросекунд. Показываю механику алгоритма, интеграцию в RAG, автотегирование, ограничения подхода и главный архитектурный вывод: не каждая AI-задача требует ещё одной нейросети. Иногда лучший AI-компонент - это тот, который удалось удалить.
https://habr.com/ru/articles/1027726/
#Rust #Tauri #RAG #SQLite #Localfirst #NLP #YAKE #Embeddings #Desktop
-
YAKE! вместо нейросети: как мы заменили 600 МБ ONNX-реранкера на 400 строк статистики
В Yttri мы изначально использовали ONNX-реранкер bge-reranker-v2-m3 для RAG-поиска. Качество было хорошим, но цена для local-first desktop-приложения оказалась слишком высокой: около 600 МБ модели, до 1.8 ГБ RAM в пике и ощутимая нагрузка на CPU. В статье разбираю, как мы заменили тяжёлый нейросетевой реранкер на собственную реализацию YAKE! на Rust: без модели, без прогрева, без внешних сервисов и с латентностью порядка микросекунд. Показываю механику алгоритма, интеграцию в RAG, автотегирование, ограничения подхода и главный архитектурный вывод: не каждая AI-задача требует ещё одной нейросети. Иногда лучший AI-компонент - это тот, который удалось удалить.
https://habr.com/ru/articles/1027726/
#Rust #Tauri #RAG #SQLite #Localfirst #NLP #YAKE #Embeddings #Desktop
-
Trying to automate Tauri app testing on arch linux.
Currently faced an issue of webkitgtk not providing webkitdriver. Anyone knows which package already exists that includes the driver? I am searching over the web, but all I found is a suggestion to build it by myself, which can be okay, yet I think I just had no luck in finding existing package.
-
Trying to automate Tauri app testing on arch linux.
Currently faced an issue of webkitgtk not providing webkitdriver. Anyone knows which package already exists that includes the driver? I am searching over the web, but all I found is a suggestion to build it by myself, which can be okay, yet I think I just had no luck in finding existing package.
-
Trying to automate Tauri app testing on arch linux.
Currently faced an issue of webkitgtk not providing webkitdriver. Anyone knows which package already exists that includes the driver? I am searching over the web, but all I found is a suggestion to build it by myself, which can be okay, yet I think I just had no luck in finding existing package.
-
Trying to automate Tauri app testing on arch linux.
Currently faced an issue of webkitgtk not providing webkitdriver. Anyone knows which package already exists that includes the driver? I am searching over the web, but all I found is a suggestion to build it by myself, which can be okay, yet I think I just had no luck in finding existing package.
-
The funny thing with #Tauri is that on Windows it uses Edge’s Chrome engine instead of WebKit (as is the case on Linux and Mac) so windows users probably get the best/fastest experience.
-
Writing a new feed reader. I'm reusing and reworking code from BlogCat which is my Firefox Add-on to make blogging a real feature inside #Firefox
For years, some people told me they'd prefer it as a standalone app, so I'm making it with #Tauri so I don't rewrite everything.
So far so good. Calling it Blog Garden.
-
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.
-
I'm Josh — DevOps by trade, dark fantasy novelist by compulsion. I live in Nova Scotia and spend my non-work hours writing a trilogy or building Kindling: a free, open-source desktop app that turns fiction outlines into a scaffolded drafting view. No AI. No cloud. Runs on your machine.
Here to talk Rust, Tauri, local-first software, and the writing life.
#introduction #buildinpublic #rustlang #tauri #opensource #writingcommunity #indiedev #localfirst
-
FiT календарь тренировок — финал трилогии пет-проекта
Год назад я опубликовал первую статью про разработку приложения календаря тренировок. Спустя 5 месяцев опубликовал рассказ о 10 обновлениях . Сейчас время финала истории - ещё 7 обновлений за 7 месяцев. Сам регулярно пользуюсь приложением - оно добавляет мотивации заниматься спортом дальше, сохраняет график тренировок, следит за объемом выполненных упражнений. На текущий момент в приложении больше 150 зарегистрированных пользователей. Времени на пет-проект уделял крайне мало, но основная функциональность была уже готова ранее. Сейчас на нём можно пробовать что-то новое - получается хороший полигон для испытаний. Исходный код Приложение в RuStore Веб-версия Frontend: Typescript, Vitest, Vite, Vue, Tanstack Query, Vue I18n, Tauri Backend: Typescript, Vitest, Esbuild, Fastify, Mongoose, MongoDB, Swagger
https://habr.com/ru/articles/1021790/
#vue #vuejs #vuejs #петпроект #петпроекты #tauri #мобильные_приложения #javascript #typescript #вебприложения
-
FiT календарь тренировок — финал трилогии пет-проекта
Год назад я опубликовал первую статью про разработку приложения календаря тренировок. Спустя 5 месяцев опубликовал рассказ о 10 обновлениях . Сейчас время финала истории - ещё 7 обновлений за 7 месяцев. Сам регулярно пользуюсь приложением - оно добавляет мотивации заниматься спортом дальше, сохраняет график тренировок, следит за объемом выполненных упражнений. На текущий момент в приложении больше 150 зарегистрированных пользователей. Времени на пет-проект уделял крайне мало, но основная функциональность была уже готова ранее. Сейчас на нём можно пробовать что-то новое - получается хороший полигон для испытаний. Исходный код Приложение в RuStore Веб-версия Frontend: Typescript, Vitest, Vite, Vue, Tanstack Query, Vue I18n, Tauri Backend: Typescript, Vitest, Esbuild, Fastify, Mongoose, MongoDB, Swagger
https://habr.com/ru/articles/1021790/
#vue #vuejs #vuejs #петпроект #петпроекты #tauri #мобильные_приложения #javascript #typescript #вебприложения
-
FiT календарь тренировок — финал трилогии пет-проекта
Год назад я опубликовал первую статью про разработку приложения календаря тренировок. Спустя 5 месяцев опубликовал рассказ о 10 обновлениях . Сейчас время финала истории - ещё 7 обновлений за 7 месяцев. Сам регулярно пользуюсь приложением - оно добавляет мотивации заниматься спортом дальше, сохраняет график тренировок, следит за объемом выполненных упражнений. На текущий момент в приложении больше 150 зарегистрированных пользователей. Времени на пет-проект уделял крайне мало, но основная функциональность была уже готова ранее. Сейчас на нём можно пробовать что-то новое - получается хороший полигон для испытаний. Исходный код Приложение в RuStore Веб-версия Frontend: Typescript, Vitest, Vite, Vue, Tanstack Query, Vue I18n, Tauri Backend: Typescript, Vitest, Esbuild, Fastify, Mongoose, MongoDB, Swagger
https://habr.com/ru/articles/1021790/
#vue #vuejs #vuejs #петпроект #петпроекты #tauri #мобильные_приложения #javascript #typescript #вебприложения
-
FiT календарь тренировок — финал трилогии пет-проекта
Год назад я опубликовал первую статью про разработку приложения календаря тренировок. Спустя 5 месяцев опубликовал рассказ о 10 обновлениях . Сейчас время финала истории - ещё 7 обновлений за 7 месяцев. Сам регулярно пользуюсь приложением - оно добавляет мотивации заниматься спортом дальше, сохраняет график тренировок, следит за объемом выполненных упражнений. На текущий момент в приложении больше 150 зарегистрированных пользователей. Времени на пет-проект уделял крайне мало, но основная функциональность была уже готова ранее. Сейчас на нём можно пробовать что-то новое - получается хороший полигон для испытаний. Исходный код Приложение в RuStore Веб-версия Frontend: Typescript, Vitest, Vite, Vue, Tanstack Query, Vue I18n, Tauri Backend: Typescript, Vitest, Esbuild, Fastify, Mongoose, MongoDB, Swagger
https://habr.com/ru/articles/1021790/
#vue #vuejs #vuejs #петпроект #петпроекты #tauri #мобильные_приложения #javascript #typescript #вебприложения
-
🚀 Wow, VS Code is now a microscopic marvel thanks to Tauri! They've somehow crammed the same bloated architecture into a 96% smaller package—probably by eliminating all those pesky features developers never knew they needed. Who needs robust functionality when you can have teeny, tiny disappointment instead? 😜🦄
https://github.com/Sidenai/sidex #VSCode #Tauri #Microservices #DeveloperDisappointment #TinyPackage #TechNews #HackerNews #ngated -
VS Code rebuilt on Tauri. Same architecture, 96% smaller
https://github.com/Sidenai/sidex
#HackerNews #VSCode #Tauri #Rebuild #Smaller #Architecture #96Percent
-
VS Code rebuilt on Tauri. Same architecture, 96% smaller
https://github.com/Sidenai/sidex
#HackerNews #VSCode #Tauri #Rebuild #Smaller #Architecture #96Percent
-
VS Code rebuilt on Tauri. Same architecture, 96% smaller
https://github.com/Sidenai/sidex
#HackerNews #VSCode #Tauri #Rebuild #Smaller #Architecture #96Percent
-
VS Code rebuilt on Tauri. Same architecture, 96% smaller
https://github.com/Sidenai/sidex
#HackerNews #VSCode #Tauri #Rebuild #Smaller #Architecture #96Percent
-
VS Code rebuilt on Tauri. Same architecture, 96% smaller
https://github.com/Sidenai/sidex
#HackerNews #VSCode #Tauri #Rebuild #Smaller #Architecture #96Percent
