# State of machine learning in Julia

**URL:** https://discourse.julialang.org/t/state-of-machine-learning-in-julia/74385
**Category:** Machine Learning
**Created:** [January 11, 2022, 10:39am UTC](https://discourse.julialang.org/t/state-of-machine-learning-in-julia/74385 "2022-01-11T10:39:27Z")
**Posts on this page:** 1
**Showing post:** 10

<div class="post-metadata">

### Author: ![jlapeyre](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jlapeyre/32/4514_2.png) [@jlapeyre](https://discourse.julialang.org/u/jlapeyre)
#### Post date: [January 11, 2022, 9:01pm UTC](https://discourse.julialang.org/t/state-of-machine-learning-in-julia/74385/10 "2022-01-11T21:01:58Z")

</div>

> [@patrick-kidger](#):
>
> Special syntax for implicitly re-striding an array just seems a little odd to me. I don’t think I’ve ever done it deliberately in either Python or Julia.

It is used it in a fair amount of Julia code. I’ve used it. It’s handy, and it’s clear what’s happening.

But, obviously, this is the least important of your criticisms.

I am trying to find a robust way to deploy Julia inside a python project. People have put a ton of work into Julia-Python interop in general. But, the parts closer to deployment are not there yet. It would be a great place for people to lend a hand. (This has been known for long time.) But, it has to compete with the other pressing issues you mentioned.

---

_[View the full topic](https://discourse.julialang.org/t/state-of-machine-learning-in-julia/74385)._