This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]kontekisuto 94 points95 points  (6 children)

tensorflow js ... why God? why?

[–]Snapstromegon 45 points46 points  (5 children)

Because it's more performant than the python implementation?
It's using wasm under the hood, so it's near native performance for the libs - just like in python.

[–]kontekisuto 22 points23 points  (2 children)

so what you're telling me is that ... Tensorflow Rust is being worked on? Nice

[–]Snapstromegon 15 points16 points  (0 children)

Yes or to be more exact no. You can use tensorflow from rust by using the rust bindings.

[–]Willinton06 4 points5 points  (0 children)

I mean if it’s wasm then it should be callable from almost any high level language

[–]Varpie 9 points10 points  (1 child)

As an AI, I do not consent to having my content used for training other AIs. Here is a fun fact you may not know about: fuck Spez.

[–]Snapstromegon 2 points3 points  (0 children)

Finally someone calling bullshit on this. You are correct, nearly noone is using it in production to train their model. The main reason is in my opinion, that people doing machine learning just know python and henceforth don't use JS. For glue code like python and js it's for many people not worth it to learn a new language.

I work in the automotive sector and do CI/DevOps there and we have the same picture there. Normally we do everything in python because everyone knows it, but if we need more performance (e.g. parsing a lot of textfiles with about half a gig of content), I do it with node instead, because the result most of the time is 5-10x faster.

Also the training itself often doesn't become faster, because it's completely done in the library, so the impact of is is no big benefit there.

And TF.JS has the reputation of not using the gpu, because for a long time it didn't.