I completely disagree, the browser is the worst platform for scientific computing. However, with Julia language you can also run ganja.js (i have a Ganja.jl package but dont maintain it much) and with javascript in Julia, you can launch a browser window from Julia, to display a javascript. However, I don’t personally need javascript, as I am able to work with the Julia language and visualize results without that.
My interface is the Julia language, I believe that the most important features are the algorithms and language design itself, and the ideal way to do an engineering scientific computation session is in a command line interface with a visualization tool like Makie.jl available. You can have direct access to all the functions and API to manipulate data and feed it into a plotting or experiment an algorithm by defining a function and evaluating it.
With a graphical user interface instead of a command line interface, you are very restricted and limited in what you can do, compared to directly accessing the data and algorithms and plotting API.
If you use a separate CAD software, a separate physics solver software, a separate data visualization software, etc, then it is not a unified interface.
In my approach everything is fully unified with geometric algebra every step of the way, from generating the geometry with Grassmann.jl, then computing the PDE solutions with Grassmann.jl, and then using Grassmann.jl to facilitate into the visualization step as well.
By using the Julia language, I can easily interface with MATLAB or Mathematica as well, and I have access to the full Grassmann.jl geometric algebra every step of the way.
My philosophy is that a graphical user imterface can always be implemented as an after thought, as long as I already created the necessary API. The user interface should be the last step in such a project.
I’m not exactly sure what you mean, I work directly with the mesh topology including the boundary, I have a language design to deal with that. Either I generate my own geometry from scratch, or I can import it from another source, such as MATLAB or other Julia packages. Other Julia packages may support importing certain file types, and then the imported data could be transformed into the format that I personally designed for my purposes.
I am just using basic and standard finite element procedures, except that every step of the way it is built on top of Grassmann.jl geometric algebra, enabling the immediate manipulation of results with exterior algebra or the geometric product, so that those results can immediately be plotted, and everything is unified tensor algebra along each step.
However, I will not be going into great detail about how I approach all this on a public chat. Perhaps someday I will document these features, when I decide it is appropriate. The only way to learn about these features is if there is a good reason or purpose for me to explain it to someone. Currently, there are no good reasons to explain this stuff to anyone, so I will only make vague statements about my work.
Explaining all this stuff and teaching it is an entire job of itself, a thankless job, where other people will copy and imitate me and they refuse to give attribution. So there is no reason to fully reveal this stuff for now.
As far as splines go, I know a person who has used Grassmann.jl in combination with CUDA to do high performance computing with splines, the person has not published any of the code for that yet.