HN2new | past | comments | ask | show | jobs | submitlogin

>Why not let things play out a little before predicting chaos?

History.



GP gave you a very good reason why this is different than historical Microsoft EEE[0]:

> Github doesn't have the vendor lock-in that other companies have

There's not much about Github that can't be easily replaced; it uses git at its core. Comments, issues, and wikis are convenient, but relatively simple to implement.

The main value in Github is the de facto community status it has, which it earned by being an open community and good steward of open source projects. The worst MS could do here is shoot themselves in the foot and ruin that value (which they just purchased for 7.5B) by driving developers to other platforms (who will make it all too easy to switch).

I think the M&A teams at MS must have seen this possiblity and have a different plan in mind for Github. Think dead simple (one-click) Azure deployments and integrations. And if you want (or need) that functionality for a different cloud provider, you'll just have to build it yourself on a different site.

[0] https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...


> There's not much about Github that can't be easily replaced.

Integration and workflow. Thanks to the various gubbins available in the marketplace[0], CI/CD goodies, hooks into communication and project management tools and so on, for a lot of people migrating away from Github would mean losing access to enough little convenience things that actually it's not feasible for a large organisation with not great process change management techniques.

https://github.com/marketplace


It's not like anything about github is open source. Maybe that will change.


well, there was the atom editor. which now i fully expect msft to kill in favor of vs code. damn it.


VsCode is open source too: https://github.com/Microsoft/vscode


i vastly prefer atom - open source or not.


How would they kill it? It's open source.


They can't really "kill" it as in destroy it, but the biggest contributors to that project were all GitHub staff. MS will most definitely redirect any staff efforts to VSCode instead.


Yea, but if you maintain that mentality, that affects your thoughts, affects behavior, affects 'crowd' behavior generally (all those agree), is perceived as such from those you predict about, get it? Affects all those who disagree too.

2 sides, same coin. You assume chaos, they see you assume that. They shape their narrative to fit their perspective with this data in mind. That rationalizes the behavioral pattern from their end, which continues the cycle.

Not saying I know any better solution, just that it's annoying as fuck to actually change when everyone keeps assuming you won't, and treats you as such. Chaos is probably going to happen even if there's a general mutual trust that springs forth. Can't control chaos.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: