So, after spending time moving from Make to Task, I decided. I’m going with Task in my future projects. Make will not be removed from my projects immediately, but I will not use it in the future. Let me tell you why. All this is my personal opinion. I’m not saying that Task is better than Make. I think that Task is better for me. Global Taskfile I have a global Task in my home directory for standard stuff....
Recently, I stumbled upon a tool called Taskfile. It is a task runner, similar to Makefile, but with many improvements. I decided to try it and see if it can replace my Makefiles. Why Taskfile? First of all, Makefile is a good tool. Today, you can use it on any platform, not just Linux. It is a standard tool for running tasks. It is flexible and powerful. My relation with it is love/hate....
I set the stage for learning eBPF. As mentioned in the previous post, eBPF is a technology that allows us to run code in the kernel. This is a compelling technology, but it comes with a few limitations. One of them is that we can’t use the standard output to print messages. At least not directly. Let’s explore how we can do this. Why can’t I use the standard input/output? Let’s look at this picture The eBPF programs are executed in the kernel....