#vuejs — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #vuejs, aggregated by home.social.
-
Roses are red
JS frameworks are a pain
https://codeberg.org/trevdev/nvim-nix/commit/d66c4246ca60c63eb56998ed99adbcf1c1933956 -
Roses are red
JS frameworks are a pain
https://codeberg.org/trevdev/nvim-nix/commit/d66c4246ca60c63eb56998ed99adbcf1c1933956 -
Roses are red
JS frameworks are a pain
https://codeberg.org/trevdev/nvim-nix/commit/d66c4246ca60c63eb56998ed99adbcf1c1933956 -
Roses are red
JS frameworks are a pain
https://codeberg.org/trevdev/nvim-nix/commit/d66c4246ca60c63eb56998ed99adbcf1c1933956 -
Roses are red
JS frameworks are a pain
https://codeberg.org/trevdev/nvim-nix/commit/d66c4246ca60c63eb56998ed99adbcf1c1933956 -
GridStack: цена выбора API для nested grids
Реальный кейс с nested grids в GridStack: — почему подход на addGrid() привёл к ручной синхронизации DnD, проблемам с lifecycle и множеству фиксов; — как переход на subGridOpts упростил архитектуру и сделал поведение стабильным.
https://habr.com/ru/articles/1071556/
#grid #gridstack #nested_grids #subgrid #архитектура #dashboard #widget #vue #vuejs #widgets
-
GridStack: цена выбора API для nested grids
Реальный кейс с nested grids в GridStack: — почему подход на addGrid() привёл к ручной синхронизации DnD, проблемам с lifecycle и множеству фиксов; — как переход на subGridOpts упростил архитектуру и сделал поведение стабильным.
https://habr.com/ru/articles/1071556/
#grid #gridstack #nested_grids #subgrid #архитектура #dashboard #widget #vue #vuejs #widgets
-
GridStack: цена выбора API для nested grids
Реальный кейс с nested grids в GridStack: — почему подход на addGrid() привёл к ручной синхронизации DnD, проблемам с lifecycle и множеству фиксов; — как переход на subGridOpts упростил архитектуру и сделал поведение стабильным.
https://habr.com/ru/articles/1071556/
#grid #gridstack #nested_grids #subgrid #архитектура #dashboard #widget #vue #vuejs #widgets
-
Зачем всё так сложно: постановка и архитектура
Итак, разбираем реальные сценарии, роли судей и организаторов, ночные нюансы и архитектуру SPA с оффлайн-синхронизацией.
https://habr.com/ru/articles/1070910/
#вебразработка #aspnet_core #c# #javascript #vuejs #postgresql #архитектура_приложений #эксперимент
-
Зачем всё так сложно: постановка и архитектура
Итак, разбираем реальные сценарии, роли судей и организаторов, ночные нюансы и архитектуру SPA с оффлайн-синхронизацией.
https://habr.com/ru/articles/1070910/
#вебразработка #aspnet_core #c# #javascript #vuejs #postgresql #архитектура_приложений #эксперимент
-
Зачем всё так сложно: постановка и архитектура
Итак, разбираем реальные сценарии, роли судей и организаторов, ночные нюансы и архитектуру SPA с оффлайн-синхронизацией.
https://habr.com/ru/articles/1070910/
#вебразработка #aspnet_core #c# #javascript #vuejs #postgresql #архитектура_приложений #эксперимент
-
Зачем все так сложно
У нас уже подходит к концу лето 2026 года. AI‑агенты, вайб-кодинг, Docker и тонны фреймворков, библиотек и примеров для всех современных платформ. Микросервисы — цель, икона и грааль как в разговорах, так и в требованиях к кандидатам. В одиночку можно быстро поднять работающий проект, подключить к нему ИИ и выложить для использования. Наконец-то закончилась волна «входа в IT» с бесконечными полусырыми курсами и инфоцыганскими каналами для вайтишников. Как-то поуспокоилось. Но есть ряд вопросов: Не тратит ли разработчик больше времени, сражаясь с настройками контейнеров для разработки или с тем же Webpack, чем на написание самого кода? Сколько нужно изучить, чтобы написать простое веб-приложение? Каково минимальное количество библиотек и фреймворков для этого? Всегда ли нужны микросервисы? Именно такие вопросы давно и регулярно всплывали в разговорах с коллегами и для ответа на них был сделан небольшой проект — чисто эксперимента ради. О нём я и хочу рассказать. Что-то будет разбираться очень подробно, а что-то пройдём мимо — это не обучение, это результат эксперимента.
https://habr.com/ru/articles/1070908/
#вебразработка #aspnet_core #c# #javascript #vuejs #архитектура_приложений #эксперимент
-
Зачем все так сложно
У нас уже подходит к концу лето 2026 года. AI‑агенты, вайб-кодинг, Docker и тонны фреймворков, библиотек и примеров для всех современных платформ. Микросервисы — цель, икона и грааль как в разговорах, так и в требованиях к кандидатам. В одиночку можно быстро поднять работающий проект, подключить к нему ИИ и выложить для использования. Наконец-то закончилась волна «входа в IT» с бесконечными полусырыми курсами и инфоцыганскими каналами для вайтишников. Как-то поуспокоилось. Но есть ряд вопросов: Не тратит ли разработчик больше времени, сражаясь с настройками контейнеров для разработки или с тем же Webpack, чем на написание самого кода? Сколько нужно изучить, чтобы написать простое веб-приложение? Каково минимальное количество библиотек и фреймворков для этого? Всегда ли нужны микросервисы? Именно такие вопросы давно и регулярно всплывали в разговорах с коллегами и для ответа на них был сделан небольшой проект — чисто эксперимента ради. О нём я и хочу рассказать. Что-то будет разбираться очень подробно, а что-то пройдём мимо — это не обучение, это результат эксперимента.
https://habr.com/ru/articles/1070908/
#вебразработка #aspnet_core #c# #javascript #vuejs #архитектура_приложений #эксперимент
-
Зачем все так сложно
У нас уже подходит к концу лето 2026 года. AI‑агенты, вайб-кодинг, Docker и тонны фреймворков, библиотек и примеров для всех современных платформ. Микросервисы — цель, икона и грааль как в разговорах, так и в требованиях к кандидатам. В одиночку можно быстро поднять работающий проект, подключить к нему ИИ и выложить для использования. Наконец-то закончилась волна «входа в IT» с бесконечными полусырыми курсами и инфоцыганскими каналами для вайтишников. Как-то поуспокоилось. Но есть ряд вопросов: Не тратит ли разработчик больше времени, сражаясь с настройками контейнеров для разработки или с тем же Webpack, чем на написание самого кода? Сколько нужно изучить, чтобы написать простое веб-приложение? Каково минимальное количество библиотек и фреймворков для этого? Всегда ли нужны микросервисы? Именно такие вопросы давно и регулярно всплывали в разговорах с коллегами и для ответа на них был сделан небольшой проект — чисто эксперимента ради. О нём я и хочу рассказать. Что-то будет разбираться очень подробно, а что-то пройдём мимо — это не обучение, это результат эксперимента.
https://habr.com/ru/articles/1070908/
#вебразработка #aspnet_core #c# #javascript #vuejs #архитектура_приложений #эксперимент
-
Бесшовный переезд с Perl на Nuxt: история одного 20-летнего монолита
Привет, Хабр! Меня зовут Эрнест Гилязов, я тимлид группы разработки интерфейсов Рунити. В этой статье расскажу, как мы переносим на новый стек проект Рег.ру, кодовой базе которого исполняется 20 лет, и почему в итоге Nuxt-приложение само раздает шапку и футер в легаси-монолит через обычный JSON-эндпоинт.
https://habr.com/ru/companies/runity/articles/1070084/
#Nuxt #Vuejs #SSR #легаси #миграция #Template_Toolkit #Perl #микрофронтенды #серверный_рендеринг #Vite
-
Бесшовный переезд с Perl на Nuxt: история одного 20-летнего монолита
Привет, Хабр! Меня зовут Эрнест Гилязов, я тимлид группы разработки интерфейсов Рунити. В этой статье расскажу, как мы переносим на новый стек проект Рег.ру, кодовой базе которого исполняется 20 лет, и почему в итоге Nuxt-приложение само раздает шапку и футер в легаси-монолит через обычный JSON-эндпоинт.
https://habr.com/ru/companies/runity/articles/1070084/
#Nuxt #Vuejs #SSR #легаси #миграция #Template_Toolkit #Perl #микрофронтенды #серверный_рендеринг #Vite
-
Бесшовный переезд с Perl на Nuxt: история одного 20-летнего монолита
Привет, Хабр! Меня зовут Эрнест Гилязов, я тимлид группы разработки интерфейсов Рунити. В этой статье расскажу, как мы переносим на новый стек проект Рег.ру, кодовой базе которого исполняется 20 лет, и почему в итоге Nuxt-приложение само раздает шапку и футер в легаси-монолит через обычный JSON-эндпоинт.
https://habr.com/ru/companies/runity/articles/1070084/
#Nuxt #Vuejs #SSR #легаси #миграция #Template_Toolkit #Perl #микрофронтенды #серверный_рендеринг #Vite
-
CVE-2026-71319 lets attackers run arbitrary commands via unauthenticated Nuxt DevTools RPC. CVSS 9.6, 7.3M monthly downloads. Patch now.
-
CVE-2026-71319 lets attackers run arbitrary commands via unauthenticated Nuxt DevTools RPC. CVSS 9.6, 7.3M monthly downloads. Patch now.
-
CVE-2026-71319 lets attackers run arbitrary commands via unauthenticated Nuxt DevTools RPC. CVSS 9.6, 7.3M monthly downloads. Patch now.
-
Как я собрал браузерный хоррор на Three.js: GLB-контракт, аномалии и PS1-рендеринг для слабых устройств
Как я сделал браузерную 3D-игру на Three.js и Vue: система аномалий, GLB-сцена, PS1-рендеринг и оптимизация под слабые устройства.
https://habr.com/ru/articles/1069580/
#threejs #webgl #JavaScript #TypeScript #Vuejs #blender #glTF #Разработка_игр #браузерные_игры #оптимизация_производительности
-
Как я собрал браузерный хоррор на Three.js: GLB-контракт, аномалии и PS1-рендеринг для слабых устройств
Как я сделал браузерную 3D-игру на Three.js и Vue: система аномалий, GLB-сцена, PS1-рендеринг и оптимизация под слабые устройства.
https://habr.com/ru/articles/1069580/
#threejs #webgl #JavaScript #TypeScript #Vuejs #blender #glTF #Разработка_игр #браузерные_игры #оптимизация_производительности
-
Как я собрал браузерный хоррор на Three.js: GLB-контракт, аномалии и PS1-рендеринг для слабых устройств
Как я сделал браузерную 3D-игру на Three.js и Vue: система аномалий, GLB-сцена, PS1-рендеринг и оптимизация под слабые устройства.
https://habr.com/ru/articles/1069580/
#threejs #webgl #JavaScript #TypeScript #Vuejs #blender #glTF #Разработка_игр #браузерные_игры #оптимизация_производительности
-
Hexnome: моя первая игра, 245 промптов и один выброшенный бэкенд
Тридцать лет я собирался написать игру, а потом за десять рабочих сессий довёл до продакшена браузерную Hexnome: 3D-поле, одиночный режим, онлайн-мультиплеер и серверный журнал команд. Получилось 245 промптов и 99 коммитов в основной ветке. Ещё 30 коммитов пришлось выбросить, когда первая архитектура мультиплеера оказалась «играбельной, но ненадёжной». Рассказываю, что именно ускорил AI — и какие решения он за меня не принял.
-
Hexnome: моя первая игра, 245 промптов и один выброшенный бэкенд
Тридцать лет я собирался написать игру, а потом за десять рабочих сессий довёл до продакшена браузерную Hexnome: 3D-поле, одиночный режим, онлайн-мультиплеер и серверный журнал команд. Получилось 245 промптов и 99 коммитов в основной ветке. Ещё 30 коммитов пришлось выбросить, когда первая архитектура мультиплеера оказалась «играбельной, но ненадёжной». Рассказываю, что именно ускорил AI — и какие решения он за меня не принял.
-
Hexnome: моя первая игра, 245 промптов и один выброшенный бэкенд
Тридцать лет я собирался написать игру, а потом за десять рабочих сессий довёл до продакшена браузерную Hexnome: 3D-поле, одиночный режим, онлайн-мультиплеер и серверный журнал команд. Получилось 245 промптов и 99 коммитов в основной ветке. Ещё 30 коммитов пришлось выбросить, когда первая архитектура мультиплеера оказалась «играбельной, но ненадёжной». Рассказываю, что именно ускорил AI — и какие решения он за меня не принял.
-
История одного архитектурного круга: реактивность Vue
Vue снова меняет способ обновления интерфейса: теперь на горизонте Vapor и рендеринг без Virtual DOM. Зачем очередная архитектурная перестройка и что не устраивает команду Vue в нынешнем подходе? Чтобы ответить, проследим путь Vue от Object.defineProperty до Proxy и зачем теперь понадобился Vapor. Это поможет лучше понимать поведение ref, reactive и computed, вникнуть в причины архитектурных изменений Vue и подготовиться к дальнейшим изменениям.
https://habr.com/ru/companies/first/articles/1069048/
#vue #vuejs #vue3 #signals #reactivity #reactivity_javascript #proxy #virtualdom #vapor #dom
-
История одного архитектурного круга: реактивность Vue
Vue снова меняет способ обновления интерфейса: теперь на горизонте Vapor и рендеринг без Virtual DOM. Зачем очередная архитектурная перестройка и что не устраивает команду Vue в нынешнем подходе? Чтобы ответить, проследим путь Vue от Object.defineProperty до Proxy и зачем теперь понадобился Vapor. Это поможет лучше понимать поведение ref, reactive и computed, вникнуть в причины архитектурных изменений Vue и подготовиться к дальнейшим изменениям.
https://habr.com/ru/companies/first/articles/1069048/
#vue #vuejs #vue3 #signals #reactivity #reactivity_javascript #proxy #virtualdom #vapor #dom
-
История одного архитектурного круга: реактивность Vue
Vue снова меняет способ обновления интерфейса: теперь на горизонте Vapor и рендеринг без Virtual DOM. Зачем очередная архитектурная перестройка и что не устраивает команду Vue в нынешнем подходе? Чтобы ответить, проследим путь Vue от Object.defineProperty до Proxy и зачем теперь понадобился Vapor. Это поможет лучше понимать поведение ref, reactive и computed, вникнуть в причины архитектурных изменений Vue и подготовиться к дальнейшим изменениям.
https://habr.com/ru/companies/first/articles/1069048/
#vue #vuejs #vue3 #signals #reactivity #reactivity_javascript #proxy #virtualdom #vapor #dom
-
𝗩𝘂𝗲-𝗴𝗼𝗼𝗱-𝘁𝗮𝗯𝗹𝗲:
#DataTable #VueJS #VueGoodTable
https://thewhale.cchttps://thewhale.cc/posts/vue-good-table
A powerful data table plugin for VueJS. Get features like sorting / column filtering / paging with minimal setup. Easily customize anything from table cells to column headers. Leverage checkbox table, grouped rows and remote workflow for your table.
-
𝗩𝘂𝗲-𝗴𝗼𝗼𝗱-𝘁𝗮𝗯𝗹𝗲:
#DataTable #VueJS #VueGoodTable
https://thewhale.cchttps://thewhale.cc/posts/vue-good-table
A powerful data table plugin for VueJS. Get features like sorting / column filtering / paging with minimal setup. Easily customize anything from table cells to column headers. Leverage checkbox table, grouped rows and remote workflow for your table.
-
𝗩𝘂𝗲-𝗴𝗼𝗼𝗱-𝘁𝗮𝗯𝗹𝗲:
#DataTable #VueJS #VueGoodTable
https://thewhale.cchttps://thewhale.cc/posts/vue-good-table
A powerful data table plugin for VueJS. Get features like sorting / column filtering / paging with minimal setup. Easily customize anything from table cells to column headers. Leverage checkbox table, grouped rows and remote workflow for your table.
-
𝗩𝘂𝗲-𝗴𝗼𝗼𝗱-𝘁𝗮𝗯𝗹𝗲:
#DataTable #VueJS #VueGoodTable
https://thewhale.cchttps://thewhale.cc/posts/vue-good-table
A powerful data table plugin for VueJS. Get features like sorting / column filtering / paging with minimal setup. Easily customize anything from table cells to column headers. Leverage checkbox table, grouped rows and remote workflow for your table.
-
@Chao-c'BTW I had account on identi.ca, which was StatusNet powered (I believe).
It was. At least until Evan and Erin could no longer justify it running on that janky OStatus protocol. The result was the ActivityPump protocol, the pump.io software and Identi.ca's switch to pump.io with all hands on board.Yes, and it should not be implemented in Ruby or PHP or something like that. I have seen one online discussion forum being rewritten from PHP to Rust few years ago, and the improvement in responsiveness of the web platform was amazing. (I do C, not Rust, but C is too oldschool now, and the performance penalty of Rust is minor, probably not noticeable at all)
This reminds me of how the Fediverse is all over the place in terms of programming languages. Everyone has their own Holy Grail.
Friendica and its descendants are written in PHP. They may not be the fastest (even though what bogged down early Friendica were its heavyweight federation connectors to everywhere, especially the one for Facebook that came in 2011). Mike either discarded or rewrote these when he rewrote Red. But they happily run on a run-of-the-mill LAMP stack.
Mastodon is written in Ruby on Rails. Hubzilla runs circles around it in terms of performance per account/channel, and that has to say something. The only thing that managed to top this was early diaspora*, written in Ruby on Rails for Mac with MongoDB as the database system.
The *omas are built in Elixir. Granted, they're utter featherweights, especially considering their features. They're legendary for their low server impact. Then again, Pleroma apparently is spaghetti code straight from hell. Its own devs often don't have a clue where to go look for bugs, much less how to fix them. (Miraculously, the Akkoma devs do manage to get ride of quite a number of them.)
The *keys are built in TypeScript and Vue.js. I guess one reason why Misskey is infamous for having so many forks and forks of forks is because there are tons of people who can code in JavaScript, the primary mobile programming language.
Iceshrimp.NET is a still very incomplete "rewrite" of old Iceshrimp in C#. It was largely tackled to get rid of all those nasty bugs inherited from Misskey that even Misskey doesn't manage to get rid of. I've heard quite some outcry: Iceshrimp.NET is a sell-out to Microsoft. I guess whoever uttered that didn't go check who owns TypeScript.
PieFed is a dead giveaway: Python. And PieFed makes more headlines in the Threadiverse for server politics than for its underlying technology, except that Lemmy pales in comparison.
GoToSocial is a dead giveaway, too: Go. And it was one of the first Fediverse server applications to not come with a Web UI. Those who use it for a single-user server often don't even bother installing one and use some Mastodon app or other instead. Besides, why drag around a Web UI if there are much better third-party Web UIs than whatever you could whip up?
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Friendica #Hubzilla #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Iceshrimp #IceshrimpJS #Iceshrimp.NET #PieFed #GoToSocial #PHP #RubyOnRails #Elixir #JavaScript #TypeScript #VueJS #C# #Python #Go -
@Chao-c'BTW I had account on identi.ca, which was StatusNet powered (I believe).
It was. At least until Evan and Erin could no longer justify it running on that janky OStatus protocol. The result was the ActivityPump protocol, the pump.io software and Identi.ca's switch to pump.io with all hands on board.Yes, and it should not be implemented in Ruby or PHP or something like that. I have seen one online discussion forum being rewritten from PHP to Rust few years ago, and the improvement in responsiveness of the web platform was amazing. (I do C, not Rust, but C is too oldschool now, and the performance penalty of Rust is minor, probably not noticeable at all)
This reminds me of how the Fediverse is all over the place in terms of programming languages. Everyone has their own Holy Grail.
Friendica and its descendants are written in PHP. They may not be the fastest (even though what bogged down early Friendica were its heavyweight federation connectors to everywhere, especially the one for Facebook that came in 2011). Mike either discarded or rewrote these when he rewrote Red. But they happily run on a run-of-the-mill LAMP stack.
Mastodon is written in Ruby on Rails. Hubzilla runs circles around it in terms of performance per account/channel, and that has to say something. The only thing that managed to top this was early diaspora*, written in Ruby on Rails for Mac with MongoDB as the database system.
The *omas are built in Elixir. Granted, they're utter featherweights, especially considering their features. They're legendary for their low server impact. Then again, Pleroma apparently is spaghetti code straight from hell. Its own devs often don't have a clue where to go look for bugs, much less how to fix them. (Miraculously, the Akkoma devs do manage to get ride of quite a number of them.)
The *keys are built in TypeScript and Vue.js. I guess one reason why Misskey is infamous for having so many forks and forks of forks is because there are tons of people who can code in JavaScript, the primary mobile programming language.
Iceshrimp.NET is a still very incomplete "rewrite" of old Iceshrimp in C#. It was largely tackled to get rid of all those nasty bugs inherited from Misskey that even Misskey doesn't manage to get rid of. I've heard quite some outcry: Iceshrimp.NET is a sell-out to Microsoft. I guess whoever uttered that didn't go check who owns TypeScript.
PieFed is a dead giveaway: Python. And PieFed makes more headlines in the Threadiverse for server politics than for its underlying technology, except that Lemmy pales in comparison.
GoToSocial is a dead giveaway, too: Go. And it was one of the first Fediverse server applications to not come with a Web UI. Those who use it for a single-user server often don't even bother installing one and use some Mastodon app or other instead. Besides, why drag around a Web UI if there are much better third-party Web UIs than whatever you could whip up?
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Friendica #Hubzilla #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Iceshrimp #IceshrimpJS #Iceshrimp.NET #PieFed #GoToSocial #PHP #RubyOnRails #Elixir #JavaScript #TypeScript #VueJS #C# #Python #Go -
@Chao-c'BTW I had account on identi.ca, which was StatusNet powered (I believe).
It was. At least until Evan and Erin could no longer justify it running on that janky OStatus protocol. The result was the ActivityPump protocol, the pump.io software and Identi.ca's switch to pump.io with all hands on board.Yes, and it should not be implemented in Ruby or PHP or something like that. I have seen one online discussion forum being rewritten from PHP to Rust few years ago, and the improvement in responsiveness of the web platform was amazing. (I do C, not Rust, but C is too oldschool now, and the performance penalty of Rust is minor, probably not noticeable at all)
This reminds me of how the Fediverse is all over the place in terms of programming languages. Everyone has their own Holy Grail.
Friendica and its descendants are written in PHP. They may not be the fastest (even though what bogged down early Friendica were its heavyweight federation connectors to everywhere, especially the one for Facebook that came in 2011). Mike either discarded or rewrote these when he rewrote Red. But they happily run on a run-of-the-mill LAMP stack.
Mastodon is written in Ruby on Rails. Hubzilla runs circles around it in terms of performance per account/channel, and that has to say something. The only thing that managed to top this was early diaspora*, written in Ruby on Rails for Mac with MongoDB as the database system.
The *omas are built in Elixir. Granted, they're utter featherweights, especially considering their features. They're legendary for their low server impact. Then again, Pleroma apparently is spaghetti code straight from hell. Its own devs often don't have a clue where to go look for bugs, much less how to fix them. (Miraculously, the Akkoma devs do manage to get ride of quite a number of them.)
The *keys are built in TypeScript and Vue.js. I guess one reason why Misskey is infamous for having so many forks and forks of forks is because there are tons of people who can code in JavaScript, the primary mobile programming language.
Iceshrimp.NET is a still very incomplete "rewrite" of old Iceshrimp in C#. It was largely tackled to get rid of all those nasty bugs inherited from Misskey that even Misskey doesn't manage to get rid of. I've heard quite some outcry: Iceshrimp.NET is a sell-out to Microsoft. I guess whoever uttered that didn't go check who owns TypeScript.
PieFed is a dead giveaway: Python. And PieFed makes more headlines in the Threadiverse for server politics than for its underlying technology, except that Lemmy pales in comparison.
GoToSocial is a dead giveaway, too: Go. And it was one of the first Fediverse server applications to not come with a Web UI. Those who use it for a single-user server often don't even bother installing one and use some Mastodon app or other instead. Besides, why drag around a Web UI if there are much better third-party Web UIs than whatever you could whip up?
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Friendica #Hubzilla #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Iceshrimp #IceshrimpJS #Iceshrimp.NET #PieFed #GoToSocial #PHP #RubyOnRails #Elixir #JavaScript #TypeScript #VueJS #C# #Python #Go -
@Chao-c'BTW I had account on identi.ca, which was StatusNet powered (I believe).
It was. At least until Evan and Erin could no longer justify it running on that janky OStatus protocol. The result was the ActivityPump protocol, the pump.io software and Identi.ca's switch to pump.io with all hands on board.Yes, and it should not be implemented in Ruby or PHP or something like that. I have seen one online discussion forum being rewritten from PHP to Rust few years ago, and the improvement in responsiveness of the web platform was amazing. (I do C, not Rust, but C is too oldschool now, and the performance penalty of Rust is minor, probably not noticeable at all)
This reminds me of how the Fediverse is all over the place in terms of programming languages. Everyone has their own Holy Grail.
Friendica and its descendants are written in PHP. They may not be the fastest (even though what bogged down early Friendica were its heavyweight federation connectors to everywhere, especially the one for Facebook that came in 2011). Mike either discarded or rewrote these when he rewrote Red. But they happily run on a run-of-the-mill LAMP stack.
Mastodon is written in Ruby on Rails. Hubzilla runs circles around it in terms of performance per account/channel, and that has to say something. The only thing that managed to top this was early diaspora*, written in Ruby on Rails for Mac with MongoDB as the database system.
The *omas are built in Elixir. Granted, they're utter featherweights, especially considering their features. They're legendary for their low server impact. Then again, Pleroma apparently is spaghetti code straight from hell. Its own devs often don't have a clue where to go look for bugs, much less how to fix them. (Miraculously, the Akkoma devs do manage to get ride of quite a number of them.)
The *keys are built in TypeScript and Vue.js. I guess one reason why Misskey is infamous for having so many forks and forks of forks is because there are tons of people who can code in JavaScript, the primary mobile programming language.
Iceshrimp.NET is a still very incomplete "rewrite" of old Iceshrimp in C#. It was largely tackled to get rid of all those nasty bugs inherited from Misskey that even Misskey doesn't manage to get rid of. I've heard quite some outcry: Iceshrimp.NET is a sell-out to Microsoft. I guess whoever uttered that didn't go check who owns TypeScript.
PieFed is a dead giveaway: Python. And PieFed makes more headlines in the Threadiverse for server politics than for its underlying technology, except that Lemmy pales in comparison.
GoToSocial is a dead giveaway, too: Go. And it was one of the first Fediverse server applications to not come with a Web UI. Those who use it for a single-user server often don't even bother installing one and use some Mastodon app or other instead. Besides, why drag around a Web UI if there are much better third-party Web UIs than whatever you could whip up?
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Friendica #Hubzilla #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Iceshrimp #IceshrimpJS #Iceshrimp.NET #PieFed #GoToSocial #PHP #RubyOnRails #Elixir #JavaScript #TypeScript #VueJS #C# #Python #Go -
@Chao-c'BTW I had account on identi.ca, which was StatusNet powered (I believe).
It was. At least until Evan and Erin could no longer justify it running on that janky OStatus protocol. The result was the ActivityPump protocol, the pump.io software and Identi.ca's switch to pump.io with all hands on board.Yes, and it should not be implemented in Ruby or PHP or something like that. I have seen one online discussion forum being rewritten from PHP to Rust few years ago, and the improvement in responsiveness of the web platform was amazing. (I do C, not Rust, but C is too oldschool now, and the performance penalty of Rust is minor, probably not noticeable at all)
This reminds me of how the Fediverse is all over the place in terms of programming languages. Everyone has their own Holy Grail.
Friendica and its descendants are written in PHP. They may not be the fastest (even though what bogged down early Friendica were its heavyweight federation connectors to everywhere, especially the one for Facebook that came in 2011). Mike either discarded or rewrote these when he rewrote Red. But they happily run on a run-of-the-mill LAMP stack.
Mastodon is written in Ruby on Rails. Hubzilla runs circles around it in terms of performance per account/channel, and that has to say something. The only thing that managed to top this was early diaspora*, written in Ruby on Rails for Mac with MongoDB as the database system.
The *omas are built in Elixir. Granted, they're utter featherweights, especially considering their features. They're legendary for their low server impact. Then again, Pleroma apparently is spaghetti code straight from hell. Its own devs often don't have a clue where to go look for bugs, much less how to fix them. (Miraculously, the Akkoma devs do manage to get ride of quite a number of them.)
The *keys are built in TypeScript and Vue.js. I guess one reason why Misskey is infamous for having so many forks and forks of forks is because there are tons of people who can code in JavaScript, the primary mobile programming language.
Iceshrimp.NET is a still very incomplete "rewrite" of old Iceshrimp in C#. It was largely tackled to get rid of all those nasty bugs inherited from Misskey that even Misskey doesn't manage to get rid of. I've heard quite some outcry: Iceshrimp.NET is a sell-out to Microsoft. I guess whoever uttered that didn't go check who owns TypeScript.
PieFed is a dead giveaway: Python. And PieFed makes more headlines in the Threadiverse for server politics than for its underlying technology, except that Lemmy pales in comparison.
GoToSocial is a dead giveaway, too: Go. And it was one of the first Fediverse server applications to not come with a Web UI. Those who use it for a single-user server often don't even bother installing one and use some Mastodon app or other instead. Besides, why drag around a Web UI if there are much better third-party Web UIs than whatever you could whip up?
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Friendica #Hubzilla #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Iceshrimp #IceshrimpJS #Iceshrimp.NET #PieFed #GoToSocial #PHP #RubyOnRails #Elixir #JavaScript #TypeScript #VueJS #C# #Python #Go -
J'ai commis un petit serveur de chat anonyme et embeddable facilement, qui utilise ntfy comme backend.
Bon je me suis aidé de Claude pour le début, je dois l'avouer. Ce n'est pas quelque chose que je compte généraliser mais c'était intéressant.
https://lanterne-rouge.info/2026/07/chatfy-le-mini-chat-anonyme-quon-peut-poser-partout
Le code est là : https://codeberg.org/nanawel/chatfy
#chat #ntfy #self-hosted #anonymous #vuejs #messaging #opensource
-
J'ai commis un petit serveur de chat anonyme et embeddable facilement, qui utilise ntfy comme backend.
Bon je me suis aidé de Claude pour le début, je dois l'avouer. Ce n'est pas quelque chose que je compte généraliser mais c'était intéressant.
https://lanterne-rouge.info/2026/07/chatfy-le-mini-chat-anonyme-quon-peut-poser-partout
Le code est là : https://codeberg.org/nanawel/chatfy
#chat #ntfy #self-hosted #anonymous #vuejs #messaging #opensource
-
Oh, my first commit and PR is merged in the #vuejs #documentation !!
`87113 docs: update nodejs expected version (#3415) bdae3ed · 1 hour ago`
That's just a little versionning fix but I'm a bit proud of it. 🤓️ 😊️
-
Oh, my first commit and PR is merged in the #vuejs #documentation !!
`87113 docs: update nodejs expected version (#3415) bdae3ed · 1 hour ago`
That's just a little versionning fix but I'm a bit proud of it. 🤓️ 😊️
-
Oh, my first commit and PR is merged in the #vuejs #documentation !!
`87113 docs: update nodejs expected version (#3415) bdae3ed · 1 hour ago`
That's just a little versionning fix but I'm a bit proud of it. 🤓️ 😊️
-
Oh, my first commit and PR is merged in the #vuejs #documentation !!
`87113 docs: update nodejs expected version (#3415) bdae3ed · 1 hour ago`
That's just a little versionning fix but I'm a bit proud of it. 🤓️ 😊️
-
The browser is the framework
#customelements #frontenddev #react #vuejs #svelte #angular
Crossposted with @openvibe
-
Morning lovely peopl of the Fediverse.
My current contract will come to an end in August, so I am on the lookout for my next gig.
- Frontend JavaScript developer with 15+ years experience
- Fond of VueJS, minimal frameworks, Vanilla JS (but also React experience over the years)
- CSS advocate. Currently using super modern CSS on this project which has been awesome, feel free to ask me about it if you like.
- Accessibility advocate, trying to push to make sure code and markup is as accessible as it can be. WCAG, ARIA and A11Y.
- Communication skills - Advanced! (love being a team player)
- All round nice fellow you could introduce to your friends and family.
- Contract ideally, will consider Perm but has to be a good fit.
I am UK based (in the East Midlands) but really looking for remote.
Also I know the market is odd now, maybe not once what it was, and LinkedIn seems to be a bit flaky, so if you have recommendations for other platforms, hit me with it.
Retoots very welcome 😊
#JavaScript #Frontend #FrontendDeveloper #Hire #SeekingWork #OpenToWork #Contract #Vue #VueJS #React #CSS #SASS #SCSS #FediHire #FediHired
-
Morning lovely peopl of the Fediverse.
My current contract will come to an end in August, so I am on the lookout for my next gig.
- Frontend JavaScript developer with 15+ years experience
- Fond of VueJS, minimal frameworks, Vanilla JS (but also React experience over the years)
- CSS advocate. Currently using super modern CSS on this project which has been awesome, feel free to ask me about it if you like.
- Accessibility advocate, trying to push to make sure code and markup is as accessible as it can be. WCAG, ARIA and A11Y.
- Communication skills - Advanced! (love being a team player)
- All round nice fellow you could introduce to your friends and family.
- Contract ideally, will consider Perm but has to be a good fit.
I am UK based (in the East Midlands) but really looking for remote.
Also I know the market is odd now, maybe not once what it was, and LinkedIn seems to be a bit flaky, so if you have recommendations for other platforms, hit me with it.
Retoots very welcome 😊
#JavaScript #Frontend #FrontendDeveloper #Hire #SeekingWork #OpenToWork #Contract #Vue #VueJS #React #CSS #SASS #SCSS #FediHire #FediHired
-
Morning lovely peopl of the Fediverse.
My current contract will come to an end in August, so I am on the lookout for my next gig.
- Frontend JavaScript developer with 15+ years experience
- Fond of VueJS, minimal frameworks, Vanilla JS (but also React experience over the years)
- CSS advocate. Currently using super modern CSS on this project which has been awesome, feel free to ask me about it if you like.
- Accessibility advocate, trying to push to make sure code and markup is as accessible as it can be. WCAG, ARIA and A11Y.
- Communication skills - Advanced! (love being a team player)
- All round nice fellow you could introduce to your friends and family.
- Contract ideally, will consider Perm but has to be a good fit.
I am UK based (in the East Midlands) but really looking for remote.
Also I know the market is odd now, maybe not once what it was, and LinkedIn seems to be a bit flaky, so if you have recommendations for other platforms, hit me with it.
Retoots very welcome 😊
#JavaScript #Frontend #FrontendDeveloper #Hire #SeekingWork #OpenToWork #Contract #Vue #VueJS #React #CSS #SASS #SCSS #FediHire #FediHired
-
Morning lovely peopl of the Fediverse.
My current contract will come to an end in August, so I am on the lookout for my next gig.
- Frontend JavaScript developer with 15+ years experience
- Fond of VueJS, minimal frameworks, Vanilla JS (but also React experience over the years)
- CSS advocate. Currently using super modern CSS on this project which has been awesome, feel free to ask me about it if you like.
- Accessibility advocate, trying to push to make sure code and markup is as accessible as it can be. WCAG, ARIA and A11Y.
- Communication skills - Advanced! (love being a team player)
- All round nice fellow you could introduce to your friends and family.
- Contract ideally, will consider Perm but has to be a good fit.
I am UK based (in the East Midlands) but really looking for remote.
Also I know the market is odd now, maybe not once what it was, and LinkedIn seems to be a bit flaky, so if you have recommendations for other platforms, hit me with it.
Retoots very welcome 😊
#JavaScript #Frontend #FrontendDeveloper #Hire #SeekingWork #OpenToWork #Contract #Vue #VueJS #React #CSS #SASS #SCSS #FediHire #FediHired
-
Morning lovely peopl of the Fediverse.
My current contract will come to an end in August, so I am on the lookout for my next gig.
- Frontend JavaScript developer with 15+ years experience
- Fond of VueJS, minimal frameworks, Vanilla JS (but also React experience over the years)
- CSS advocate. Currently using super modern CSS on this project which has been awesome, feel free to ask me about it if you like.
- Accessibility advocate, trying to push to make sure code and markup is as accessible as it can be. WCAG, ARIA and A11Y.
- Communication skills - Advanced! (love being a team player)
- All round nice fellow you could introduce to your friends and family.
- Contract ideally, will consider Perm but has to be a good fit.
I am UK based (in the East Midlands) but really looking for remote.
Also I know the market is odd now, maybe not once what it was, and LinkedIn seems to be a bit flaky, so if you have recommendations for other platforms, hit me with it.
Retoots very welcome 😊
#JavaScript #Frontend #FrontendDeveloper #Hire #SeekingWork #OpenToWork #Contract #Vue #VueJS #React #CSS #SASS #SCSS #FediHire #FediHired
-
How to use Vue and i18n to offer your site in multiple languages
I am genuinely surprised we haven’t covered this topic before, given that it is one of the most powerful ways to instantly level up a web application. Today, we are tackling internationalization, showing you how to easily offer your website in multiple languages. The web is inherently global, and locking your content behind a single language limits your audience from the start. To bridge that gap, we are going to integrate the industry-standard vue-i18n plugin to handle our translations reactively, all while continuing to use the sleek Web Awesome components we’ve been exploring lately. We will look at how to neatly organize your content into JSON files, avoid common reactivity quirks, and instantly swap your UI’s vocabulary with a simple dropdown menu.
What is our goal? Previously, we focused on making your apps accessible to individuals with visual impairments, ensuring they can access your content. This time, we will concentrate on making your content accessible to those who do not understand English. In the header, you will notice a dropdown with the options of English, Spanish, French, and Mandarin. When you select a new language, the content changes.
If you want to modify what the (sample text) poem says, there is a JSON file available for each of the four languages. To obtain translations, you can either consult someone who speaks the language or, as I did, use a translation website.
Example: https://enjoyed-star-jennet.codepen.app
#vueI18n #VueJs #WebAwesome #WebComponents -
How to use Vue and i18n to offer your site in multiple languages
I am genuinely surprised we haven’t covered this topic before, given that it is one of the most powerful ways to instantly level up a web application. Today, we are tackling internationalization, showing you how to easily offer your website in multiple languages. The web is inherently global, and locking your content behind a single language limits your audience from the start. To bridge that gap, we are going to integrate the industry-standard vue-i18n plugin to handle our translations reactively, all while continuing to use the sleek Web Awesome components we’ve been exploring lately. We will look at how to neatly organize your content into JSON files, avoid common reactivity quirks, and instantly swap your UI’s vocabulary with a simple dropdown menu.
What is our goal? Previously, we focused on making your apps accessible to individuals with visual impairments, ensuring they can access your content. This time, we will concentrate on making your content accessible to those who do not understand English. In the header, you will notice a dropdown with the options of English, Spanish, French, and Mandarin. When you select a new language, the content changes.
If you want to modify what the (sample text) poem says, there is a JSON file available for each of the four languages. To obtain translations, you can either consult someone who speaks the language or, as I did, use a translation website.
Example: https://enjoyed-star-jennet.codepen.app
#vueI18n #VueJs #WebAwesome #WebComponents -
How to use Vue and i18n to offer your site in multiple languages
I am genuinely surprised we haven’t covered this topic before, given that it is one of the most powerful ways to instantly level up a web application. Today, we are tackling internationalization, showing you how to easily offer your website in multiple languages. The web is inherently global, and locking your content behind a single language limits your audience from the start. To bridge that gap, we are going to integrate the industry-standard vue-i18n plugin to handle our translations reactively, all while continuing to use the sleek Web Awesome components we’ve been exploring lately. We will look at how to neatly organize your content into JSON files, avoid common reactivity quirks, and instantly swap your UI’s vocabulary with a simple dropdown menu.
What is our goal? Previously, we focused on making your apps accessible to individuals with visual impairments, ensuring they can access your content. This time, we will concentrate on making your content accessible to those who do not understand English. In the header, you will notice a dropdown with the options of English, Spanish, French, and Mandarin. When you select a new language, the content changes.
If you want to modify what the (sample text) poem says, there is a JSON file available for each of the four languages. To obtain translations, you can either consult someone who speaks the language or, as I did, use a translation website.
Example: https://enjoyed-star-jennet.codepen.app
#vueI18n #VueJs #WebAwesome #WebComponents -
How to use Vue and i18n to offer your site in multiple languages
I am genuinely surprised we haven’t covered this topic before, given that it is one of the most powerful ways to instantly level up a web application. Today, we are tackling internationalization, showing you how to easily offer your website in multiple languages. The web is inherently global, and locking your content behind a single language limits your audience from the start. To bridge that gap, we are going to integrate the industry-standard vue-i18n plugin to handle our translations reactively, all while continuing to use the sleek Web Awesome components we’ve been exploring lately. We will look at how to neatly organize your content into JSON files, avoid common reactivity quirks, and instantly swap your UI’s vocabulary with a simple dropdown menu.
What is our goal? Previously, we focused on making your apps accessible to individuals with visual impairments, ensuring they can access your content. This time, we will concentrate on making your content accessible to those who do not understand English. In the header, you will notice a dropdown with the options of English, Spanish, French, and Mandarin. When you select a new language, the content changes.
If you want to modify what the (sample text) poem says, there is a JSON file available for each of the four languages. To obtain translations, you can either consult someone who speaks the language or, as I did, use a translation website.
Example: https://enjoyed-star-jennet.codepen.app
#vueI18n #VueJs #WebAwesome #WebComponents -
How to use Vue and i18n to offer your site in multiple languages
I am genuinely surprised we haven’t covered this topic before, given that it is one of the most powerful ways to instantly level up a web application. Today, we are tackling internationalization, showing you how to easily offer your website in multiple languages. The web is inherently global, and locking your content behind a single language limits your audience from the start. To bridge that gap, we are going to integrate the industry-standard vue-i18n plugin to handle our translations reactively, all while continuing to use the sleek Web Awesome components we’ve been exploring lately. We will look at how to neatly organize your content into JSON files, avoid common reactivity quirks, and instantly swap your UI’s vocabulary with a simple dropdown menu.
What is our goal? Previously, we focused on making your apps accessible to individuals with visual impairments, ensuring they can access your content. This time, we will concentrate on making your content accessible to those who do not understand English. In the header, you will notice a dropdown with the options of English, Spanish, French, and Mandarin. When you select a new language, the content changes.
If you want to modify what the (sample text) poem says, there is a JSON file available for each of the four languages. To obtain translations, you can either consult someone who speaks the language or, as I did, use a translation website.
Example: https://enjoyed-star-jennet.codepen.app
#vueI18n #VueJs #WebAwesome #WebComponents -
УМНЫЙ К1 — контроллер на базе ESP32 с REST, syslog и много опенсорса
Предисловие Возможно то, про что я хочу рассказать в своей первой статье тут, покажется не новым, уже знакомым велосипедом. Речь пойдет о контроллерах на базе ESP32 и программном обеспечении. Да, современных решений, открытых и бесплатных – много. А сейчас зарождается еще одно (а опенсорса мало не бывает, я считаю). В статье я упущу и не буду рассказывать ни про свое знакомство с ардуиной, esp, php, python, js ни про то, что пришел сюда давным-давно гуманитарием. И да простят мой, вероятно не корректный, «жаргон» истинные профессионалы в микроэлектронике и программировании - итак, приступим. Совсем недавно я отключил RPI4 с HA и наконец «воткнул» в котельную очередную, но «готовую к деплою» версию контроллера (разрешите его далее называть «УМНЫЙ К1», спасибо).
https://habr.com/ru/articles/1053764/
#esp32 #rest_api #espidf #tauri #javascript #vuejs #vite #rust #умныйдом #видеонаблюдение
-
УМНЫЙ К1 — контроллер на базе ESP32 с REST, syslog и много опенсорса
Предисловие Возможно то, про что я хочу рассказать в своей первой статье тут, покажется не новым, уже знакомым велосипедом. Речь пойдет о контроллерах на базе ESP32 и программном обеспечении. Да, современных решений, открытых и бесплатных – много. А сейчас зарождается еще одно (а опенсорса мало не бывает, я считаю). В статье я упущу и не буду рассказывать ни про свое знакомство с ардуиной, esp, php, python, js ни про то, что пришел сюда давным-давно гуманитарием. И да простят мой, вероятно не корректный, «жаргон» истинные профессионалы в микроэлектронике и программировании - итак, приступим. Совсем недавно я отключил RPI4 с HA и наконец «воткнул» в котельную очередную, но «готовую к деплою» версию контроллера (разрешите его далее называть «УМНЫЙ К1», спасибо).
https://habr.com/ru/articles/1053764/
#esp32 #rest_api #espidf #tauri #javascript #vuejs #vite #rust #умныйдом #видеонаблюдение
-
УМНЫЙ К1 — контроллер на базе ESP32 с REST, syslog и много опенсорса
Предисловие Возможно то, про что я хочу рассказать в своей первой статье тут, покажется не новым, уже знакомым велосипедом. Речь пойдет о контроллерах на базе ESP32 и программном обеспечении. Да, современных решений, открытых и бесплатных – много. А сейчас зарождается еще одно (а опенсорса мало не бывает, я считаю). В статье я упущу и не буду рассказывать ни про свое знакомство с ардуиной, esp, php, python, js ни про то, что пришел сюда давным-давно гуманитарием. И да простят мой, вероятно не корректный, «жаргон» истинные профессионалы в микроэлектронике и программировании - итак, приступим. Совсем недавно я отключил RPI4 с HA и наконец «воткнул» в котельную очередную, но «готовую к деплою» версию контроллера (разрешите его далее называть «УМНЫЙ К1», спасибо).
https://habr.com/ru/articles/1053764/
#esp32 #rest_api #espidf #tauri #javascript #vuejs #vite #rust #умныйдом #видеонаблюдение
-
I got some bad news: there will be no #Vuejs #Berlin #meetup in July. But we'll be back in August with a new #hackntell and maybe a teeny tiny anniversary...
-
I got some bad news: there will be no #Vuejs #Berlin #meetup in July. But we'll be back in August with a new #hackntell and maybe a teeny tiny anniversary...