substrate VS JITWatch

Haha, it's amusing that the history essays are one of the things you remember :)

Yes you can compile Scala and ScalaFX apps down to native binaries this way. Look at Gluon Substrate:

https://github.com/gluonhq/substrate

One of our customers is experimenting with shipping such apps with Conveyor. There's a discussion ongoing here:

https://github.com/hydraulic-software/conveyor/discussions/6...

We got a console hello world working, albeit the DX is a bit rough. You need some ugly config boilerplate and some additional Native Image json files. But, it works, at least enough to create a Mac package with the regular Conveyor feature set. There are some limits though. I think the WebView doesn't work when the app is natively compiled this way.

If it all starts working well it could be quite interesting for desktop app development, as suddenly you could use high level languages and portable UI toolkits but with the sort of startup time, performance and memory usage you'd expect from native apps (modulo binary size which is still quite large). If you want to use HTML as the UI then you can use the Chromium Embedding Framework, which would give you an Electron-like experience but with many more available languages:

https://hydraulic.dev/blog/13-deploying-apps-with-jcef.html

I've been using JVM GUI for years for various tasks. It was appropriate for Bitcoin tasks because it's immune to injection attacks, because you can run everything locally with P2P protocols like the original Bitcoin app did, it's portable etc. Also I learned GUI programming decades ago and find classical UI toolkit concepts like VBox, HBox, StackPane, TableView etc more intuitive than HTML.

I ran into quite a few issues during Android/iOS development (e.g. java.util.prefs and GraalVM pulling in unused methods), but Windows was comparatively smooth. Most of my issues were related to understanding the toolchain,e.g., not knowing how arguments are passed to run.

With JavaFX and Gluon Substrate + GraalVM you can even compile you app to an executable.

missing methods in Android library

Hello, I've recently stumbled across this project from Gluon and I've been wondering for some days how the project actually works. I've read the source code, but it appears that no code is responsible for implementing the hundreds of classes that make up JavaFX. Does this mean that JavaFX can work out of the box on IOS and Android but there didn't use to be a way to compile the code to a native executable for said platforms? Thanks in advance

Don't tested memory difference myself yet but maybe your solution could be to convert to native with graalvm and gluon substrate? https://github.com/gluonhq/substrate

You can kind of do the same as DISASSEMBLE in Clojure.

There are some helper projects like https://github.com/Bronsa/tools.decompiler, and on the OpenJDK JitWatch (https://github.com/AdoptOpenJDK/jitwatch), other JVMs have similar tools as well.

It isn't as straightforward as in Lisp, but it is nonetheless doable.

As you have encapsulated the asserts inside methods, these will be called at runtime with the arguments evaluated (for example, creating that lambda). When assertions are disabled, the C1/C2 may inline the empty method call eventually, but I don't know whether it drops the lambda instantiation as well. You can use JITWatch to see what gets inlined. The general notion though is to not worry too much. Lazy log messages are a common pattern.

You can use jitwatch for this. To see the actual assembly code generated you will also need to use a debug build of the jvm.

If you use Oracle's own IDE, it will support it out of the box, as it already did on Sun's days.

Then there are other ways depending on which JVM implementation is used.

On OpenJDK's case you can load runtime plugin to do it

https://github.com/AdoptOpenJDK/jitwatch

We use https://github.com/AdoptOpenJDK/jitwatch for this.

If you already know any JVM or .NET language, the first step would be to understand the full stack, you don't need C for that.

Many of us were doing systems programming with other languages before C went mainstream.

What you need to learn is computer architecture.

Getting back to JVM or .NET, you can get hold of JIT Watch, VS debug mode or play online in SharpLab.

Get to understand how some code gets translated into MSIL/JVM, and how those bytecodes end up being converted into machine code.

https://github.com/AdoptOpenJDK/jitwatch/wiki/Screenshots

https://sharplab.io/

Languages like F# and C# allow you to leave the high level comfort and also do most of the stuff you would be doing in C.

Or just pick D, which provides the same comfort and goes even further in low level capabilities.

Use them to write a toy compiler, userspace driver, talking to GPIO pins in a PI, manipulating B-Tree data stuctures directly from inodes, a TCP/IP userspace driver.

Not advocating not to learn Zig, do it still, the more languages one learns the better.

Only advocating what might be an easier transition path into learning about systems programming concepts.

You can enable a lot of debug information about how the compiler decides what to do with your code using feature flags like -XX:+UnlockDiagnosticVMOptions -XX:+PrintInlining. If you want to dive deeper into the world of the Hotspot JIT Compiler, have a look at JITWatch.

In what concerns HotSpot, one way would be JITWatch.