Damn, Unpoly looks great! Never tried HTMX but have been a fan of it, it solves a UX problem that frameworks like Django and Rails suffer from, without needing to bring in something heavy like React.
I'm currently working on a side project in Rails using Stimulus but sometimes I wonder if Stimulus is overkill with all of the controllers and stuff as well. Do you have an opinion on when you should reach for something like Inertia or Stimulus over htmx?
In most simple cases you probably don't want to be handling request-response initiated DOM updates in a Stimulus controller. Turbo Frames and Turbo Streams are the more htmx-like in functionality and they're excellent for this.
Correct. Django 6.0 comes with a standardised API, with 2 testing backends (ImmediateBackend and DummyBackend). You need a third-party backend to store and execute tasks.
django-tasks is the reference implementation for django.tasks, by the same author. It's up for discussion if and when the DatabaseBackend gets merged, and it seems likely to me that a Redis-based backend would be suggested at some point. It takes time and energy though!
I was traveling during this entire ordeal. My flight got delayed by 7 hours. Insane day, just now boarding my flight. American Airlines was in shambles today.
It's pretty cool that QR codes were created by a Japanese automotive company in order to address the limitations of scanning bar codes, mainly that the scans only worked with a certain orientation. [1]
That being said, I believe bar codes have the UPC number below it in case the code itself is damaged. Could QR codes have a similar textual encoding to identify them? And would that even fit legibly in the square?
QR codes also encode text, just like UPC-A. As far as I'm aware, no barcode reader can actually interpret the letters at the bottom of the code. They're just there for a human failover when the barcode gets messed up.
With that in mind, there's nothing preventing you from putting the encoded text of a QR code below it. I have a QR code in my living room that guests can scan to connect to the Wi-Fi, and I put the SSID and password below the QR code on the same page. It's not the exact encoded string, but it serves the same purpose.
My first "real" job was working for an industrial automation company, where I did a lot of work on RFID and barcode readers. Barcodes (both 2D and 3D) are delightful things. There's an enormous variety out there, and you would never know unless you look closely, because they're so well-supported. I'd bet the barcode reader at your local grocery store can read at least 9 different encodings. Some are probably physically capable of reading QR (and other 3D codes like Aztec), but the firmware has been instructed to ignore them.
In the industry, we called "normal" barcodes "2D," and stuff like QR and Aztec were called "3D" barcodes. Think of the "Z" axis as the coloration of a given point.
In all barcodes I'm aware of, that Z axis only has one bit of resolution (i.e. black or white, 1 or 0). If you had an encoding with more colors, you'd be increasing the resolution of that axis, but you wouldn't be adding a new axis per se.
Honestly, I also think 1D/2D would make more sense. But, 2D/3D is the nomenclature I saw being used among industry professionals on both the marketing and engineering sides.
reply