home.social

#htmx — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #htmx, aggregated by home.social.

  1. Built a little Obsidian web viewer/editor with #htmx and #alpine - no JS framework bloat, no build step. Python just returns straight HTML (and a tiny bit of json for git sync operations).

  2. The Programmer's Fulcrum: 01 May, 2026 is out! It's your weekly curation of the essential news in the Open Media Network and Fediverse development communities with a focus on devastating big tech via Techno Anarchism. #fediverse #OMN #WordPress #Linux #ActivityPub #ATProto #Holos #RSS #HTML #HTMX

  3. The Programmer's Fulcrum: 01 May, 2026 is out! It's your weekly curation of the essential news in the Open Media Network and Fediverse development communities with a focus on devastating big tech via Techno Anarchism. #fediverse #OMN #WordPress #Linux #ActivityPub #ATProto #Holos #RSS #HTML #HTMX

  4. The Programmer's Fulcrum: 01 May, 2026 is out! It's your weekly curation of the essential news in the Open Media Network and Fediverse development communities with a focus on devastating big tech via Techno Anarchism. #fediverse #OMN #WordPress #Linux #ActivityPub #ATProto #Holos #RSS #HTML #HTMX

  5. The Programmer's Fulcrum: 01 May, 2026 is out! It's your weekly curation of the essential news in the Open Media Network and Fediverse development communities with a focus on devastating big tech via Techno Anarchism. #fediverse #OMN #WordPress #Linux #ActivityPub #ATProto #Holos #RSS #HTML #HTMX

  6. The Programmer's Fulcrum: 01 May, 2026 is out! It's your weekly curation of the essential news in the Open Media Network and Fediverse development communities with a focus on devastating big tech via Techno Anarchism. #fediverse #OMN #WordPress #Linux #ActivityPub #ATProto #Holos #RSS #HTML #HTMX

  7. The Fulcrum 10 April, 2026

    Welcome to this week’s The Programmer’s Fulcrum.

    It’s your weekly review of the essential news in the Open Media Network and Fediverse development communities with a focus on devastating big tech via Techno Anarchism. We aim to provide actionable content you can use to destroy Techno Feudalism each week. It has the additional benefit of weakening authoritarianism.

    IMHO, the best way to do […]

    https://newsletter.mobileatom.net/the-fulcrum-10-april-2026/ #ActivityPub #astro #ATProto #BackdropCMS #Bear #Bonfire #Codefloe #CSS #Decidim #DWeb #EmDash #FDroid #FediLab #fediverse #Ghost #Holos #HTML #HTMX #JavasScript #Kdenlive #LAUTI #Linux #OMN #PWAs #RSS #WebAwesome #WordPress #WriteFreely #XMPP #xWiki
  8. The Programmer’s Fulcrum: 27 February, 2026

    Welcome to this week’s The Programmer’s Fulcrum.

    It’s your weekly review of the essential news in the Open Media Network and Fediverse development communities with a focus on devastating big tech via Techno Anarchism. We aim to provide actionable content you can use to destroy Techno Feudalism each week. It has the additional benefit of weakening authoritarianism.

    IMHO, the best way to do […]

    https://newsletter.mobileatom.net/the-programmers-fulcrum-27-february-2026/ #ActivityPub #AI #ATProto #bluesky #Buttondown #Codeberg #CSS #Emissary #FAIR #fediverse #Ghost #GoToSocial #Gutenberg #Holos #HTML #HTMX #javascript #Linux #Mastodon #Nextcloud #OMN #OrganicMaps #PixelFed #Tuta #WordPress #XMPP #xWiki
  9. The journey of #javascript is the poster child of out of control #complexity. What started as tiny client side code to introduce some interactivity has eaten html itself (virtual #dom) and then metastasized also on the server side. A gargantuan duplication of functionality between client and server that eventually backlashed into the #htmx and #livewire type approaches.

    When you throw in the explosion of mobile clients (with architectures controlled by a duopoly) you get to the lunacy of today.

  10. Рецензия на книгу «Современные фронтенды на базе HTMX»

    Фронтенд переживает очередной виток переосмысления технологий. После десятилетия доминирования SPA-подхода, React-подобных экосистем и инструментального «комбайна» из Webpack/Vite/TypeScript/Redux появляются идеи возврата к простоте. Это о том, чтобы минимизировать JavaScript, отдать больше задач на сервер и перестать городить frontend + backend там, где это не нужно. В этом контексте библиотека HTMX стала одним из заметных феноменов последних лет.

    habr.com/ru/companies/ssp-soft

    #разработка_сайтов #фронтендразработка #фуллстек #htmx #springboot #crud #spa #книга_по_фронтенд

  11. 🤓 Oh, the joys of reading about how technology should be a festering mess of warts! Apparently, watching a #YouTube video is now the pinnacle of intellectual endeavor for those pondering the eternal mysteries of web services. 🤦‍♂️ The talk promises #insights on "htmx," but delivers a sermon on bridge-building instead—because what coder doesn't need architectural advice? 🏗️
    entropicthoughts.com/you-want- #techdebate #webservices #htmx #architecture #HackerNews #ngated

  12. I've been playing with #RustLang again.
    Using #Axum #Handlebars #Htmx #Sqlx and #Sqlite
    It's a really joyful environment to work with. I'm finding it far easier than last time, a combination of much improved compiler errors, clippy guidance, #VSCode also seems to have improved understanding of the code (I'm not using #AI just Rust-Analyser and Even Better TOML
    Plus I'm building depth rather than width, fits much better for exploration and learning.
    The amount of syntax feels much reduced :-)

  13. A quick demonstration of using the State: Overview page in Kitten’s¹ settings while developing to keep an eye on your event and event listener counts to avoid memory leaks.

    Notice how the events and listeners counts change as I navigate between the People and Settings pages in my Place² node and that they are consistent. If they were rising as I navigated back and forth I’d know I had a memory leak somewhere.

    If you use Kitten’s built-in features (e.g., the `addEventHandler()` method on your `kitten.Component` subclasses, Kitten will handle adding and removing listeners for you automatically during your component’s lifecycle. You can also do so manually in your component’s automatically-called `onConnect()` and `onDisconnect()` event handlers.

    This view is useful during development to ensure you don’t have any memory leaks as pages are loaded and unloaded.

    vimeo.com/1050714714

    ¹ kitten.small-web.org
    ² Place is in early development at the moment (codeberg.org/place/app)

    #Kitten #SmallWeb #SmallTech #demo #developerExperience #developerTools #design #eventModel #events #memory #memoryLeaks #observerPattern #listeners #web #dev #HTML #CSS #JavaScript #NodeJS #server #platform #framework #WebSockets #hypermedia #htmx #StreamingHTML #place #peerToPeer #peerToPeerWeb

  14. Started to mess around in making my own files. Already with , this has been immensely useful. As I'm able to get answers. Let alone a functioning code generator! Which for using framework like this, you kind of want a generator. 😅

    llmstxt.org/

  15. Little preview video: Kitten’s improved component model

    • Class-based page routes and components
    • Object-oriented
    • Event-based
    • Seamless hypermedia-driven WebSocket-based event mapping and interface updates (Streaming HTML)
    • A light server-side live component hierarchy with event bubbling
    • Almost as if you’re building a desktop or mobile app instead of a web app…

    … another authoring simplification made possible because on the Small Web – which is a peer-to-peer web – you build a web app/site as a tool for one person (the owner of the site/app) instead of as a tool for you to farm millions of people.

    … still experimental ;)

    vimeo.com/1049055406

    Learn more about Kitten:

    kitten.small-web.org

    If you like what you see and want us to keep existing, we could definitely use your support:

    small-tech.org/fund-us/

    :kitten:💕

    #Kitten #SmallWeb #SmallTech #StreamingHTML #objectOriented #eventBased #hypermedia #htmx #WebSocket #HTML #JavaScript #CSS #NodeJS

  16. Pretty soon, you’re going to be able to view your live pages and the events on them in real time while developing Kitten apps.

    The improved component model with support for class-based routes (and a server-side component hiearchy that lets you build well-encapsulated components and pages and work in an event-driven way) is coming along nicely and I’m back to writing Place¹ using it.

    (In the GIF, you’re looking at Place’s profile settings page. Not shown here but those profile changes reflect in realtime on all open pages. The highlighted piece of code is what streams the event details to the browser.)

    ¹ codeberg.org/place/app

    #Kitten #StreamingHTML #SmallWeb #htmx #hypermedia #WebSockets #web #dev #eventDriven #objectOriented #JavaScript #NodeJS

  17. HMPL — лучшая альтернатива HTMX

    Всем привет! В данной статье рассмотрим такой javascript модуль как HMPL и как он может заменить HTMX в проекте. Также, рассмотрим в чём их отличия, преимущества и недостатки. При дальнейшем сравнение двух модулей стоит учесть, что один является языком шаблонов, когда как другой является набором инструментов для работы с HTML, реализуемых через атрибуты и не только.

    habr.com/ru/articles/851042/

    #javascript #html #hmpl #htmx #dom #api #typescript #restful #serverside #serverside_javascript

  18. Кофе по SSH, сайты в zip-архивах. Чистый HTML лучше всего

    Очень интересная штука — интернет-магазин в консоли . Он позволяет авторизоваться в магазине и заказать товар (кофе), не выходя из терминала. Говорят , кофе из командной строки даже вкуснее, чем обычное. Просто заходим в магазин по SSH: ssh terminal.shop или ssh 172.65.113.113

    habr.com/ru/companies/ruvds/ar

    #ruvds_статьи #трюки_HTML #CSS #JS #HTMX #SSH #HTMLредактор #htmz #HTML_Notepad #текстовый_интерфейс #TUI #MPA_Archive #Redbean #libwebsockets #ArT_DeCo #предсказание_текста #MessagePack #стриминг_HTML #Shadow_DOM #вебкольцо #Comet #Observable #генератор_статических_сайтов #SeaMonkey #KompoZer

  19. Programming Jan-April 2024

    This year started off pretty light when it came to programming because I’ve been addicted to the video game Against the Storm since last winter. But I eventually started working again on various projects – some old and some new. I didn’t do any programming in January, so we’ll start in February.

    February and March

    Over these two months I worked on my replacement for web access to my Taskwarrior TODO list because Inthe.am had shut down. In February I got the podman containers set up – one to run the taskd server and one to run the website I’d coded up in Flask. In March I had to write some rudimentary Javascript to get the website to highlight the selected tab (Overdue, Today, This Month, etc). The rest of the interactivity on the site works using HTMX, letting me focus on Python instead of Javascript, but I just wasn’t able to get that part of the site to work without a tiny bit of Javascript. I also added some fixes because the date/time widget assumes UTC. Of course, now that I have it all working correctly and get lots of use for it (especially when I’m at work and I want to quickly get something out of my brain’s short-term buffer), Taskwarrior went to 3.0 which completely changes the way the program works, the API, and the way syncing works. I think in the end it’ll be for the best, but it’s annoying that I need to figure this out. That may involve finally learning how to use PyO3 to interact with Rust or re-writing part of my backend in Rust. We’ll have to see where that goes.

    April

    Things really picked up in April, programming-wise. First off, I had to upgrade the dependencies in my Amortization program. This will segue into the next topic in a second, but essentially every time I upgrade Fedora, I get a new version of Python. This means I have to redo my virtual environment. So when I tried to run this program again, I had to pip install my requirements and since some of the packages were no longer available on PyPi as wheels, it tried to compile. When that failed, I upgraded the dependencies.

    As I’ve mentioned before, because of the virtual environment annoyances, I’ve decided to rewrite all my cron utilities in a compiled language. If it’s a utility I have running via cron, it’s something I want to work all the time. I don’t want to have to run around recreating virtual environments (something I don’t mind for a program I’m going to run occasionally – see previous paragraph). So I rewrote my NASA background downloading program in Go. This was a real breeze. It truly is a pretty easy language to work with – a hybrid of C and Python in my humble opinion. I also used the opportunity to learn how to use Go’s new(ish) SLOG package.

    I also took a few days to update the one project I know for a fact is used by other people besides myself, Extra Life Donation Tracker, to use PyQt6. It was an annoying couple days figuring out what has changed since PyQt5. Or rather, to be more specific, the Qt devs did a great job documenting what had changed, but seeing how that translated to what I needed to fix for pyinstaller to make an exe for my Windows users took a few days.

    As I mentioned a couple days ago, I’ve started learning Rust. Just as I did with Python when I first learned it, I started with a project-based book: Command-Line Rust. However, while I was getting a good feel for the language, the author wasn’t quite explaining some concepts early enough (to my mind) like when to use a double colon vs a dot to access a function/method. So I started also reading The Rust Programming Language (2018 version) (link is to the newer 2021 edition). There I learned that (using Python terms) double colon is a static method (would belong to the class as a whole) while dot is a method on an instance of the “class”. While I probably could say the same thing about modern C++ or C, I think Rust is actually a good stepping-stone on the path that goes Python->Go->Hard Systems language. As a newer language with less baggage, it seems to be a child of Haskell and C, with functional programming being a first class way of programming in Rust. (I may be speaking out of my butt since I’m only a week or so into learning the language, but that’s my first impression).

    Going back to what I said about rewriting my cron utilities in compiled languages, I may end up rewriting Snap-In-Time, my btrfs snapshot project in Rust. Based on what I did in the first project of Command-Line Rust, it seems like it would be pretty trivial (compared to Go) to retrieve and use the output of system commands (like btrfs sub snap, btrfs sub del, etc). If this happens, it’s probably a few months away.

    Speaking of future projects, over at my personal Mastodon account (started before WordPress joined the Fediverse or I might have only used this account as my Fediverse presence) @djotaku I post my top scrobbled artists every week. (Here’s an example) This is another cron utility that I would prefer not to have to be mindful of when I upgrade Python (although, in comparison to the other utilities, it’s also the most trivial). I’m thinking of redoing this one in Go as (as of this point) interacting with a JSON API seems easier than in Rust. I’m basing that from looking on crates.io at the last.fm crates on there. Most of them are older (makes sense since a lot fewer of us still scrobble to last.fm than in its heyday) and none of them covered the endpoints I needed so I’d have to write my own. One last thing – even though many folks aren’t scrobbling anymore, they must be getting information from somewhere (I thought CBS either sold last.fm to Spotify or did a partnership) because this article mentions the researchers using it to analyze song lyrics.

    #Amortization #eldonationtracker #ExtraLife #Flask #Go #Golang #HTMX #Javascript #lastFm #NASA #Podman #PyQT #python #QT #rust #Taskwarrior

    https://wp.me/p5cs3g-4I3

  20. We're working on a website re-design. Made some decisions today. Will be simplifying the design concept to cards representing each of the website sections and then a search that eliminates cards that do not match the search.

    This allowed us to remove the bulky menus that the previous version of the website had and simplify the primary use of the website, which is to quickly find information.

    Will be using #PicoCSS, #Lapis #Lua and #HTMX

    #webdev