4 ms·
The move to Github is interesting. I'm wondering if this is harbinger of Codeplex's doom very soon.
by untog 12y ago
The move to Github is interesting. I'm wondering if this is harbinger of Codeplex's doom very soon.
- lbotos 12y agoThe flip-side to that could be trying to bring the food to the fish so to speak. Github users are in their (perceived) target market.
- kyriakos 12y agoThis is part of the new face of Microsoft. They realised that they are losing their followers in the developer community by sticking to their old ways. They've been 'listening' to the public opinion a lot lately.
- BigChiefSmokem 12y agoI just got off the phone with a recruiter who offered me a chance at a Ruby job based on my ASP.NET experience because, quote "they have a lot of old C# guys there and they're willing to train anyone willing to cross over". This means I can make a lateral (stack) move without having to revert back to "junior" status. Hey, I love me some C# and .NET but the offers from the open-source community are just too tempting. I booked an interview.
- cobalt 12y agowhy not get them to move to asp.net maybe or at least something more like it
- untog 12y agoWhy not turn up at a Ruby shop and try to get them to convert to ASP.NET? As a former .NET dev... why would you even want to do that?
- _random_ 12y agoIsn't Ruby considered a passing technology nowadays?
- chc 12y agoIsn't just about everything? Hypothesis: For any language X, there exist articles claiming either "X is too immature for real-world use" or "X is no longer a good choice for new development".
- julien_c 12y agoNot an exclusive OR though :)
- Pacabel 12y agoRuby on Rails is somewhat of a special case, though. Early web technologies like CGI, PHP, JSP, ColdFusion, ASP and ASP.NET arose due to real-world needs. Ruby on Rails, on the other hand, arose mainly due to hype. From a technological perspective, there really wasn't anything special about Ruby on Rails. Many of us who had been doing web development for some time had already built or used proprietary/in-house frameworks that offered the same functionality, but were written in Perl, Python or Tcl instead. If it weren't for strong and very loud personalities within the Ruby on Rails community, combined with some very lucky timing with respect to the rise of the so-called "Web 2.0", it likely wouldn't have been seen as "special", and wouldn't have garnered the hype that it did. Technologies that come out of an environment of hype, rather than solving real problems, tend not to stick around as long. Systems built using technologies that solve real problems continue to be used and maintained. Systems built using technology chosen purely because some manager or executive saw a webcast full of nice-sounding buzzwords tend not to survive very long.
- chc 12y agoThe idea that Rails' popularity came from managers hearing buzzwords doesn't match my recollection of history. Rails' early support came from backend web developers who hated working in enterprise Java frameworks. Ruby on Rails offered them a pleasant and easy-to-jump-into alternative to that environment. I remember Pythonistas at the time raised similar complaints about how Python already had all this stuff — but the thing is, Rails did a nice job of packaging it up in a way that was easy for disaffected Java jockeys to get into and start having fun, while the Python approach at the time was more along the lines of "take this thing and that thing — or maybe one of these five other things, we can't decide — then make this other piece yourself and stick them together with chewing gum." Rails did come to prominence largely through social channels rather than technical superiority, but it wasn't a marketing-driven hype train targeted at nontechnical managers — it appealed to hackers who wanted to have fun but did not already have a homebrew Perl stack at the ready. That's how I remember it, anyway.
- MichaelGG 12y agoShouldn't this be expected? Hire people based on intelligence and capability, not necessarily for knowing a particular language or APIs.
- UK-AL 12y ago"This means I can make a lateral (stack) move without having to revert back to "junior" status. " - Good. Because developers would reset or be unemployed every 5 years otherwise. I've made several stack switches without issue. Usually it involves switching languages at your current company, then using your current salary as leverage to get the next. The main barrier is HR, which you can get around using this method.
- shurcooL 12y agoYeah, this is awesome and it's making me jealous. I'm still dreaming of a world where one day Google will announce that golang source code is moving to git and GitHub.
- felixrieseberg 12y agoTruth be told, CodePlex is fairly popular in the .NET world. TypeScript simply is a JavaScript project, plays well with Node, NPM and Jake - I think it makes sense for it to be on GitHub. It's not the first MSFT source base hosted on GitHub, probably won't be the last. Heck, I work at MSFT and keep all my open source code on GitHub. I wouldn't read too much into that though - huge company, a bunch of projects and different audiences. CodePlex has an audience - there's a bunch of cool projects on there, too.
- yellowapple 12y ago> It's not the first MSFT source base hosted on GitHub It is, however, the only repo under the "Microsoft" GitHub user AFAICT (https://github.com/Microsoft https://github.com/Microsoft).
- felixrieseberg 12y agoTrue - but remember, there's a bunch of teams building stuff. Most of Open Tech's and Azure's open code bases are on GitHub. TypeScript isn't the biggest MS project on GitHub and I just want to make sure that nobody is using this as a "CodePlex is dead!" data point. https://github.com/MSOpenTech https://github.com/MSOpenTech https://github.com/Azure/ https://github.com/Azure/
- rl3 12y agoNot to mention ASP.NET vNext and related projects: https://github.com/aspnet/ https://github.com/aspnet/
- spankyj 12y agoAnd WinJS https://github.com/winjs/winjs https://github.com/winjs/winjs
- mattpodwysocki 12y agoAnd the Reactive Extensions for all languages: https://github.com/Reactive-Extensions/ https://github.com/Reactive-Extensions/