mousetraps

Okay fair enough, maybe we’re just talking past each other :).

Why so black and white? There are many incentives at play, and many ways to contribute to solving real world problems.

I’ve spent time in both academic research and industry.

Research is not supposed to be immediately applicable. The goal is to produce new knowledge - more importantly shared knowledge. Publishing is not a bad measure of that. Additionally, ability to secure grants provides incentive to focus on problems others want solved.

No incentive system is perfect, but I don’t really see how this is any different from any organization. And I don’t think it’s fair to judge an entire discipline by the negative examples.

> stigma coming from the academic side that dataset collection is a low-level problem not worthy of serious algorithmic investment

Agreed it needs more attention, but - for academia - I think it's more of an incentive issue than a stigma issue. E.g. harder to benchmark the performance of two algorithms if they don't operate on the same dataset. Also to be fair, research into things like synthetic data mitigates the problem, just in a different way.

The paper you cited is interesting. Thanks for sharing. Hopefully that spawns more focus into understanding the subtleties of each dataset. IIRC Kaggle also had issues around generalizability, but for different reasons.

Anyways it's still early on... but we're currently building tools to help solve this problem. In particular simplifying the data collection / labeling process for vision systems. Would love to chat further w/ anyone interested in providing feedback. Email is [email protected]

Good question. From an engineering perspective, the codebases are different, so (with the exception of some components like JS/TS language service) the two will continue to evolve separately until we invest further in consolidating engineering efforts. From a product perspective, VS and VSCode appeal to different communities, and we need to be cognizant of that whenever we consider lighting up new functionality. Is there a specific feature or improvement you're especially excited about?

Node.js Tools dev here - excited to see this on HN! Happy to answer any Qs

I believe ams6110 meant that there is no need for Mozilla to build their own search engine from the ground up when they could simply partner with DuckDuckGo.