5 ms·
As an aside: The ML-ML/MachineLearning and JS-JavaScript/Jane Street interpretations makes comments on anything even tangentially related harder to parse. Reaso
by superlopuh 8y ago
As an aside: The ML-ML/MachineLearning and JS-JavaScript/Jane Street interpretations makes comments on anything even tangentially related harder to parse. Reason coming in and closing the loop has not made this easier. I wonder whether this affects anyone else.
- mhd 8y agoI'm affected by the "ML" switcheroo, but Jane Street isn't big enough on my monitor to cause confusion. And thankfully there's little cause for "NLP" ambiguity these days.
- pure-awesome 8y ago> And thankfully there's little cause for "NLP" ambiguity these days. Is there not? When I Google "NLP" the first results are for "Neuro-Linguistic Programming", which I assume is NOT the definition you'd consider the important one. The fact that it also has "programming" in the name and has to do with "linguistics" does not make things easier.
- mhd 8y agoTrue, but its popularity seems to have decreased enough that I don't get that many quackery-NLP news in my personal bubble / here. So when NLP does turn up, it usually means the right thing. That people now use "ML" when it's just a simple matter of NLP is another matter…
- erk__ 8y agoA good example of this is ML Kit from google [0] vs MLKit a ML compiler [1] [0]: https://developers.google.com/ml-kit/ https://developers.google.com/ml-kit/ [1]: http://www.elsman.com/mlkit/ http://www.elsman.com/mlkit/
- cannam 8y agoDoubly confusing as people associate "Kit" names with Apple a lot of the time - a company and platform that has nothing to do with either project.