There is a good opportunity there for microsoft to contribute NTFS source to the linux kernel, i doubt they'll do it, i personally want to see NTFS replaced, but for legacy concerns, i think they should go ahead
'Because it's a very practical issue that can't be magicked away into the cloud.'
Maybe I'm not focusing on the 'into the cloud' part enough but is the first part of that statement true? Filesystems seem like a very practical issue: writing 1s and 0s in a (sometimes not even sequential) stream to a block device...my first glance at the issue it doesn't seem nearly a daunting challenge as CPU interoperability (multiple vendors, multiple instruction sets, somewhat overlapping, somewhat not) or networking, etc
Practically it's so easy to just put everything in git/SMB when you transition to Linux NTFS hardly matters anymore. It would make interoperating with running Windows systems slightly easier but if Microsoft wants to cut their legs off it's their issue.
Can you elaborate on the git/smb process a little more? I've been using ubuntu exclusively for a number of years but haven't worked git into my workflow as much as I'd like.
For git just set the origin to ssh somewhere one of your other computers (preferably one that's always on and has a public IP) and keep your stuff in it.
6 comments
[ 4.0 ms ] story [ 20.0 ms ] threadMaybe I'm not focusing on the 'into the cloud' part enough but is the first part of that statement true? Filesystems seem like a very practical issue: writing 1s and 0s in a (sometimes not even sequential) stream to a block device...my first glance at the issue it doesn't seem nearly a daunting challenge as CPU interoperability (multiple vendors, multiple instruction sets, somewhat overlapping, somewhat not) or networking, etc
For git just set the origin to ssh somewhere one of your other computers (preferably one that's always on and has a public IP) and keep your stuff in it.