- cross-posted to:
- commandline@programming.dev
- cross-posted to:
- commandline@programming.dev
cross-posted from: https://lemmy.ml/post/49444213
In this release:
- use ISO8601 for date time format
- sort by time
- unsorted output option
- colorized/text output modes for entry types
Full list of features and available flags is in repository readme.
rpi zero binary is still 18KB. It was both challenging and interesting to add new features keeping binary size small.
I don’t have an intention to replace ls which is obviously preinstalled, I see fli as a complimentary daily driver. The north star of the project is to always have smaller binary size than ls , while extending or improving ls functionality
Interesting how much we can achieve with rust.
As for a new features, I see various sorting options could be implemented cheaply. If you have ideas, please share.
If you see ways to squeeze some more bytes, you are welcome.
upd:
I created dedicated community for people who may be interested : https://lemmy.ml/c/fli
i don’t care about licenses or ip, if you want to use, modify or sell it, you are free to do this, you got my personal permission… anyway, if you here to propose better license , I’m all ears.
I don’t think a different license is “needed”.
Sounds like a perfect use case for the WTFPL.
Why recommend a license that isn’t OSI approved?
so folks, what the correct one? Apache License 2.0? European Union Public License ? GNU Affero General Public License v3.0?
When not sure, this site explains it well: https://choosealicense.com/
MIT is perfectly fine. Most people want something more copyleft to avoid corporate bs. I use GPLv3 to make sure my company doesn’t do anything dumb. GPLv2 and MIT are fine if you just want credit.
AGPL is also cool, but I normally see it used in client/server configurations to prevent people from hiding the useful stuff under a different service.
Anything OSI approved will at least protect you from anything. The other licenses I see floating around usually get in trouble for vague language that can be interpreted in unintended ways.
Here’s the big book of licenses if you feel like skimming: https://www.gnu.org/licenses/license-list.en.html
Thx for info
i’d say if you want to be the most permissive but forcing other people to keep the code they create with your project to still be open source use GNU AGPL3.
Thx