DifferentialEquations.jl
femtolisp
Our great sponsors
DifferentialEquations.jl | femtolisp | |
---|---|---|
6 | 10 | |
2,754 | 1,550 | |
1.5% | - | |
7.3 | 0.0 | |
16 days ago | about 4 years ago | |
Julia | Scheme | |
GNU General Public License v3.0 or later | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
DifferentialEquations.jl
-
Startups are building with the Julia Programming Language
This lists some of its unique abilities:
https://docs.sciml.ai/DiffEqDocs/stable/
The routines are sufficiently generic, with regard to Julia’s type system, to allow the solvers to automatically compose with other packages and to seamlessly use types other than Numbers. For example, instead of handling just functions Number→Number, you can define your ODE in terms of quantities with physical dimensions, uncertainties, quaternions, etc., and it will just work (for example, propagating uncertainties correctly to the solution¹). Recent developments involve research into the automated selection of solution routines based on the properties of the ODE, something that seems really next-level to me.
[1] https://lwn.net/Articles/834571/
-
From Common Lisp to Julia
https://github.com/SciML/DifferentialEquations.jl/issues/786. As you could see from the tweet, it's now at 0.1 seconds. That has been within one year.
Also, if you take a look at a tutorial, say the tutorial video from 2018,
-
When is julia getting proper precompilation?
It's not faith, and it's not all from Julia itself. https://github.com/SciML/DifferentialEquations.jl/issues/785 should reduce compile times of what OP mentioned for example.
-
Julia 1.7 has been released
Let's even put raw numbers to it. DifferentialEquations.jl usage has seen compile times drop from 22 seconds to 3 seconds over the last few months.
https://github.com/SciML/DifferentialEquations.jl/issues/786
- Suggest me a Good library for scientific computing in Julia with good support for multi-core CPUs and GPUs.
-
DifferentialEquations compilation issue in Julia 1.6
https://github.com/SciML/DifferentialEquations.jl/issues/737 double posted, with the answer here. Please don't do that.
femtolisp
- Petalisp: Elegant High Performance Computing
- fe: A tiny, embeddable language implemented in ANSI C
-
From Common Lisp to Julia
> In short, Julia is very similar to Common Lisp, but brings a lot of extra niceties to the table
This probably because Jeff Bezanson, the creator of Julia, created a Lisp prior to Julia, which I think still exists inside Julia in some fashion
https://github.com/JeffBezanson/femtolisp
-
Modern Python Performance Considerations
Well let's flip this around: do you think you could write a performant minimal Python in a weekend? Scheme is a very simple and elegant idea. Its power derives from the fact that smart people went to considerable pains to distill computation to limited set of things. "Complete" (i.e. rXrs) schemes build quite a lot of themselves... in scheme, from a pretty tiny core. I suspect Jeff Bezanson spent more than a weekend writing femtolisp, but that isn't really important. He's one guy who wrote a pretty darned performant lisp that does useful computation as a passion project. Check out his readme; it's fascinating: https://github.com/JeffBezanson/femtolisp
You simply can't say these things about Python (and I generally like Python!). It's truer for PyPy, but PyPy is pretty big and complex itself. Take a look at the source for the scheme or scheme-derived language of your choice sometime. I can't claim to be an expert in any of what's going on in there, but I think you'll be surprised how far down those parens go.
The claim I was responding to asserted that lisps and smalltalks can only be fast because of complex JIT compiling. That is trueish in practice for Smalltalk and certainly modern Javascript... but it simply isn't true for every lisp. Certainly JIT-ed lisps can be extremely fast, but it's not the only path to a performant lisp. In these benchmarks you'll see a diversity of approaches even among the top performers: https://ecraven.github.io/r7rs-benchmarks/
Given how many performant implementations of Scheme there are, I just don't think you can claim it's because of complex implementations by well-resourced groups. To me, I think the logical conclusion is that Scheme (and other lisps for the most part) are intrinsically pretty optimizable compared to Python. If we look at Common Lisp, there are also multiple performant implementations, some approximately competitive with Java which has had enormous resources poured into making it performant.
-
CppCast: Julia
While it uses an Algol inspired syntax, it has the same approach to OOP programing as CLOS(Common Lisp Object System), with multi-methods and protocols, it has a quite powerfull macro system like Lisp, similar REPL experience, and underneath it is powerered by femtolisp.
- Julia and the Incarceration of Lisp
-
What is the smallest x86 lisp?
For a real answer, other replies have already mentioned KiloLisp, but there's also femtolisp. Also, not exactly what you're asking for, but Maru is a very compact and elegant self-hosting lisp (compiles to x86).
-
lisp but small and low level?Does it make sense?
Take a look at femtolisp It has some low level features and is quite small. There is also a maintenance fork at lambdaconservatory
-
Lispsyntax.jl: A Clojure-like Lisp syntax for julia
A fun Julia easter egg I recently discovered.
Running 'julia --lisp' launches a femtolisp (https://github.com/JeffBezanson/femtolisp) interpreter.
-
Wisp: A light Lisp written in C++
Reminds me of the femtolisp README :)
Almost everybody has their own lisp implementation. Some programmers' dogs and cats probably have their own lisp implementations as well. This is great, but too often I see people omit some of the obscure but critical features that make lisp uniquely wonderful. These include read macros like #. and backreferences, gensyms, and properly escaped symbol names. If you're going to waste everybody's time with yet another lisp, at least do it right damnit.
https://github.com/JeffBezanson/femtolisp
What are some alternatives?
ModelingToolkit.jl - An acausal modeling framework for automatically parallelized scientific machine learning (SciML) in Julia. A computer algebra system for integrated symbolics for physics-informed machine learning and automated transformations of differential equations
small-lisp - A very small lisp interpreter, that I may one day get working on my 8-bit AVR microcontroller.
diffeqpy - Solving differential equations in Python using DifferentialEquations.jl and the SciML Scientific Machine Learning organization
julia - The Julia Programming Language
Gridap.jl - Grid-based approximation of partial differential equations in Julia
Carp - A statically typed lisp, without a GC, for real-time applications.
ApproxFun.jl - Julia package for function approximation
Fennel - Lua Lisp Language
DiffEqBase.jl - The lightweight Base library for shared types and functionality for defining differential equation and scientific machine learning (SciML) problems
sectorlisp - Bootstrapping LISP in a Boot Sector
FFTW.jl - Julia bindings to the FFTW library for fast Fourier transforms
hissp - It's Python with a Lissp.