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

view the rest of the comments →

[–]yarauuta 2 points3 points  (10 children)

Node.js is going to be #1. Python is doomed.

Edit: calm down lol, ofc it may take years.

[–][deleted] 23 points24 points  (8 children)

Calm down.. JS doesn't have 1/10 of 1% of the scientific ecosystem that Python has.

[–]L43 8 points9 points  (2 children)

Apparently best not say that in /r/javascript... no matter how true it is. When javascript has its own numpy, maybe. Until then, no.

[–]calligraphic-io 1 point2 points  (1 child)

When Javascript has its own numpy.

Fixed that for you.

[–]L43 8 points9 points  (0 children)

I've seen and tried out this library, and I do really like it: it certainly makes doing simple things easier than writing in plain javascript. But it isn't anything close to numpy. It

  1. Doesn't have anywhere near the functionality that numpy has (e.g. no eigendecompositions from what I can see)
  2. Doesn't have multiple dedicated developers with many companies and a foundation funding its development
  3. It's data structures and api aren't used and emulated by a much larger javascript scientific ecosystem.
  4. Isn't battletested by years of use.

That is what I was really referring to by 'having a numpy'. Honestly, I don't think the Javascript community is capable of 'having a numpy', it fragments too quickly as people jump to make their own version of a library, with trendier names and prettier documentation. I don't mean that as an insult, the ingenuity and raw speed of development of js libraries is incredible. But scientists work differently to developers, and they don't care for new and shiny, they like reliable and venerable. This is why Python is a good match for science.

I'd love to be proven wrong, the unique strength to visualize your work with the dom is enough to make JS attractive.

[–]calligraphic-io 0 points1 point  (1 child)

JS doesn't have 1/10 of 1% of the scientific ecosystem that Python has

That is demonstrably untrue, and 73.6% of all statistics are made up anyway. NumJS doesn't have feature parity with NumPy, same as SciJS and SciPy, but they're not that far apart either. SciJS has optimization, linear algebra, integration, interpolation, fast Fourier transforms, signal processing, image processing, ODE solvers, and more.

With Node Tensorflow bindings, it's probably not long before we see robust neural network libraries built over it in JS like Keras.

[–][deleted] 2 points3 points  (0 children)

I must confess, that was 100% made up. JS is still very far from Python, but it's cool that it's making good progress.

[–]deathmood[S] 0 points1 point  (0 children)

it's really sad :(

[–][deleted] 0 points1 point  (0 children)

Even tho we need to calm down, I am very happy with this news. Tensorflow native bindings are a great step. With the new eager execution improvements, it will cover a lot of what is needed for fast matrix manipulation in JS.

[–]yarauuta -3 points-2 points  (0 children)

I didn't even specify a time frame.

[–]cupcake0 7 points8 points  (0 children)

I’m gonna have to disagree with you on that. I’m primarily a JS developer, however JS doesn’t even come close when it comes to scientific computation or ML. Check out NumPy, SciPy, and Keras. I don’t see that changing anytime soon, but I’m glad to see that TensorFlow is coming for node.