Why Native?

Unattended Installs

Silent installation is a simple as appending the /S switch to *any* of our installers! For Process Lasso, see more installer command line switches here.

Native x86 and x86-64 code

Process Lasso, ParkControl, PECompact and our other software is written entirely in native, unmanaged code. This means that it does NOT use the .NET Common Language Runtime (CLR) and that the code is compiled to machine code, instead of to Microsoft Intermediate Language (MSIL). The advantage of this is low memory use and fast performance.

You may ask, why do developers use .NET if it increases memory consumption and CPU use? The answer is simply that .NET offers easier Rapid Application Development (RAD), and, theoretically, the same code can be used on multiple platforms. To be fair, we should note that for *some* applications the difference in user-perceived performance between managed (.NET) and unmanaged (native) code is negligible, but that is certainly NOT the case for a resident process manager like Process Lasso.

Since Process Lasso is always running, ‘resident’, it is *imperative* that it consume as few system resources as possible. The worst thing a performance utility could do is make matters worse by consuming a lot of system resources itself. Sadly, this is what many of them do.

Native, unmanaged code makes our core engine, which we’ve named ProcessGovernor.exe, highly efficient and able to respond more quickly to changing system conditions. No competitor can match the performance of our core engine.

We took the hard route to ensure our applications consume as few resources as possible.

Discover more from Bitsum

Subscribe to get the latest posts to your email.