Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Propel – Machine learning for Javascript

propelml.org

Post reply on HN
Print view View original

11–20 of 64 posts

Re: Propel – Machine learning for Javascript

#11

Post by kevincennis »

irrational wrote: post #10
tekkk wrote: post #9

This could a fun way to learn ML using just your browser. I'm still skeptic about the performance but for prototyping it could be viable. One thing bothering me about reading the API is the inconsistent way of adding semicolons. Not an important thing I'm sure and as my personal opinion I'd much rather have the examples without them. To me they are just waste of time. Also it makes the code look more like Python. Any…

You will hate to hear that there is a serious proposal to make semicolons mandatory in the next version of ECMAScript.

Can you provide a source for that?

Closest thing I could find was this, which simply adds an ASI hazard clause: https://github.com/tc39/ecma262/pull/1062

Re: Propel – Machine learning for Javascript

#12

Post by seniorsassycat »

irrational wrote: post #10
tekkk wrote: post #9

This could a fun way to learn ML using just your browser. I'm still skeptic about the performance but for prototyping it could be viable. One thing bothering me about reading the API is the inconsistent way of adding semicolons. Not an important thing I'm sure and as my personal opinion I'd much rather have the examples without them. To me they are just waste of time. Also it makes the code look more like Python. Any…

You will hate to hear that there is a serious proposal to make semicolons mandatory in the next version of ECMAScript.

I found [this pull request] that adds language recommending the use of semicolons, but no proposals to require semicolons or to remove Automatic Semicolon Insertion.

Removing ASI from ECMAScript would break backwards compatibility - modern JS engines couldn't run scripts that use ASI which would break a lot of websites that are alread deployed. ECMA will add features that won't run in old engines (older V8 can't parse arrow functions) but they won't add/remove/change features that break existing behavior.

Today there are code patterns where ASI is ambiguous, or at-least hard for a developer to grok. TC39 is warning developers that new language features will not be designed for ASI and might have confusing behavior if those new features are used without semicolons.

[this pull request]: https://github.com/tc39/ecma262/pull/1062/files

Re: Propel – Machine learning for Javascript

#16

Post by Phrodo_00 »

dustinmoorenet wrote: post #6

It binds directly to the TensorFlow C API, if you run it in NodeJS, which is awesome. I get tired of having to setup a python env anytime I want to play around with ML.

So now you'll have to setup a nodeJS env? I don't really see the difference.

Re: Propel – Machine learning for Javascript

#17

Post by sgslo »

Phrodo_00 wrote: post #16
dustinmoorenet wrote: post #6

It binds directly to the TensorFlow C API, if you run it in NodeJS, which is awesome. I get tired of having to setup a python env anytime I want to play around with ML.

So now you'll have to setup a nodeJS env? I don't really see the difference.

Setting up a node env is arguably easier. An installer from the NodeJS downloads page includes both the Node runtime and NPM. One executable to get started.

Python, on the other hand, requires a python installer, then a pip or conda installation script. Not to mention python vs python3 decisions.

Re: Propel – Machine learning for Javascript

#18

Post by crandycodes »

Phrodo_00 wrote: post #16
dustinmoorenet wrote: post #6

It binds directly to the TensorFlow C API, if you run it in NodeJS, which is awesome. I get tired of having to setup a python env anytime I want to play around with ML.

So now you'll have to setup a nodeJS env? I don't really see the difference.

Maybe they already have a Node environment set up and appreciate not having to context switch?

Re: Propel – Machine learning for Javascript

#19

Post by Phrodo_00 »

sgslo wrote: post #17
Phrodo_00 wrote: post #16

Earlier quoted context omitted.

So now you'll have to setup a nodeJS env? I don't really see the difference.

Setting up a node env is arguably easier. An installer from the NodeJS downloads page includes both the Node runtime and NPM. One executable to get started. Python, on the other hand, requires a python installer, then a pip or conda installation script. Not to mention python vs python3 decisions.

But some version python comes pretty much with every system, then you only need to install tensorflow with pip.

Re: Propel – Machine learning for Javascript

#20

Post by akatechis »

Phrodo_00 wrote: post #16
dustinmoorenet wrote: post #6

It binds directly to the TensorFlow C API, if you run it in NodeJS, which is awesome. I get tired of having to setup a python env anytime I want to play around with ML.

So now you'll have to setup a nodeJS env? I don't really see the difference.

Not sure what there is to set up for a new python project, but on Node, all you have to do is `npm init` and then `npm install propel` to get started.
Post reply on HN