One of my pet ideas is a new programmer's editor that uses proportionally as much compute resources as Emacs did in the late-80s. An amount of computing that would show up as a major line item on your department's timesharing bill.<p>1000 cores costs around $50/hr, so if it boosted my productivity measurably it'd be worth it. Searching all public github code for strings matching around my cursor seems like the sort of thing these 1000 cores should be doing.
the linked page is an old version. New version:
<a href="https://visualstudiogallery.msdn.microsoft.com/a1166718-a2d9-4a48-a5fd-504ff4ad1b65" rel="nofollow">https://visualstudiogallery.msdn.microsoft.com/a1166718-a2d9...</a>
This seems like a really cool idea, but I'm not sure how useful it'd end up being. I also wasn't able to get it to actually work with anything other than the demo question they provided
I installed the plugin, restarted VS, but nothing happens when I type:<p>/// convert string to byte array<p>and press tab afterwards.<p>Am I missing anything?<p>Edit: actually something does happen... it inserts a tab, just like any VS installation would do.<p>Edit 2: from browsing through the comments it seems like it might be a ReSharper conflict. They said they would update it though, but in 8~9 months nothing has changed apparently.
I always thought that people should have more built-in search power when they code. It's funny that Microsoft is taking the lead over Google on this, though I guess Google doesn't have their own IDE.<p>Soon, modular projects will just consist of searching and plugging in components...
I installed on VS2013 Ultimate wo/Resharper and here is how it worked for me.<p>The '///' then tab does nothing but when I start typing in the IDE however it kicks in with a much better Intellisense
complete with the Bing snippets like depicted on the VS Gallery. So perhaps they limited the slash+tab sequence?
Why aren't we using git like hashes for compilers? Take referentially transparent parts of code, blob together and make a hash of the AST in a canonical form and a hash of the assembly, source, transforms used, and benchmark stats. The compiler would run continiously searching for new solutions.
Unfortunately I don't write much C# (took a few courses that heavily used it) so it's going to be hard for me to really get an idea of what this feels like to have access to all the time (i.e. know if it's really useful). I'd really love to see what it feels like with a scripting language like Python or Javascript
I fear for the future of working with copy/paste programmers, but then my fears are probably unfounded because after all, this uses the Bing search engine. Searching for "///how to sort an array" will most likely just give me the top ten tourist hotels in Paraguay instead.