7 ms·
Im not sure if Julia will ever take off. Right now there are huge investments in the AI space and Julia has no presence in those.
by chestertn 3y ago
Im not sure if Julia will ever take off. Right now there are huge investments in the AI space and Julia has no presence in those.
- affinepplan 3y agojulia has already taken off for certain niches
- spenczar5 3y agoWhat is an example? Are there any where it is dominant?
- affinepplan 3y agoscientific models and simulations can be and are made very successfully in julia. In particular the diffeq landscape is probably the languages largest comparative advantage
- spenczar5 3y agoThat’s a broad area. I work in astrodynamic simulations, and don’t know anyone doing much work in Julia. Maybe a couple of grad students playing with it, but that’s it. 99% of the work is Python, Fortran, and C/C++. Are there subdomains that use it a lot? I am not sure what the diffeq landscape is exactly although it sounds related to dynamical simulations?
- affinepplan 3y agoI'm sure there are other subdomains that make use of Julia, but in particular I think if your problem involves writing an evolution-like or agent-based-model-like simulation you may find the strengths of Julia particularly compelling
- lagrange77 3y agoI recently found this: https://github.com/JuliaSpace/ https://github.com/JuliaSpace/ Out of curiosity, what Python, Fortran, and C/C++ packages do you use / can you recommend?
- spenczar5 3y agoAstropy [0] lives at the heart of most work. It has a Python interface, often backed by Fortran and C++ extension modules. If you use Astropy, you're indirectly using libraries like ERFA [6] and cfitsio [7] which are in C/Fortran. I personally end up doing a lot of work that uses the HEALPix sky tesselation, so I use healpy [2] as well. Openorb is perhaps a good example of a pure-Fortran package that I use quite frequently for orbit propagation [3]. In C, there's Rebound [4] (for N-body simulations) and ASSIST [5] (which extends Rebound to use JPL's pre-calculated positions of major perturbers, and expands the force model to account for general relativity). There are many more, these are just ones that come to mind from frequent usage in the last few months. ---- [0] https://www.astropy.org/ https://www.astropy.org/ [1] https://healpix.jpl.nasa.gov/ https://healpix.jpl.nasa.gov/ [2] https://healpy.readthedocs.io/en/latest/ https://healpy.readthedocs.io/en/latest/ [3] https://github.com/oorb/oorb https://github.com/oorb/oorb [4] https://rebound.readthedocs.io/en/latest/ https://rebound.readthedocs.io/en/latest/ [5] https://github.com/matthewholman/assist https://github.com/matthewholman/assist [6] https://github.com/liberfa/erfa https://github.com/liberfa/erfa [7] https://heasarc.gsfc.nasa.gov/fitsio/ https://heasarc.gsfc.nasa.gov/fitsio/
- lagrange77 3y agoThank you very much for the detailed answer! Will look into those. I recently wrote a little n-body simulator to become familiar with Julia's DifferentialEquations.jl and that motivated me to learn more about astrodynamics.
- chestertn 3y agoOne of the things I don't like about the Julia ecosystem is the monolithic libraries that have tons of dependencies. DiffEq is one of those. I think its fine to write a script but if you want to develop something more sophisticated, you want to keep your dependencies lean.
- krull10 3y agoYou can always (slightly) reduce the DiffEq dependencies by adding OrdinaryDiffEq.jl instead of the meta DifferentialEquations.jl package. But lots of those dependencies arise from supporting modular functionality (changing BLAS, linear solvers, Jacobian calculation methods, in vs. out of place workflows, etc.). That said, the newer extension functionality may let more and more of the dependencies get factored out into optional extensions as time goes on.
- chestertn 3y agoI think it’s also the design philosophy. JuMP and ForwardDiff are great success stories and are packages very light on dependencies. I like those. The DiffEq library seems to pull you towards the SciML ecosystem and that might not be agreeable to everyone. For instance a known Julia project that simulates diff equations seems to have implemented their own solver https://github.com/CliMA/Oceananigans.jl https://github.com/CliMA/Oceananigans.jl
- ChrisRackauckas 3y agoThat's a bit different, and an interesting different. Certain types of partial differential equations like the one solved there generally use a form of step splitting (i.e. a finite volume method with a staggard grid). Those don't map cleanly into standard ODE solvers since you generally want to use a different method on one of the equations. It does map into the SplitODEProblem form as a not DynamicalODEProblem, and so there is a way to represent it, but we have not created optimized time stepping methods for that. But I work with those folks so I understand their needs and we'll be kicking off a new project in the MIT Julia Lab in the near future to start developing split step and multi-rate methods specifically for these kinds of PDEs. It's an interesting space because: -(a) there aren't really good benchmarks on the full set of options, so a benchmarking paper would be interesting to the field (which then gives a motivation to the software development) -(b) none of the implementations I have seen used the detailed tricks from standard stiff ODE solvers and so there's some major room for performance improvements -(c) there's some alternative ways to generate the stable steppers that haven't been explored, and we have some ideas for symbolic-numeric methods that extend the ideas of what people have traditionally done by hand here. That should. so we do plan to do things in the future. And having Oceananigans is then great because it serves as a speed-of-light baseline: if you auto-generate an ocean model, do you actually get as fast as a real hand-optimized ocean model? That's the goal, and we'll see if we can get there. We have tons of solvers, but you always need more!
- pjmlp 3y agoPlenty of examples, https://juliahub.com/case-studies/ https://juliahub.com/case-studies/
- passion__desire 3y agoYou don't need Julia. Julia was trying to be a better python. We will have better python in form of Mojo.
- FridgeSeal 3y agoMojo is vapourware from a private company (and we all know how those turn out re programming languages) until proven otherwise.
- csjh 3y agoWhat other private company languages are there? Swift is the best example I can think of, which matches Mojo's situation down to the head of the project.
- ReleaseCandidat 3y agoIBM has some, ABAP, ...
- Conscat 3y agoK is one such language.
- dist-epoch 3y agoMathematica
- deleted 3y ago[deleted]
- sinkwool 3y agoaren't most languages invented and initially developed within a private company? Go, Dart, Java, JavaScript, C#, F#, VBA, Kotlin, Erlang, C(at AT&T), Rust (at Mozilla). The list is probably very long
- notthemessiah 3y ago
- jakobnissen 3y agoAs much as it pains me to say it, I don't think Julia will. It looks to me like the practical problems with Julia, while addressable, are being addressed too slowly. There is simply too many rough edges and usability problems as it is now, and at the current pace it will take maybe 10 or 15 years to address them. On the other hand, the major use case for Julia is to have a fast, dynamic language. And it seems to me the time horizon for Python to become fast, or Rust or C++ to become dynamic is indefinite, so Julia is still the best bet in that space.
- __s 3y agoWhat's wrong with JS/TS or Lua as a fast dynamic language?
- jakobnissen 3y agoJavascript doesn't compile to native code, so isn't as fast. I've never tried LuaJIT, though, that's supposed to be on par with Julia.
- ReleaseCandidat 3y ago> Javascript doesn't compile to native code, so isn't as fast. There are AOT compilers for JS.
- jakobnissen 3y agoSo there is for Python, but it's still slow. JS has slow semantics. It can't be made in the same performance league as Julia.
- yabbs 3y agoI think you mean Julia is on par with LuaJIT? ..maybe exceeds?
- markkitti 3y agoOne of my favorite things recently is using JS/TS with Julia, usually via a Pluto.jl notebook. There are also some nice demonstrations showing Julia compiled to web assembly. https://tshort.github.io/WebAssemblyCompiler.jl/stable/examples/lorenz/?p1=9.6 https://tshort.github.io/WebAssemblyCompiler.jl/stable/examp...
- ReleaseCandidat 3y agoIt has already taken off and found its not so small niche. I don't think it will ever be one of the "big 10" languages (by users), but it has already a _big_ user base.
- pjmlp 3y agoJulia is flying for these folks already, https://juliahub.com/case-studies/ https://juliahub.com/case-studies/
- chestertn 3y agoThat page is a bit marketing
- pjmlp 3y agoNo different from the usual rewrite in Zig and Rust articles on HN, and more industry relevant.
- ChrisRackauckas 3y agoAny page like that which is industry relevant is going to have to be associated with a company because you need the marketing team to go through the effort to get the case studies approved by each and every company. It's not an easy process since for example something like the Instron case study (https://juliahub.com/case-studies/auto-crash-simulation/ https://juliahub.com/case-studies/auto-crash-simulation/) has details of upcoming projects like the Catapult Light which are major cost improvements passed on to customers, but you then have to go through the whole process of "well should we share this and let our competitors know what we used to get this advantage?" and contracts have to be signed before such a page can ever be built. The JuliaHub website has a whole list of case studies which have undergone this process and I couldn't see how you would get such detailed industrial accounts otherwise. For open source accounts, there's the SciML showcase page https://sciml.ai/showcase/ https://sciml.ai/showcase/. Thats very focused in just one domain though, and I tend to just update it with what I remember to put in there so it probably only has about 1/4 of the blogs and news articles that it should, and the "External Applications Libraries and Large Projects using SciML" part is woefully incomplete, but at least it gives a picture of what's going on. It's hard to keep those kinds of pages up to date because exponential growth means that page requires exponential work.
- systems 3y agoJulia need good a complete database connectivity libraries to do better they need to have full support for MS SQL and Oracle and other commercial dbs All my data are in a database, Julia need to become more db oriented , that is it
- markkitti 3y agoAre there solid C interfaces that can be used? A large part of why I started using Julia is because calling into other languages through the C FFI is pretty easy and efficient. Most of the wrappers are a single line. If there is not existing driver support, I would pass the C headers through Clang.jl, which automatically wraps the C API in a C header. https://github.com/JuliaInterop/Clang.jl https://github.com/JuliaInterop/Clang.jl I most recently did this with libtiff. Here is the Clang.jl code to generate the bindings. It's less than 30 lines of sterotypical code. https://github.com/mkitti/LibTIFF.jl/tree/main/gen https://github.com/mkitti/LibTIFF.jl/tree/main/gen The generated bindings with a few tweaks is here: https://github.com/mkitti/LibTIFF.jl/blob/main/src/LibTIFF.jl https://github.com/mkitti/LibTIFF.jl/blob/main/src/LibTIFF.j...
- pjmlp 3y agoYes, both Oracle (OCI) and SQL Server (ODBC), although they are quite a bit low level.
- kloch 3y agoI love Julia language for the seamless arbitrary precision math support and not much else. If we could get that in C I would be all set.
- notthemessiah 3y agoJulia was ahead of the game with automatic differentiation which took a few years for Python to get support. And it's still ahead of the game with integrating machine learning with scientific modeling. Macros and multiple dispatch are a game changer, and it allows people to hack and iterate on Julia far easier than on Python. And don't get me started on how nice JuMP.jl is for mathematical optimization.
- 6gvONxR4sf7o 3y ago> Julia was ahead of the game with automatic differentiation which took a few years for Python to get support. In what way is this true? Looks like Julia didn't exist until 2012. If I remember correctly, theano was the big AD thing in python at that point.
- notthemessiah 3y agoTheano existed, but it didn't use autodiff at the time, most loss functions had preprogrammed derivative functions. Python first had native autodiff in June of 2013 with the ad package, but previously had bindings to Fortran and C++ libraries that supported autodiff in different use cases. Julia first had native autodiff in April of 2013 with ForwardDiff.jl.
- 6gvONxR4sf7o 3y agoIt seems overly nitpicky to differentiate (no pun intended) so much between forward mode AD with DiffRules and theano's specific flavor of symbolic differentiation, but I'm no expert there.
- 7thaccount 3y agoJuMP is cool, but honestly...I find the native Python APIs from CPLEX & GUROBI to be best. The additional abstraction of JuMP or the Python equivalent frameworks always is a pain to me as I don't need to switch solvers often.