Byte Buddy VS timber

Currently, Ulyp uses bytebuddy library which does an immense job of handling all the work of instrumentation and makes it extremely easy for all Java developers. The rest is relatively straightforward to implement. The ongoing blogposts will shed a light on how the tool is implemented. Right now, let’s move to action.

byte-buddy - runtime code generation for the Java virtual machine - https://github.com/raphw/byte-buddy

> It is stable and in use by distinguished frameworks and tools such as Mockito, Hibernate , Jackson, Google's Bazel build system and many others. Byte Buddy is also used by a large number of commercial products to great result. It is currently downloaded over 75 million times a year.

As seen above, the API exposes the user to low-level bytecode manipulation via byte arrays. It would be unwieldy to do it directly. Hence, real-life projects rely on bytecode manipulation libraries. ASM has been the traditional library for this, but it seems that Byte Buddy has superseded it. Note that Byte Buddy uses ASM but provides a higher-level abstraction.

Just a drive-by comment: ByteBuddy is worth a look https://bytebuddy.net/. It is built on top of ASM.

> can you show an example of how you'd parse, say, a .java.in

The canonical way to do such a thing is through the java annotation processing api [1] and using a tool like java poet [2]. Before you did that, you'd probably decide if you wanted to instead use bytecode generation with a library like bytebuddy [3]

But, assuming for some reason, you wanted to torture yourself and actually consume a java.in file and apply a regex, then you'd probably pull out the "maven-replacer-plugin" [4] and configure that for the task at hand. (or use your favorite templating language plugin. There's a million of them).

Though, to be fair, this really isn't something that comes up in regular java programming due to the nature of the ecosystem. Anything you'd want to codegen likely already has a library and anything you didn't would receive (legitimate) push back.

[1] https://www.baeldung.com/java-annotation-processing-builder

[2] https://github.com/square/javapoet

[3] https://bytebuddy.net/

[4] https://github.com/beiliubei/maven-replacer-plugin

Have a look at byte buddy.

If you've ever used libraries like https://github.com/JakeWharton/hugo or https://hibernate.org/ (if you've ever done some backend development) and wondered how do they seem to add some code/logic into your app just by adding some annotation to some method, or if you ever wondered how mocking frameworks like Mockito can change a class behavior for example, then most likely you're interested in a programming technique that allows to modify existing code, usually known as Aspect oriented programming (also known in Java as Bytecode instrumentation) which, even though it might sound intimidating at first, some really cool tools such as Byte Buddy or AspectJ make it quite easy to accomplish.

To try and fix this problem fast I knew I needed some sort of logging and that is when I discovered Timber and Firebase Crashlynics. I then used THIS video to set both of them up and to create a decent crash reporting system.

Timber

Do you still use the Android Timber lib? The only real pro I see is that you don't need to declare the Tag, other than that that "pro" where each call checks if debug or not I wonder why you would like to have that, I mean what I want is all debug-only logs to get stripped out from the code, and instead of calling if(BuildConfig.Debug) on each Timer.xy() call why not create an extra Application class under the debug folder where logs are activated? Just trying to figure out of this lib that actually started like 9 years ago is still needed or not really anymore. https://github.com/JakeWharton/timber

One of the options could be to setup logging to the file within the app and sync it with backend once necessary or required. This could be achieved by using library, such as Timber and setting up local file. Depending on your constraints, such as file size, you might want to include a file rotation strategy, e.g. start a new file and remove the old one.

Timber for logging

Same as in Timber