It can be a little tricky to get working with some tools, but it is very fast and doesn't take up as much repo space as you'd expect since the approach is much more efficient than node_modules.
If you have weak back muscles, for example, walking is not going to do that much for them - but weight lifting will.
If your quads have atrophied because of a past knee injury, just walking - even very actively - will not fix them (bitter experience here) and the injury may well recur. But gentle goblet squats and light leg presses combined with balance exercises for proprioception will sort that out.
You lose a lot of muscle when you get older, and if you have any injuries you will naturally tend to avoid specific movements in your daily life. This _is_ better addressed by weight training (ideally with physio guidence) rather than just aiming for a goal of "being active".
"The Elastic projects were offered under the Apache license. Outside contributors donated time and energy with the understanding that their work was going towards the greater good, the public software commons. Now, instead, their contributions are embedded in a proprietary product. If they want to enjoy the fruits of their own and their co-contributors’ labor, they have to agree to a proprietary license or fork."
"Elastic’s current business model is inconsistent with what open source licenses are designed to do. Its current business desires are what proprietary licenses (which includes source available) are designed for."
Elastic are a $13 billion company. They get little sympathy from me.
They built that value off the back of many other open source products, and with help from the community - all under licenses like Apache 2.0 and MIT.
And now, after building all that value by selling Enterprise and SaaS versions of the software, they decided to specifically target their competitor who was doing the exact same thing.
Without Lucene, there would have been no ElasticSearch. Why does ElasticSearch get to take all the hard work done by Lucene contributors and sell it as part of their own product? This does not sound fair... in the terms you put it.
If this hurts Elastic, they did it to themselves. They don't deserve your support.
It can be a little tricky to get working with some tools, but it is very fast and doesn't take up as much repo space as you'd expect since the approach is much more efficient than node_modules.