ml5-library VS Flux.jl

Important APIs - ml5 for in-browser detection, face-api that uses tensorflow-node to accelerate on-server detection. VueUse for a bunch of useful component tools like the QR Code generator. Yahoo's Gifshot for creating gif files in-browser etc.

> Have we seen any creator of a deep learning library, take a similar position if not stopping any support for anyone using it for mass surveillance?

ml5.js license:

> This license gives everyone as much permission to work with this software as possible as long as they comply with the ml5.js Code of Conduct [...]

ml5.js code of conduct:

> Do not: [...] Use ml5.js to build tools of mass surveillance and prediction to repress the rights of people

https://github.com/ml5js/ml5-library/blob/main/LICENSE.md

Not sure how enforcable this is but it exists.

See also: https://ml5js.org/

"The library provides access to machine learning algorithms and models in the browser, building on top of TensorFlow.js with no other external dependencies."

(5) ml5.js

ML.js

I used ml5js.org , p5js.org and https://teachablemachine.withgoogle.com to train the Banana images. When you create a new image project on Teachable Machine, you can output the p5js and basically use it right out of the box - I customized js, css, and html from there.

Going forward: I'll be 100% into JavaScript. You can use JavaScript in so many fields nowadays. Websites React, Mobile Apps React Native, Machine Learning TensorFlow & ML5, Desktop Applications Electron, and of course the backend Node as well. It's kind of a no-brainer. Of course, they all have specific languages that are better, but for now, JavaScript is a bit of a catch-all.

Yeah they made ml5.js for this reason: https://ml5js.org/

I do feel like Google could do better communicating all of their different tools though. Their ecosystem is large and pretty confusing - they've got so many projects going on at once that it always seems like everyone gets fed up with them before they take a second pass and make them more friendly to newcomers.

Facebook seems to have taken a much more focused approach as you can see with PyTorch Live

From other comments, a lot of JavaScript developers who want to use TensorFlow had never heard of TensorFlow.js or ml5.js!

If you are really committed to running on Apple hardware then take a look at Tensorflow for macOS. Another option is the Julia programming language which has very basic Metal support at a CUDA-like level. FluxML would be the ML framework in Julia. I’m not sure either option will be painless or let you do everything you could do with a Nvidia GPU.

Flux dominance!

I’m no compiler expert but check out flux and zygote https://fluxml.ai/ https://fluxml.ai/

I would suggest you to look into Julia ecosystem instead of C++. Julia is almost identical to Python in terms of how you use it but it's still very fast. You should look into flux.jl package for Julia.

Give Julia a try: https://fluxml.ai

2) Flux treats softmax a little different than most other activation functions (see here for more details) such as relu and sigmoid. When you pass an activation function into a layer like Dense(3, 32, relu), Flux expects that the function is broadcast over the layer's output. However, softmax cannot be broadcast as it operates over vectors rather than scalars. This means that if you want to use softmax as the final activation in your model, you need to pass it into Chain() like so:

Can you point to a concrete example of one that someone would run into when using the differential equation solvers with the default and recommended Enzyme AD for vector-Jacobian products? I'd be happy to look into it, but there do not currently seem to be any correctness issues in the Enzyme issue tracker that are current (3 issues are open but they all seem to be fixed, other than https://github.com/EnzymeAD/Enzyme.jl/issues/278 which is actually an activity analysis bug in LLVM). So please be more specific. The issue with Enzyme right now seems to moreso be about finding functional forms that compile, and it throws compile-time errors in the event that it cannot fully analyze the program and if it has too much dynamic behavior (example: https://github.com/EnzymeAD/Enzyme.jl/issues/368).

Additional note, we recently did a overhaul of SciMLSensitivity (https://sensitivity.sciml.ai/dev/) and setup a system which amounts to 15 hours of direct unit tests doing a combinatoric check of arguments with 4 hours of downstream testing (https://github.com/SciML/SciMLSensitivity.jl/actions/runs/25...). What that identified is that any remaining issues that can arise are due to the implicit parameters mechanism in Zygote (Zygote.params). To counteract this upstream issue, we (a) try to default to never default to Zygote VJPs whenever we can avoid it (hence defaulting to Enzyme and ReverseDiff first as previously mentioned), and (b) put in a mechanism for early error throwing if Zygote hits any not implemented derivative case with an explicit error message (https://github.com/SciML/SciMLSensitivity.jl/blob/v7.0.1/src...). We have alerted the devs of the machine learning libraries, and from this there has been a lot of movement. In particular, a globals-free machine learning library, Lux.jl, was created with fully explicit parameters https://lux.csail.mit.edu/dev/, and thus by design it cannot have this issue. In addition, the Flux.jl library itself is looking to do a redesign that eliminates implicit parameters (https://github.com/FluxML/Flux.jl/issues/1986). Which design will be the one in the end, that's uncertain right now, but it's clear that no matter what the future designs of the deep learning libraries will fully cut out that part of Zygote.jl. And additionally, the other AD libraries (Enzyme and Diffractor for example) do not have this "feature", so it's an issue that can only arise from a specific (not recommended) way of using Zygote (which now throws explicit error messages early and often if used anywhere near SciML because I don't tolerate it).

So from this, SciML should be rather safe and if not, please share some details and I'd be happy to dig in.

> In his item #1, he links to https://discourse.julialang.org/t/loaderror-when-using-inter... The issue is actually a Zygote bug, a Julia package for auto-differentiation, and is not directly related to Julia codebase (or Flux package) itself. Furthermore, the problematic code is working fine now, because DiffEqFlux has switched to Enzyme, which doesn't have that bug. He should first confirm whether the problem he is citing is actually a problem or not.

> Item #2, again another Zygote bug.

If flux chose a buggy package as a dependency, that's on them, and users are well justified in steering clear of Flux if it has buggy dependencies. As of today, the Project.toml for both Flux and DiffEqFlux still lists Zygote as a dependency. Neither list Enzyme.

https://github.com/FluxML/Flux.jl/blob/master/Project.toml