←back to thread

490 points jarmitage | 1 comments | | HN request time: 0.309s | source
Show context
raytopia ◴[] No.40681705[source]
I love how many python to native/gpu code projects there are now. It's nice to see a lot of competition in the space. An alternative to this one could be Taichi Lang [0] it can use your gpu through Vulkan so you don't have to own Nvidia hardware. Numba [1] is another alternative that's very popular. I'm still waiting on a Python project that compiles to pure C (unlike Cython [2] which is hard to port) so you can write homebrew games or other embedded applications.

[0] https://www.taichi-lang.org/

[1] http://numba.pydata.org/

[2] https://cython.readthedocs.io/en/stable/

replies(8): >>40681794 #>>40681883 #>>40681919 #>>40682488 #>>40684037 #>>40685851 #>>40686919 #>>40693004 #
pjmlp ◴[] No.40684037[source]
I would rather that Python catches up with Common Lisp tooling in JIT/AOT in the box, instead of compilation via C.
replies(3): >>40684186 #>>40684624 #>>40686404 #
crabbone[dead post] ◴[] No.40684624[source]
[flagged]
pjmlp ◴[] No.40685156[source]
Unfortunately there are folks that believe we have to use Python, and then rewrite in C, while calling those wrappers "Python" libraries, regardless of how much I would like to use JVM or CLR instead.

So if Python has taken Lisp's place in AI, I would rather that it also takes the JIT and AOT tooling as well.

replies(2): >>40685224 #>>40686949 #
math_dandy ◴[] No.40686949[source]
PyTorch and JAX have very good — but narrowly scoped — compilation facilities, and this suffices for a lot of really compelling AI applications.

A strong general purpose compilation story for Python is unlikely to materialize, IMO.

replies(1): >>40688308 #
pjmlp ◴[] No.40688308[source]
The pressure from slow and steady Julia's adoption, Mojo arriving into the scene, Facebook and Microsoft jumping into the JIT story, changing CPython team opinion on the matter, still leaves some hopes it might happen.

However now having Pytorch, Tensorflow and ONMX exposing the underylying native libraries to more programming languages, might mean to leave Python as it is, and use the other programming stacks for production.

replies(1): >>40729042 #
1. math_dandy ◴[] No.40729042[source]
I’m very excited about Mojo as a Rust 2.0 with first-class Python compatibility and support. Who knows if it’ll take off, but I love the project’s ideas and respect its ambition.