5 ms·

Interestingly enough, that feature already exists and is being removed from Windows. From the transactional NTFS Wikipedia page[0]: > Microsoft has deprecated

by jfim 6y ago

Interestingly enough, that feature already exists and is being removed from Windows. From the transactional NTFS Wikipedia page[0]: > Microsoft has deprecated TxF and stated that it may be removed in a future version of Windows [0] https://en.wikipedia.org/wiki/Transactional_NTFS https://en.wikipedia.org/wiki/Transactional_NTFS

josephg 6y ago
Cool! Does anyone know why its being removed? The article says it supports atomic operations spanning multiple computers. Thats pretty tricky to implement correctly. My guess would be that its being removed because the feature is overbaked and it impacts too many parts of windows. But I'd love to know for sure if anyone has insider knowledge into the feature.
- jdjtktktmf 6y ago
  Basically nobody is using it: > While TxF is a powerful set of APIs, there has been extremely limited developer interest in this API platform since Windows Vista primarily due to its complexity and various nuances which developers need to consider as part of application development. > As a result, Microsoft is considering deprecating TxF APIs in a future version of Windows to focus development and maintenance efforts on other features and APIs which have more value to a larger majority of customers.
  - adontz 6y ago
    Actually, it is hard to remove it, since Windows Update is dependent on it. "TxF is presently deprecated, but the functionality is still available. We don't recommend disabling this feature on the C: volume." Microsoft supports APIs which were declared deprecated for decades. However, I totally agree in "Basically nobody is using it" part. It's because it was not properly implemented in .Net Framework. And now, when .Net Core is multiplatform, i.e. worst of all worlds, chances it will be implemented are very close to zero. ReFS does not support TxF. Windows has a lot of awesome APIs which are accessible only to C/C++ and are not advertised well.

by jfim 6y ago

josephg 6y ago

Cool! Does anyone know why its being removed? The article says it supports atomic operations spanning multiple computers. Thats pretty tricky to implement correctly. My guess would be that its being removed because the feature is overbaked and it impacts too many parts of windows. But I'd love to know for sure if anyone has insider knowledge into the feature.

jdjtktktmf 6y ago
Basically nobody is using it: > While TxF is a powerful set of APIs, there has been extremely limited developer interest in this API platform since Windows Vista primarily due to its complexity and various nuances which developers need to consider as part of application development. > As a result, Microsoft is considering deprecating TxF APIs in a future version of Windows to focus development and maintenance efforts on other features and APIs which have more value to a larger majority of customers.
- adontz 6y ago
  Actually, it is hard to remove it, since Windows Update is dependent on it. "TxF is presently deprecated, but the functionality is still available. We don't recommend disabling this feature on the C: volume." Microsoft supports APIs which were declared deprecated for decades. However, I totally agree in "Basically nobody is using it" part. It's because it was not properly implemented in .Net Framework. And now, when .Net Core is multiplatform, i.e. worst of all worlds, chances it will be implemented are very close to zero. ReFS does not support TxF. Windows has a lot of awesome APIs which are accessible only to C/C++ and are not advertised well.