JavaScript for Data Science • Hacker News Board

Re: JavaScript for Data Science

#81

Post by genrez » Mon, Apr 26, 2021, 3:12 PM UTC

pwdisswordfish0 wrote: post #75

ctidd wrote: post #73

Earlier quoted context omitted.

I want to respond to this constructively, because you highlighted a useful interface I'd never taken note of previously; maybe we can focus this discussion on a technical level. Meanwhile, if you haven't had a positive response to technical feedback directed to JS engineers about this, I would encourage rereading the comment you wrote. I genuinely hope this is useful feedback, as I very much value insight from other…

> if you haven't had a positive response to technical feedback directed to JS engineers about this, I would encourage rereading the comment you wrote You're mixing up cause and effect; there's a reason why the perspective laid out in that comment has come to carry the amount of derision evident in its tone. It's wrong to assume things started out like this (and it's wrong to assume that a different tone will achieve…

Just FYI, the standardjs link doesn't seem to support your point here. It seems like standardjs is mostly about forbidding confusing syntax and obsolete APIs. (like .__iterator__, which appears to be replaced by Symbol.iterator, or .__proto__ which is replaced by .getPrototypeOf())

The only item which standardjs forbids that I could identify as possibly producing a decent performance improvement if used is the "with" statement. They also forbid wrapping non-objects in objects, which I guess could provide extra-expressiveness, but seems like it would usually just be a performance penalty.

I have seen people recommending obviously inefficient things like including large third-party libraries just to look up an element by class name, but standardjs looks like it is just a set of linting rules. I don't agree with all of them but I don't think there is a set of rules everyone would agree to.

Re: JavaScript for Data Science

#82

Post by jwilber » Mon, Apr 26, 2021, 6:05 PM UTC

javierluraschi wrote: post #65

jwilber wrote: post #63

Earlier quoted context omitted.

js does have a glm library.

Which one are you using?

I’m not using one - as said, the project required I implement the model/all requisite math from scratch.

Re: JavaScript for Data Science

#83

Post by bluishgreen » Tue, Apr 27, 2021, 12:59 AM UTC

beforeolives wrote: post #2

I know that data science is a broad and somewhat vague term but this - We will cover: Core features of modern JavaScript Programming with callbacks and promises Creating objects and classes Writing HTML and CSS Creating interactive pages with React Building data services Testing Data visualization Combining everything to create a three-tier web application - this isn't data science.

"JavaScript relies heavily on callback functions: Instead of a function giving us a result immediately, we give it another function that tells it what to do next. Many other languages use them as well, but JavaScript is often the first place that programmers with data science backgrounds encounter them."

That sentence from the book clarifies a lot for me. It is Javascript for Data Science People. Taken in that context this is an excellent book written with empathy for the Data Science user who is usually making uneasy excursions which they hope and pray is only temporary into Javascript and running back to Python the first time they encounter a Promise or a Callback.