The No Title^® Tech Blog

This time, we are releasing both Optimize Images and Optimize Images X at the same time. The original CLI version now uses temporary files with in-memory buffers, which prevents unnecessary I/O, and also displays more detailed and more useful version information. Optimize Images X, the GUI version, is now compatible with Python3.7+ and has the ability to open or preview a selected image.

So, just 3 days after the first public beta, here we got the second beta for Optimize Images X. It includes an important hot fix for Windows and Linux, and two new usability features.

Just for fun, this month I set myself to start a new Python project. It’s the same as Optimize Images, but with a big X and a nice graphical user interface. It wants to help you reduce the file size of images, and hopefully make your websites load faster.

If you’re a developer or a systems administrator, sooner or later you will meet that HUUUGE, GIANT, ENORMOUS file. A file that weights several gigabytes of more or less cryptic system or application logging messages, with no rotation scheme in place. Since log files are usually built by appending the most recent information to the end, probably you just need to check out the last 100 or 1000 lines, in order to find out why an application has crashed or failed to operate properly some seconds or a minute ago. Turns out that reading such huge files may not be as simple as editing them in Notepad. Probably, an application like that won’t even be able to the file. So, what else can you do?