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

The Node Tools extension is meant for developing apps built on Node, but VS has always had top notch support for C++ so there should be no reason why you can't use them together.

Check out this tutorial for developing a node addon in VS, and let me know if you have any ideas on how to improve the experience.

http://computer-vision-talks.com/articles/how-to-debug-nodej...

This is in Visual Studio (works in the free community edition), and we have some azure VM images ready for you to spin up if you want to give it a try without installing windows http://blogs.msdn.com/b/visualstudio/archive/2015/04/24/node...

Code and VS are different products, codebases, Etc. But if you see a specific feature you'd love to have in code or v.v., let us know, as we're always considering ways to collaborate wherever it makes sense.

Whoa totally did not expect to see this hit HN!

dev/person-in-video here, happy to answer any questions we couldn't get to in the video :)

GitHub repo for those interested in playing around with the code. https://github.com/Microsoft/nodejstools

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.

:-)

Let us know if you run into any issues!

Yep. That's definitely high priority. First we'll fix the squiggles in the editor and then we'll add intellisense...

Please comment so we can better prioritize the es6 feature work.

Dev here, happy to answer any questions.

GitHub link: https://github.com/Microsoft/nodejstools

Hi bgarbiak,

You can use the "From Existing Node.js Code" project template to create a project from a folder, but the project file itself is a requirement for visual studio and also allows us to include helpful metadata (whether or not to analyze a directory, etc - most IDEs/text editors include a project file for this very purpose - they just hide it a little better). That said, at some point we'd like to change things up so that the project does feel more similar to the folder/file experience you might expect.

This is to change the project file to be more "transparent". https://nodejstools.codeplex.com/workitem/1855

There's also another issue to directly open a folder without requiring the user to take steps to create the solution/project. https://nodejstools.codeplex.com/workitem/209

Additionally, like rlp mentioned - make sure that "show all files" is turned on so that you can see everything in the folder, not just files you've defined as being a part of your project.

Hope that helps - let me know if you have any other questions.

I posted this in the comments in the blog as well:

With regards to the technicalities of max_path itself... the issue is with the .NET file I/O API, which doesn't allow you to use \\?\ paths to work around it, and is too big for our team in particular to do much about. Here's a good article that might provide a little more context (it's a little old, and these "plans" they speak of never actually materialized.)

http://blogs.msdn.com/b/bclteam/archive/2007/02/13/long-path...

That said... we don't like it either, and we are still thinking about what we can do.

I can't speak for other teams, but re: NTVS... we definitely dont want to force abstractions upon you. For instance, with the npm integration, we provide UI where it makes sense (exploring/managing your packages, searching for packages), but you can drop into the cmd line or .npm command in the interactive window anytime you please. Think of it as semantic zoom - allowing you the flexibility to traverse the levels of abstraction when it makes sense. Are we 100% there yet? No. But I consider that to be the ideal experience, and we're definitely trending closer to that vision.

Thoughts? I'm especially curious to hear how you think we can improve the existing experience so that it caters better to your workflow. What are some of the abstractions that get in your way?

Fwiw we have remote debugging to any OS, so you can remote debug your app regardless of whether or not it's running on azure. We are striving to streamline this experience as much as possible, so any feedback or ideas you have on how to mitigate some of windows issues you've run into would be super helpful. :-)

Haha, fair enough. Then I suggest you follow @NT4VS on Twitter. We'll let you know when it happens. :-)

Also re: io.js + Azure websites - looks like someone wrote a script to make it easier!

http://azure.microsoft.com/en-us/documentation/articles/web-...

Technically...

- connect is for filing bugs

- uservoice is for "ideas and suggestions"

How people use it, of course, is a completely different story...

And then some teams (like us) have public issue trackers, which are the best approach if available because everything goes directly to the team: https://nodejstools.codeplex.com/workitem/list/basic

Awesome! Please, please, please let us know if you have any feedback!

See comments on this thread re: max_path problems, workarounds, and how we help mitigate it in NTVS: https://news.ycombinator.com/item?id=9265694

Otherwise, yeah - we don't like it either... here's the not-closed uservoice request ;-) https://windows.uservoice.com/forums/265757-windows-feature-...

EDIT: Re: fish: Indeed - we have some big fish to fry, but luckily msft is a big company that can fry multiple fish at a time. Personally, I'm excited to help improve the Node tooling story by frying this fish, and passing our learnings and feedback onto the the other teams @ msft so that they can improve their recipes. Ultimately, we strive to have a complementary set of fried fish. And maybe some vegetables too... :)

Break on exception? Done! http://nodejstools.codeplex.com/wikipage?title=Debugging#bre...

We have SO MANY PLANS, so please upvote or request the ones you think are important :) https://nodejstools.codeplex.com/workitem/list/basic

Let us know if you have any questions! There's some _really cool_ stuff going on there, but it can be tough to wade through depending on your experience.