Those are all projects under Microsoft’s rule. Name some OSS where Microsoft is a good citizen. The GVFS issue is a clear example of ol’ Microsoft behavior. I am not convinced MS will not push GVFS down peoples throats via github and there by embrace, extend, and extinguish Git.
Microsoft Engineers spent time with GitHub Engineers to build the Git Virtual File System, because Microsoft needed to use GIT as a version control for really large repositories like that of Windows which is about 300GB.
Standard GIT was unusable for such sizes.
Changes made during this development have been gradually added to standard GIT over time. gvfs.io
1) GVFS has been Gnome Virtual File System for a really long time, and this poses a naming conflict. Microsoft's response is pretty much PR nonsense and they ignore this issue.
2) Microsoft finds Git's rule about backwards compatibility troublesome. If they can, they will violate this rule and break Git repositories when they feel like.
3) GVFS is pretty much Windows-only.
4) GVFS is Microsoft's thing, not a git community thing. They have shown no interesting in working together to create a solution everybody feels happy with. It's GVFS or GTFO.
Node.JS and OCI are projects where MS seems to be behaving nicely. And unless your project is very large, I'm not sure how GVFS is even a concern for you.
It might concern me when GitHub is going to require Microsoft's version of Git, which isn't fully compatible with the standard Git.
GitHub already announced that they are going to adopt Microsoft's Git Virtual File System. This feels a lot like the Embrace and Extend.
What "Microsoft's version of Git" are you referring to here? It can't be GVFS, because that's a virtual file system driver that's separate from the git protocol and repository.
Those are all projects under Microsoft’s rule. Name some OSS where Microsoft is a good citizen. The GVFS issue is a clear example of ol’ Microsoft behavior. I am not convinced MS will not push GVFS down peoples throats via github and there by embrace, extend, and extinguish Git.
How is GVFS a bad thing?
Microsoft Engineers spent time with GitHub Engineers to build the Git Virtual File System, because Microsoft needed to use GIT as a version control for really large repositories like that of Windows which is about 300GB.
Standard GIT was unusable for such sizes.
Changes made during this development have been gradually added to standard GIT over time. gvfs.io
Because
1) GVFS has been Gnome Virtual File System for a really long time, and this poses a naming conflict. Microsoft's response is pretty much PR nonsense and they ignore this issue.
2) Microsoft finds Git's rule about backwards compatibility troublesome. If they can, they will violate this rule and break Git repositories when they feel like.
3) GVFS is pretty much Windows-only.
4) GVFS is Microsoft's thing, not a git community thing. They have shown no interesting in working together to create a solution everybody feels happy with. It's GVFS or GTFO.
Edit: it looks like MS starting to address #1
GVFS for Mac < blogs.msdn.microsoft.com/devops/20... > ... interesting!
Anyone use GVFS for Windows 10? Smooth sailing, or rough around the edges?
Node.JS and OCI are projects where MS seems to be behaving nicely. And unless your project is very large, I'm not sure how GVFS is even a concern for you.
It might concern me when GitHub is going to require Microsoft's version of Git, which isn't fully compatible with the standard Git.
GitHub already announced that they are going to adopt Microsoft's Git Virtual File System. This feels a lot like the Embrace and Extend.
What "Microsoft's version of Git" are you referring to here? It can't be GVFS, because that's a virtual file system driver that's separate from the git protocol and repository.
This one: github.com/Microsoft/git
The recommended install when you are going to install GVFS, also the only one which Microsoft tests with GVFS.