4 ms·
No rub. The code is there, legally usable, and demonstrates useful examples.
by jabits 11y ago
No rub. The code is there, legally usable, and demonstrates useful examples.
- simoncion 11y agoMSFT is currently engaged in a PR war. This offering is significantly less substantial than it would appear at first glance... the sort of first and only glance a harried tech reporter would make.
- taspeotis 11y ago> This offering is significantly less substantial than it would appear at first glance https://blogs.msdn.microsoft.com/visualstudio/2016/03/17/open-sourcing-the-visual-studio-productivity-power-tools/ https://blogs.msdn.microsoft.com/visualstudio/2016/03/17/ope... > The repository currently contains a subset of all extensions in Productivity Power Tools for Visual Studio 2015. Some extensions are not yet ready to be open-sourced, but we’re working on making all of them available over time.
- ChristianGeek 11y agoAre you guys serious? While you all are bitching about the fact that less than half the extensions are currently missing, the rest of us are going to enjoy playing with and learning from the ones that are there.
- taspeotis 11y ago> Are you guys serious? While you all are bitching... Uh, there's only one user bitching. Everybody else seems fine with it.
- simoncion 11y ago> Uh, there's only one user bitching. I'm not bitching about anything. I'm providing a contrary view to the effusive and largely uncritical praise that much of the tech press spews whenever MSFT announces that they've open sourced this tiny thing, or ported a part of that thing to a non-Windows OS. If you read my other comments elsewhere on this page, it becomes clear that I very much want for MSFT to have stopped bullying, subverting (and impeding the function of) standards bodies, engaging in anticompetitive lock-out, and other such shady backroom dealings. MSFT is a big company that hires rather smart people. They could use their money and collective brainpower to do really great things for the computing community. Thing is, those of us who've been around for at least the past twenty years have seen the "Good Microsoft" act, and we remember how that act was rather short-lived. If MSFT were to do something substantially significant (such as joining the OIN [0], making a public promise to remain a member and substantially participate in its proceedings for the next twenty years, as well as a public promise to never tamper with it or its proceedings [1]) before many of us old hands start thinking that this is an actual change in corporate direction. [0] http://www.openinventionnetwork.com/ http://www.openinventionnetwork.com/ [1] That is, to never, ever do anything even remotely like the shit they did at ISO.
- simoncion 11y agoHaven't you seen ATT use the "ATT owned gigabit fiber service is coming soon, we're rolling it out real soon now!" feint in regions where Google Fiber is actively rolling in enough times to recognize just how cheap promises are and how insignificant the cost of breaking those promises is? :) I genuinely hope that the corporate overlords within MSFT are very serious about becoming a good actor in the computing community. MSFT is a big company, and they could do a lot of good for both the software and hardware sides of the community. However, this is far from my first rodeo, and this isn't the first time we've seen MSFT play the good guy. If they stick to form, the community that they fostered will be forcibly forgotten and left to wither in the sun in a -comparative- blink of an eye. Just ask the Samba guys about those Plugfests they used to attend. :)
- deleted 11y ago[deleted]
- amadeusw 11y agoI don't smell any PR war here. This release is important because it publicizes code that is very valuable to tool developers. Before this release you had two ways to learn practical aspects of Visual Studio extensibility: 1. Use samples that each explore an isolated feature. Available on github [0] or for a few years back on MS website. 2. Decompile VS to see what's happening behind the scenes. While .NET Reflector does very fine job, the code was convoluted to begin with and it was nearly impossible to find relevant bits. I imagine engineers at MS are cleaning up the code of all power tools so that it's clear and easier to follow. For example we have "Go to definition" right here [1] and I remember long evenings unsuccessfully looking for this functionality in the decompiled code. [0] https://github.com/Microsoft/VSSDK-Extensibility-Samples https://github.com/Microsoft/VSSDK-Extensibility-Samples [1] https://github.com/Microsoft/VS-PPT/tree/master/src/GoToDef https://github.com/Microsoft/VS-PPT/tree/master/src/GoToDef
- simoncion 11y ago> I don't smell any PR war here. sigh All significant wars are much larger than the individual actions in them. :) Read my other comments attached to this HN submission to get some insight into my opinion of MSFT and its actions. It's probably a little more nuanced than you'd expect.