RecursiveArrayTools.jl
ObjectOriented.jl
RecursiveArrayTools.jl | ObjectOriented.jl | |
---|---|---|
3 | 4 | |
202 | 88 | |
2.5% | - | |
9.4 | 5.3 | |
7 days ago | 3 months ago | |
Julia | Julia | |
GNU General Public License v3.0 or later | MIT 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.
RecursiveArrayTools.jl
-
Julia's latency: Past, present and future
You're not really supposed to be using StaticArraysCore anymore, but here's a somewhat older PR that shows the siginificance of moving StaticArray functionality on a smaller library, moving it from 6228ms to 292ms load time (https://github.com/SciML/RecursiveArrayTools.jl/pull/217).
-
Julia 1.8 has been released
> > This gives the package authors a tool to basically "profile" the loading time of their package, which will help them optimize the loading time. So there _will_ be downstream improvement to package loading for us users too.
It lead to https://github.com/SciML/RecursiveArrayTools.jl/pull/217 . 6228.5 ms to 292.7 ms isn't too shabby.
-
“Why I still recommend Julia”
The load times on some core packages were reduced by an order of magnitude this month. For example, RecursiveArrayTools went from 6228.5 ms to 292.7 ms. This was due to the new `@time_imports` in the Julia v1.8-beta helping to isolate load time issues. See https://github.com/SciML/RecursiveArrayTools.jl/pull/217 . This of course doesn't mean load times have been solved everywhere, but we now have the tooling to identify the root causes and it's actively being worked on from multiple directions.
ObjectOriented.jl
-
With v1.9 about to land, what do you hope v1.10 has?
Not being an expert in Julia, I reckon that whatever https://github.com/Suzhou-Tongyuan/ObjectOriented.jl does, also included meeting around with language internals. It's macros in Julia but what is the real difference?
-
Julia 1.8 has been released
> And if that’s what you want to stick to, I guess you could program in that style by making the “object” the first method argument, and wrapping the functions along with the struct definition in a module.
You might not even need to do that. This package was released recently, implementing OOP: https://github.com/Suzhou-Tongyuan/ObjectOriented.jl
- Objectoriented.jl: a mechanical OOP programming library based on CPython OOP
What are some alternatives?
arrow-julia - Official Julia implementation of Apache Arrow
ProtoStructs.jl - Easy prototyping of structs
SciMLStyle - A style guide for stylish Julia developers
Lux.jl - Explicitly Parameterized Neural Networks in Julia
ITensors.jl - A Julia library for efficient tensor computations and tensor network calculations
TruncatedStacktraces.jl - Simpler stacktraces for the Julia Programming Language
SciMLSensitivity.jl - A component of the DiffEq ecosystem for enabling sensitivity analysis for scientific machine learning (SciML). Optimize-then-discretize, discretize-then-optimize, adjoint methods, and more for ODEs, SDEs, DDEs, DAEs, etc.
SciPy - SciPy library main repository
Flux.jl - Relax! Flux is the ML library that doesn't make you tensor