#acxi — Public Fediverse posts

@[email protected] 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.

@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.

@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.

@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.

@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

#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

#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/

@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/

@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

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

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.

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.

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.,

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.,

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.,

#inxi 3.3.25 goes out the door, last matching tables updates for cpu, disk vendor. Features gpu device id updates, various fixes, the new --config options, some documentation updates.

Some other #acxi stuff I used for inxi was the organization of sub categories in the changelog, which helps readability, and makes it easier to maintain and update.

In a sense, the recent acxi updates moved its code closer to inxi style, but also some stuff moved back into inxi that I found useful.

With with a faint pop, just missed Chinese New Year release, #acxi 3.6.00 goes out the door. Now to move on to do other things.

For those watching, #pinxi is moving very slowly towards next #inxi, but nothing pressing really calls for a release yet, but features/enhancements are slowly building up. Better intel/amd gpu IDs for example.

Last changelog and tiny fixes for #acxi 3.6.00, I think maybe I'll do it today, latest tomorrow. Nothing has changed with --taglist for a few days now, and changes have only been docs and a few tiny additions which don't matter, so maybe ok to consider it stable. Note it makes no real difference, all the dev stuff goes to main branch (called 'stable' for odd historical reasons) as soon as tested anyway, so it's really just about a tagged 'release' in github terms.

#acxi (con'd)
* Sync convert_file also used redundant code, now it's all neat and tidy, which made it easier to improve the --dry output options as well. Also, had never indicated if copy and mkdir were running in dry mode or actually happening, now shows 'Test mode:' where relevant for the entire process.
* Earlier in process, refactored OptionsHandler::verify_selections()(to make sure options have the data they need, or conflicting options aren't used), that had gotten really messy over time.

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.

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.

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.

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.

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.

I think this is a first, since the new #acxi --config option is easy to implement, and useful, I extended it to #pinxi/#inxi. This will be in next inxi, and is in present pinxi now.

Usually acxi lags somewhat behind inxi in terms of code and logic, but due to recent heavy spate of work on acxi, the pattern is reversed for the time being.

I don't know why it never struck me to just let users easily find what config file is active, and what configs it has, but there you have it.

I would complain about what a pain maintaining complicated help options, man page, changelog, and now the new acxi-values.txt dev doc is overall, but the reality is, I find that when I have to document, and more important, make sure docs are consistent and actually reflect what is going on, I almost always find little glitches.

Ongoing pre-release #acxi docs/feature additions is no exception to this rule, all kinds of odd little glitches found and fixed.

But doing code AND docs is a pain.

This will not impact any #acxi user who has set OUTPUT_TYPE already in configs, or who starts acxi with --outtput [type]. So it's just a corner case check to avoid horrible mess for any user who was using the old default of #ogg. But I've been thinking of switching to modern default for a while, but wanted to give it some time.

And, since this will be a major version release, #acxi is moving from the old default output type #ogg, which is largely in maintenance mode, to #opus. Added in a few features to avoid any users who had never explicitly set OUTPUT_TYPE in configs and aren't using --output option to exit if no explicit output type set for sync actions. it could be quite nasty if you updated and had used old default ogg, then ran with new opus without realizing. This was cleanest way to handle that test.

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.

@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.

@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.

@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.

@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.

I'm assuming since I'm now thinking about cleaning up some debuggers and documenting them for #acxi, that means this really difficult --taglist feature is largely stable now. Everything with #tagging is hard, and anyone who tells you it isn't has never written code dealing with tagging.

@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.

@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.

@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.

@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.

@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.

@mykhaylo #inxi and #acxi, backend tools for those, and some for work. Not a lot at work, but I found it far better in production in any scenario where I had used shell + php before. inxi is an extreme practical extraction and reporting tool, and is in a sense exactly what perl was designed for. #acxi not as extreme. Core requirement for inxi in particular is to work on 15+ year old os/hardware, so you can run it on old servers. No other language has the feature stability of perl 5.

And I think this largely completes this phase of #acxi active development, unless we can find some more tagging arcana corner cases to torture the code with.

Probably the most revealing project I've done with #perl so far because this one exposed 3 distinct things, one almost certainly a true bug, 2 not. This confirms my feeling that this new feature in acxi was very hard, because I had to move perl into areas I hadn't pushed it to before, thus triggering the events.
...

And I think this largely completes this phase of #acxi active development, unless we can find some more tagging arcana corner cases to torture the code with.

Probably the most revealing project I've done with #perl so far because this one exposed 3 distinct things, one almost certainly a true bug, 2 not. This confirms my feeling that this new feature in acxi was very hard, because I had to move perl into areas I hadn't pushed it to before, thus triggering the events.
...

And I think this largely completes this phase of #acxi active development, unless we can find some more tagging arcana corner cases to torture the code with.

Probably the most revealing project I've done with #perl so far because this one exposed 3 distinct things, one almost certainly a true bug, 2 not. This confirms my feeling that this new feature in acxi was very hard, because I had to move perl into areas I hadn't pushed it to before, thus triggering the events.
...

And I think this largely completes this phase of #acxi active development, unless we can find some more tagging arcana corner cases to torture the code with.

Probably the most revealing project I've done with #perl so far because this one exposed 3 distinct things, one almost certainly a true bug, 2 not. This confirms my feeling that this new feature in acxi was very hard, because I had to move perl into areas I hadn't pushed it to before, thus triggering the events.
...