smxi@doctator I had to think about it. #xfce-terminal. I use #inxi almost every day but I always use the terminal, and inxi does many things. Since I use it to be a terminal only, I guess that's the closest I get to something that does one thing well on a daily basis. Also Kate but it does several things but it is really just a code editor. And #Filezilla. And often #acxi. I like using tools I made for my needs.
#inxi #codeberg has slowly been collecting stars. As with #acxi, on github where I considered 1 star equal to 50 inxi stars because it's a very focused and specific tool, so too I think will I consider 1 codeberg inxi star equal to about 50 gh stars. Despite inxi gh not getting an update since 2023-12, and being marked as archived, it keeps getting forked and starred, which is the EXACT reason I realized there was no loss leaving gh in terms of eyeballs. Eyes with nothing behind them = no value
@axelrafn @ThePlant the team that did Audacity were aging out and had noted in blog post how the stuff is so complex to do they had been trying to get younger devs involved but zero skilled ones appeared which is when they decided to sell it. There were core upgrades they wanted to do but couldn't get done and they did not want their creation to wither and fade.
These things resonate because I do a specialized audio processing tool #acxi which touches on core audio file processing issues.
2/
In terms of the #acxi code itself, because #inxi is far larger and more complex, and requires far more code discipline to maintain, and gets refactors all the time to achieve that goal, acxi tends to follow along like inxi's little brother, and benefits from all the improvements I introduce internally in inxi code. Particularly #Perl syntax and structures. In this sense, inxi really benefits acxi since acxi's code basically gets a 'free' upgrade using my latest stress tested inxi techniques
And that closes the very first @Codeberg #acxi issue. And creates the first proper #codeberg acxi release, 3.6.02.
acxi is designed to be very stable, unlike #inxi which evolves constantly, and only gets updates for fixes, like this one, or to introduce new features wanted by me or a small handful of acxi users I know. eg --tagllst, which the #slackware packager requested. A feature I now use all the time. This has happened with several powerful features. Benefit of a few good eyes.
First @Codeberg #acxi issue (silly mistake, and good issue). acxi is a specialized CLI audio processing tool that, unlike #inxi (which is made as general utility for the wider #FreeSoftware ecosystem), is intended to meet specific audio file processing needs. It makes no effort to be 'easy' or 'user friendly', although it is immensely powerful. But not for newbies. Unlike inxi, which is fully operational out of the box, acxi does nothing until configured or run with the right CLI switches.,
This is turning into a major release for #acxi, as often happens, you sort of notice odd things when working on other features, but you can't do everything at once, so the brain notes that somewhere and then when the main feature is largely complete, attention can be put on the other less related issues. I'm finding a lot now that I'm going over various features, so 3.6.00 will be a pretty major update since so many features are polished/fixed, little things wrong, code sloppiness.etc.
Polishing up and adding public docs to #acxi. That's a first, except for its man/changelog pages. Doing this helped detect some glitches in logic for --image and --replace-images and how man page described them vs how they were working. Those issues are now resolved.
This makes 3.6.00 release close, though I tend to not want to release until no changes happen for > 24 hours. But these are fixes now, docs, etc, --taglist/-L is stable, working well.
@ChristosArgyrop @mjgardner nothing, lol.
Number 1 requirement for #inxi is that it runs anywhere on any system back to Perl 5.008, which was based on running on old redhat servers mainly.
As I noted a few posts back, the time I accidentally introduced a post 5.010 feature to #acxi (state with assignment of array), I got an almost immediate bug report from someone running it on old os.
With this said, maybe in a few years I'll bump inxi to 5.010, to get say and state.
@packy @arnandegans I like 5.008, only thing I miss is say and state, #acxi is set to 5.010, and when I accidentally let a feature slip in that broke in 5.010 I got a bug report almost immediately, lol, which surprised me, some guy was using it on an old server.
To me, one of the biggest advantage of Perl over python is that it DOES NOT BREAK over time, and if you have to update a few things, they are easy to update.
I find the assumption that I want to rewrite code every few years rude.