It’s 2025!
I don’t usually really care so much that it’s 2025 since I’m familiar with more than one way to go about counting years. On the other hand, since other people make it a big deal, and because I’ve made some promises as you can see above, I’ve got to be a little excited because Quarto by now has a glossary. RIGHT? RIGHHHTTT? Two years later, for an academic publishing tool, without any questions being asked as requested–means the feature is there, RIGHHHHTTT? Well, no. Two years of being question-free was still not enough time.
Bell South Engineers Suck?
I’d think that the Bell South Engineers would be able to belt this one out, unless there is some incentive for them not to. I’m not sure what that incentive is, but I do know that three years for a publishing app to not have any code to deal with a glossary is a lot of wasted time. I also know now that I wasn’t told the truth. It’s not so much the glossary functionality had not been worked on, so much as it was that there was no intention to work on it in any timely fashion. Result? I got the reply I got. My point? There are plenty of projects out there that get funding, and without users like me poking people to tell them they are needed features, they get left by the wayside. Blaming your user base for pointing out a needed feature is nonsensical–especially if you tell them that as an excuse to say “Hey man, answering you sucks, cause like I totally got work to do!” It’s another project-killer mentality. Just say the truth, which is, “Yeah, we should have this feature, but our lords and masters don’t think it is a priority right now so I’m not sure when it will be added.” Bummer, sure, but way more useful in terms of informational content.Certainly, it is way more honest.
Exciting update:
So you see, asking about a feature becomes abuse, no matter the timeline. You, the USER are the problem, not the project. This is why a Code of Conduct is useless. It gives people power to self-righteously believe they are doing the correct thing, when in fact, they are failing to hold themselves to reasonable behavior. Same thing was true when the Messiah walked the earth… While probably nobody is going to die for not having a glossary in Quarto, the fact I asked was the problem as it took up precious time. When I pointed out the time that had been taken that was precious, and the feature was still not present, I’m still the problem for desiring the feature and the project to be better suited to its niche. I’m not “constructive” although I’m showing exaclty something that needs “constructing”. Consequence, mute me, the voice, and the problem is solved, right? Except there is still no glossary…