task-organizer VS sysbox

Happy to see Lazarus on the front page.

I have used it for many years. For me it's still the only IDE with a fast compiler that creates native applications for Linux and Windows (and many other OS). And it doesn't require additional runtime libraries to be installed, so just download and run the application.

BTW: I created a Personal Kanban Task Organizer that is automatically built for Linux and Windows. It uses lazbuild in a GitLab CI Docker Container:

https://gitlab.com/moasda/task-organizer

https://gitlab.com/moasda/task-organizer

It has an Outlook integration so I can see my tasks for today in the Outlook calendar.

Runs on Windows and Linux.

Or maybe any other program to sort tasks and manage projects? I found that kanban is very useful for me, because columns may be not only date-based (for example "Idea/Backlog/Create branch/.../Production/...").

I recently found some good kanbans, but each of them is missing something. For example, a very cool https://gitlab.com/moasda/task-organizer/ has in-built search but has no tags. https://github.com/peterhs73/xBan looks very nice and simple but is very slow when columns are >5. Another nice kanban is https://github.com/Lyaaaaaaaaaaaaaaa/Project_Kanban, but is has no search functions and many other useful things.

Of course, at one night I can drink more coffee and try to fix one of them but maybe you know some other local, fast and easy program? Maybe not very popular.

Yes, I first learned this and the name "splay" from CFengine, back in the day.

I put together a small busybox-like collection of sysadmin tools, and one of the subcommands is "splay" to sleep for a random amount of time. It's one of those things that is useful surprisingly often, even outside cron.

https://github.com/skx/sysbox

I remember in 1999 there was a project to reimplement a bunch of these tools in perl:

https://perlpowertools.com/

I even contributed a little, back then. I guess writing basic versions of "ls", for example, is trivial. But there's a lot of work getting all the tools done, with all the flags implemented and behaving as expected.

I guess there are tools like busybox, toybox, and similar, which also implement a lot of "stuff" to varying degrees of completion. From my side the biggest takeaway from those projects is the sheer convenience of deploying a single binary and installing symlinks to change functionality.

I replicated something similar with my sysbox project, collecting tools together in one golang binary with various subcommands:

https://github.com/skx/sysbox

I use at least one of those tools on a daily basis, though I suspect they're not so universally useful.

If you've got perl installed you'll might have a "GET" binary present, mine is /usr/bin/GET, which comes with the WWW-module.

Although this is written in portable perl, rather than being compiled, so the static vs. dynamic choice doesn't really mean much it is a simple alternative.

Otherwise I built a simple busybox-inspired collection of tools, written in golang, which includes a simple HTTP client too:

https://github.com/skx/sysbox

Those are just a couple of examples, I'm certain there are multiple other choices out there. But I guess curl is ubiquitous enough that most people just use it directly, and add it when missing!

That's pretty cool.

I wrote something similar in my static collection of sysadmin tools - https://github.com/skx/sysbox - In my simple pre-processor I only allow two special things:

#include "file/goes/here"

I bundled together a small collection of sysadmin/scripting-tools here:

https://github.com/skx/sysbox

Those are probably amongst the things that I use most often which are non-standard.

I used to have very full ~/bin, and ~/$(hostname), directories. In the end I pared them back and started bundling things together in one binary.

The end result is very similar to this approach, I run "sysbox blah", or "sysbox help", and use integrated subcommands.

Very helpful and makes deployment easy by having only a single binary:

https://github.com/skx/sysbox

Not bash/shell, but similar and useful idea to experiment with.

I support that in my sysbox utility-box, via the subcommands processor, and it is very helpful.