That’s frankly mind blowing. About as much as parallel-collections gaining support for scala-native in the recent days, with the PR not even touching a single line of code (only through build configuration). The scala ecosystem is way under-appreciated :-)
Indeed so. I also intend (eventually) to try running my model with scala-native - a purpose could be to ‘pipe’ runs connected with other climate model / tools (mostly written in python nowadays) for probabilistic analyses over thousands of scenarios (as I used to do with my old java JCM from which SWIM descends). So both native and wasm offer ways to connect with other languages (without any jvm). But for such complex systems modeling it’s great to rely on the intelligence of scala compiler (and metals, as typing) - basically if it compiles it usually runs correctly, the graphical image with all the plots is my main ‘test’.
That’s frankly mind blowing. About as much as parallel-collections gaining support for scala-native in the recent days, with the PR not even touching a single line of code (only through build configuration). The scala ecosystem is way under-appreciated :-)
Indeed so. I also intend (eventually) to try running my model with scala-native - a purpose could be to ‘pipe’ runs connected with other climate model / tools (mostly written in python nowadays) for probabilistic analyses over thousands of scenarios (as I used to do with my old java JCM from which SWIM descends). So both native and wasm offer ways to connect with other languages (without any jvm). But for such complex systems modeling it’s great to rely on the intelligence of scala compiler (and metals, as typing) - basically if it compiles it usually runs correctly, the graphical image with all the plots is my main ‘test’.