CUDA.jl | hissp | |
---|---|---|
15 | 29 | |
1,133 | 331 | |
1.1% | - | |
9.5 | 9.1 | |
7 days ago | 3 months ago | |
Julia | Python | |
GNU General Public License v3.0 or later | Apache 2.0 |
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.
CUDA.jl
-
Ask HN: Best way to learn GPU programming?
It would also mean learning Julia, but you can write GPU kernels in Julia and then compile for NVidia CUDA, AMD ROCm or IBM oneAPI.
https://juliagpu.org/
I've written CUDA kernels and I knew nothing about it going in.
- What's your main programming language?
-
How is Julia Performance with GPUs (for LLMs)?
See https://juliagpu.org/
-
Yann Lecun: ML would have advanced if other lang had been adopted versus Python
If you look at Julia open source projects you'll see that the projects tend to have a lot more contributors than the Python counterparts, even over smaller time periods. A package for defining statistical distributions has had 202 contributors (https://github.com/JuliaStats/Distributions.jl), etc. Julia Base even has had over 1,300 contributors (https://github.com/JuliaLang/julia) which is quite a lot for a core language, and that's mostly because the majority of the core is in Julia itself.
This is one of the things that was noted quite a bit at this SIAM CSE conference, that Julia development tends to have a lot more code reuse than other ecosystems like Python. For example, the various machine learning libraries like Flux.jl and Lux.jl share a lot of layer intrinsics in NNlib.jl (https://github.com/FluxML/NNlib.jl), the same GPU libraries (https://github.com/JuliaGPU/CUDA.jl), the same automatic differentiation library (https://github.com/FluxML/Zygote.jl), and of course the same JIT compiler (Julia itself). These two libraries are far enough apart that people say "Flux is to PyTorch as Lux is to JAX/flax", but while in the Python world those share almost 0 code or implementation, in the Julia world they share >90% of the core internals but have different higher levels APIs.
If one hasn't participated in this space it's a bit hard to fathom how much code reuse goes on and how that is influenced by the design of multiple dispatch. This is one of the reasons there is so much cohesion in the community since it doesn't matter if one person is an ecologist and the other is a financial engineer, you may both be contributing to the same library like Distances.jl just adding a distance function which is then used in thousands of places. With the Python ecosystem you tend to have a lot more "megapackages", PyTorch, SciPy, etc. where the barrier to entry is generally a lot higher (and sometimes requires handling the build systems, fun times). But in the Julia ecosystem you have a lot of core development happening in "small" but central libraries, like Distances.jl or Distributions.jl, which are simple enough for an undergrad to get productive in a week but is then used everywhere (Distributions.jl for example is used in every statistics package, and definitions of prior distributions for Turing.jl's probabilistic programming language, etc.).
-
C++ is making me depressed / CUDA question
If you just want to do some numerical code that requires linear algebra and GPU, your best bet would be Julia or Python+JAX.
-
Parallélisation distribuée presque triviale d’applications GPU et CPU basées sur des Stencils avec…
GitHub - JuliaGPU/CUDA.jl: CUDA programming in Julia.
- Why Fortran is easy to learn
-
Generic GPU Kernels
Should have (2017) in the title.
Indeed cool to program julia directly on the GPU and Julia on GPU and this has further evolved since then, see https://juliagpu.org/
-
Announcing The Rust CUDA Project; An ecosystem of crates and tools for writing and executing extremely fast GPU code fully in Rust
I'm excited to eventually see something like JuliaGPU with support for multiple backends.
-
[Media] 100% Rust path tracer running on CPU, GPU (CUDA), and OptiX (for denoising) using one of my upcoming projects. There is no C/C++ code at all, the program shares a single rust crate for the core raytracer and uses rust for the viewer and renderer.
That's really cool! Have you looked at CUDA.jl for the Julia language? Maybe you could take some ideas from there. I am pretty sure it does the same thing you do here, and they support any arbitrary code with the limitations that you cannot allocate memory, I/O is disallowed, and badly-typed code(dynamic) will not compile.
hissp
- Hissp
-
2 line tic tac toe
Hissp is a Python library that can compile a whole program into one Python expression.
-
What's the most hilarious use of operator overloading you've seen?
If you want Python to be as customizable as Lissp, check out Hissp (and Hebigo).
-
Pythoneers here, what are some of the best python tricks you guys use when progrmming with python
Hissp is really cool for metaprogramming Python. There's also macropy, but it's harder to use.
-
Lush – Lisp-like language for deep learning designed by Yann LeCun
I prefer https://github.com/gilch/hissp, where Hy has to use shims to pretend statements are expressions, Hissp just targets the expression subset in the first place. (though as you mentioned, hy has a lot of literature and support around it, where as you're going to have to find your own way around hissp)
-
A Python-compatible statically typed language erg-lang/erg
No shortage of options, e.g. Dg, Mochi, Coconut, and Hebigo (based on Hissp[1]).
[1]: https://github.com/gilch/hissp
-
Other than having a wider range of libraries and beingthus being more "general purpose" and "practical" is there anything that makes Python an intrinsically better programming language than Lisp?
If you want Lisp metaprogramming plus Python ecosystem, check out Hissp
- Lisp.py
-
What are some amazing, great python external modules, libraries to explore?
Hissp is really interesting. Read through the docs and you'll understand Python more deeply. It works well with Toolz and Pyrsistent.
- Why Hy?
What are some alternatives?
LoopVectorization.jl - Macro(s) for vectorizing loops.
hy - A dialect of Lisp that's embedded in Python
cunumeric - An Aspiring Drop-In Replacement for NumPy at Scale
hy-lisp-python - examples for my book "A Lisp Programmer Living in Python-Land: The Hy Programming Language"
awesome-quant - A curated list of insanely awesome libraries, packages and resources for Quants (Quantitative Finance)
libpython-clj - Python bindings for Clojure
cudf - cuDF - GPU DataFrame Library
coalton - Coalton is an efficient, statically typed functional programming language that supercharges Common Lisp.
Tullio.jl - ⅀
femtolisp - a lightweight, robust, scheme-like lisp implementation
GPUCompiler.jl - Reusable compiler infrastructure for Julia GPU backends.
incanter - Clojure-based, R-like statistical computing and graphics environment for the JVM