I don't have any lifetime licenses. I see a bulk of the discussion revolving around these license. And I'm sure if I had a lifetime license, I'd be upset about this too.
Still... you have to understand that any "lifetime" offering is always a bad idea. From the producer's point of view (DirectAdmin) lifetime offerings are a way to inject a lot of capital into a product, because presumably you are paying a large fee to get a lifetime supply of that offering. This illustrates the cautionary tale of anyone considering offering a lifetime product. These probably should have been limited to a certain number when they were offered, i.e. the first 100 customers to sign up for a lifetime license. You can always grant more lifetime licenses if you need to, but this allows you to keep the number in check.
From a consumer point of view (someone that purchased a lifetime DirectAdmin license) probably should follow the idiom of "if it's too good to be true, it probably is." The company you are purchasing the lifetime offering from will likely either fold (because they didn't get enough capital to keep the project running) or will get so big that they will eventually look for ways to get out from under those sold lifetime offerings. Perhaps you can milk the purchased lifetime offering for all it's worth. If you bought a lifetime license in 2016 for $300 (no clue if that's the right price), then you've essentially paid $3.57 per month for the past 84 months (7 years) for that license. I'd say that's a pretty good milk, but it's subjective.
Like I said, I don't have any DirectAdmin lifetime licenses - so it's easy for me say that anything with "lifetime" in it's product description should be avoided.
But for me, the biggest hurt in this decision is the datacenter provided DirectAdmin (legacy) licenses. Those licenses are being paid for each month. Sure, they are at a discounted price... but who set those discounted prices? Those licenses were provided to datacenters as a way to promote DirectAdmin and providing datacenters a way to offer a comparatively cheap alternative to other pricier control panels.
Suddenly, after a fiasco with a rival control panel, DirectAdmin became quite a bit more popular. This lead to DirectAdmin raising the prices of their retail license - a license purchased directly from DirectAdmin themselves. But the datacenter pricing wasn't affected, so users still flocked to the datacenter licenses. How could DirectAdmin make more money? One way was to kill the deals with datacenters and only offer DirectAdmin direct-retail licenses. Datacenters could still qualify for cheaper licenses through bulk licensing, but that was still going to be a lot more than the previous datacenter pricing deals.
What about all of those old datacenter provided legacy licenses out there? How do we get them to pay us more money? Easy... start deprecating functions in those licenses, so that server administrators would be forced to pay a higher price for the DirectAdmin direct-retail licenses.
What functions could they deprecate to force this? It would need to be something critical to the server's functionality. Something within the DirectAdmin control panel itself probably wouldn't fit the bill. But stack applications probably would. But how do we do that? Easy, let's integrate the updating of those stack applications into the core DirectAdmin update itself. If you want to upgrade Apache, MySQL/MariaDB, or PHP you will have to be running an up-to-date version of DirectAdmin. We'll do this several months before we deprecate legacy licenses and provide no real explanation for this change, other than some garbage that it's necessary for DirectAdmin. Customers will never know what hit them! Brilliant!
Now we can control how those stack applications are upgraded, by controlling the DirectAdmin core update, which we can then control based on licensing type. Everyone will have to pay us directly for the licenses and we'll make a ton of cash!
This really was a brilliant game of chess and strategy by the DirectAdmin production team. They're playing the long game. They've started this with something that may not have an immediate impact with the MariaDB update. But if that doesn't move the needle enough, they will move to Apache, and eventually to PHP - which sees monthly updates.
As for all of the additional features and functions added to DirectAdmin (and this really applies more broadly to most every control panel out there... so it's not just a DirectAdmin thing. You can replace DirectAdmin with any of those control panels in this discussion) I think it's important to distinguish between those that use DirectAdmin as a tool and those that use DirectAdmin as a full featured server administration suite.
I come from a cPanel background. I'm sorry for mentioning that on a DirectAdmin forum, but I suspect my experience with cPanel would be similar to long time users of DirectAdmin. I remember a time to where the cPanel forums were loaded with users asking questions and having issues and the go to response was "You need to contact your datacenter" or "You need to get a qualified system administrator." Now the go to response is "Please open a ticket with us so we can check it out." I'm not exactly sure when that response changed, but that was when cPanel stopped being just a tool and became a full-fledged server administration suite. Anybody can be a web hosting company, no system administration experience is necessary. Have a problem, open a ticket with your control panel, and they'll fix you right up! And we wonder why the licensing price of control panels have gone up!
Don't misunderstand me, I'm not faulting or shaming people that use these control panels as full on server administration suites. But the ones that use the control panel as a tool are being forced to subsidize those looking for a complete server administration system through these increased licensing costs.
I came to DirectAdmin in 2019, so I definitely haven't been around very long. Honestly though... I'm still largely using the same checklist for setting up DirectAdmin now as I was back in 2019. There's not been a lot of changes to DirectAdmin that have really changed things for me. I use DirectAdmin (and other control panels) as a tool. DirectAdmin is a means for me to provide accounts to users so that they can log in and create email addresses, upload or create their website, create databases, etc. Honestly, I could still be using the same DirectAdmin from 2019 and I doubt I, nor my users, would notice any difference (the updated - Evolution? - theme is nice, however). I've gone through a lot of updates to the stack applications over those years. But DirectAdmin itself? Not so much.
Give me an interface so that users can control their email accounts, databases, and upload their website files. Give me an API so that I can more easily integrate my own interface into the backend to create and manage web hosting accounts. Give me the ability to modify stack application configurations, in such a way that future upgrades do not mess with those configuration changes. Give me a series of hookable events, so that when an action happens, I can tell the server to do something else with that data. That (unless my memory has failed me... which happens more often these days) is all I need from a control panel.
Is that for everybody? No it's not. But that's me. And I suspect that it is for a large number of people as well. I'm not a fan of rapid release scheduling. I prefer stability over everything else. Rapid releases tend to introduce unforeseen bugs or issues, because quality assurance can't possibly test everything out within the scheduling time frame. And quality assurance won't consist of the number of users that a public release will have. For DirectAdmin specific - I generally keep my servers on the previous DirectAdmin version, until I see a post about the next DirectAdmin version reaching Release Candidate status, then I upgrade to the current DirectAdmin version. Because I value stability. This hampers me a little bit because stack application update are now integrated into the DirectAdmin update itself. So in order to patch that zero-day Apache bug, I sometimes have to forego this DirectAdmin update preference and sacrifice a more stable DirectAdmin experience.
I think too often control panels (not just DirectAdmin) release updates just to prove that they are remaining relevant. "See! We're still working on the product! We're still relevant! We moved the email icon to the first line instead of the second line in your control panel. Now give us some money!" The updates themselves are largely meaningless, but are a means by the control panel to keep their customer entertained. If updates only happened once a year, some customers might forget that they even have a control panel.
One example of all of this might be the CustomBuild GUI. For those that use DirectAdmin as a tool, I would suspect that most of those people are using CustomBuild from the command-line. But some where along the line there became an influx of users that could not understand the command line (again, that's not meant to be said in a faulting tone... maybe in a tone to encourage those users to learn about the CLI) so they had to have a GUI to perform CustomBuild tasks. So a lot of development was put into a CustomBuild GUI. No doubt that took time and money, but users that are using the CustomBuild CLI aren't using the GUI - and might not even know it's there. Yet they are being forced to pay for it because other users wanted it. Developing it was also a means that DirectAdmin can point to, to say that they are still relevant.