It's an amusing solution, but if this ends up being anything like the missing PHP 6, it's also going to cause confusion for users. It might've been better to just mea culpa and release 3.0 anyway. I can't imagine anybody would really hold it against the author.
As long as they commit to making the next version after this htmx 8, I will be content with this versioning scheme.
Why skip version 7? It should be 6 7
Then 8
Meme versioning could work. Memes are temporal.
You can derive a lot of information about my age and current version from the dad-joke version string “I thought it was 6 7 when 7 8 9”
You might have to skip 9 to avoid faulty version checks
Maybe the versioning should be powers of 2
def 6 and 7
if there is another version of htmx it will be 8 for sure
htmx forever
Apple just jumped to version 26 across all its code bases. I think HTMX can survive with skipping to 4.
What's the confusion around PHP 6? - There would have been a lot more confusion due to articles, talk slides, even printed books, .. talking about PHP 6's Unicode support would have been truly confusing.
A mea culpa would've been just fine. Even Big Tech can't keep their promises around this stuff (Windows 10 was the last OS remember?)
Traditionally, software engineers are smart people
Source for this? After years in the industry, I believe otherwise at this point.
There are plenty of people with high INT and low WIS. As the old joke goes, intelligence is knowing that a tomato is a fruit. Wisdom is knowing not to put tomatoes in a fruit salad.
INT is knowing how to use Kubernetes, WIS is knowing when not to?
I wonder if the intersection of HTMX and Kubernetes users is empty or not :). I wouldn't be surprised (and it'd be great!) if it is.
Maybe they could just initially launch v3.1 instead of a v3.0. They would still be technically correct.