upx VS clj-kondo

According to this source:

Following optimization, tools like UPX can compress the resulting binary, significantly reducing file size. This compression is invaluable for resource-constrained environments but adds a decompression step during binary execution.

I have been using UPX but I'm quite sure if there's something out there that offers better compression.

Ah that's nice, long ago I used parchment.js to load a inform7 created z5 file on my website. You could try to compress your executable with upx https://upx.github.io/

In this process, the given packer tool embeds a natively compiled PE into another executable that contains the information needed to unpack the original content and execute it. Perhaps the most well known packer, which is not even for malicious purposes, is Golang's UPX package.

Rewrite in C#, and use an obfuscator on the DLL. You can also write some parts in C++ as many variable and function names are forgotten when compiling. You should also encrypt the PCK, and see if you can embed it. If it's embedded, you can make it more annoying to deal with by packing it with https://upx.github.io/

Another good example of false positives like this would be binaries that are compressed with UPX - the way it works is apparently very similar to how stub-loader malware operates and signature detection tools will flag it as malicious.

This will optimise the release binary to be as small as possible. Additionally with upx we can create really small docker image !

Then I compressed it with upx, cp small.exe smallUpx.exe && upx --brute smallUpx.exe, got a 10752 bytes executable, half the size, but still pretty large

My best suggestion here would be clj-kondo with flycheck-clj-kondo in Emacs. I really can't recommend it enough and would have killed to have it when I was learning Clojure. Not only will it underline all of those references to (now) undefined vars, but it can tell you about numerous little mistakes like mixing up arguments orders in (say) sequence functions, misplaced docstrings that get discarded, style conventions, etc. It's staggering how good it is even for a language as dynamic as Clojure.

The clj-kondo linters are worth reading.

Sure!

Spec: https://github.com/edn-format/edn

Example (linter config): https://github.com/clj-kondo/clj-kondo/blob/634294183a0aa2ca...

Clj-kondo doesn't produce an AST but you could easily combine the analysis output with the AST produced by rewrite-clj by matching on location.

But if you want full support, you can implement a hook: https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md

Please configure and use tools like clj-kondo and kibit. Kibit will report areas where you could write idiomatic clojure instead. Eg, it should catch all those (if (condition) true false) and ask you to replace it with (condition). Or if you really need a boolean value, use boolean to coerce it.

Try clj-kondo, a Clojure linter which will tell you about arity errors and more, before you even evaluate your code.