JetBrainsRuntime VS unlogged-sdk

JetBrains have their tweaks to the JRE available: https://github.com/JetBrains/JetBrainsRuntime

The major problems begin when you want to leverage the GPU or multimedia components in which case you would want something else.

Jetbrains Runtime – this is bundled with IntelliJ and Android Studio, but with patches focused on optimization for use within an Interactive Development Environment context – doing incremental builds, hot reload of class definition, and embedded Chromium in the runtime. I do not believe the added features are useful for building and archiving Android Applications for distribution, but it will work non-the-less.

https://github.com/JetBrains/JetBrainsRuntime

Also with 'Java on Truffle' on GraalVM you can use enhanced class reloading

However, I am running IntelliJ on Asahi since June already. They did not provide offical Linux arm64 support, but what since May, when they released the first 2022.2 EAP, they switched to JBR 17 (the JetBrains Java Runtime). JBR 17. Fortunatly, in May, they started to release JBR builds for Linux am64, starting with JBR 17.0.3-b463.3. That meant we had everything we needed to run IntelliJ on Asahi: I just had to set the env var IDEA_JDK=/path/to/arm64/jbr/ to make IntelliJ use the correct JBR. Besides that it was necessary to download a fsnotifier version that was build for arm64 and set the path in ~/.config/JetBrains/IntelliJIdea2022.3/idea.properties.

Have you tried the JetBrains Runtime with DCEVM? https://github.com/JetBrains/JetBrainsRuntime/releases/tag/jbr17.0.2b396.4

This project's key is replacing x86_64 Jetbrains Runtime (https://github.com/JetBrains/JetBrainsRuntime) to arm64 Jetbrains Runtime. Arctic Fox IntelliJ Core version is 2020.3.1, maybe google upgrade core version to 2021.1 as soon as possible. (IntelliJ Core version 2021.1 released at a few days ago.)

https://github.com/JetBrains/JetBrainsRuntime

Hello HN! Parth, and Shardul here. We have been building unlogged.io for the last 21 months. We started as a time travel debugger and pivoted to record and replay with assertions, mocking, and code coverage. You can save the replays in the form of a JSON and commit them to your git.

Both Parth and I come from an e-commerce/payments background where production bugs meant heavy financial losses. Big billion days/Black Friday sales meant months of code freezes with low productivity. Before committing the code, we wanted to replay production traffic and know the breaking changes right away, like in sub-second. Kind of like unit+integration tests on steroids.

So, we built an SDK that adds probes to the code in compile time. The SDK logs code execution, in detail.

Git: https://github.com/unloggedio/unlogged-sdk

We also built an IDE plugin that keeps monitoring code changes, hot reloads these changes, replays the relevant methods, and alerts on failing replays. It also lets developers call Java methods directly, mock downstream methods in run time, highlight code coverage in real-time, and show performance numbers for methods with inlay hints. (right above each method)

Git: https://github.com/unloggedio/intellij-java-plugin

We are excited to launch the first version of our product that replays with assertions + mocking + code coverage reports right inside the IDE.

Link to our IntelliJ plugin: https://plugins.jetbrains.com/plugin/18529-unlogged/

Record and Replay Demo: https://www.youtube.com/watch?v=muCyE-doEB0

Define Assertions on Replay: https://www.youtube.com/watch?v=YKsi1p634-M

Track Code Coverage: https://www.youtube.com/watch?v=NMmp954kfaU

Generate JUnit Test Cases: https://www.youtube.com/watch?v=rTUmg5b1Z_Q

Mocking when replaying: https://www.youtube.com/watch?v=O_aqU1u-Kmw

Documentation: http://read.unlogged.io/

Roadmap:

1. Create a production logger

Link to the source code: https://github.com/unloggedio/unlogged-sdk

will fix the link on the plugin page, thanks for noticing it.