0x1d7

4 ms·

61.
by 0x1d7 4mo ago
What does this have to do with the article you're responding to which is about OneDrive for Business? More HN comments, less reddit comments, please.
62.
by 0x1d7 4mo ago
Odfb has always had a SharePoint backend. Used to be called MySites and carried no relation to the consumer product you’re confusing it with.
63.
by 0x1d7 4mo ago
> What does Windows offer these devs that is missing in Linux? A stable ABI. Then there are the specifics to the apps you're mentioning (i.e., decent color calibration support, memory management, display drivers). We saw what happen
64.
by 0x1d7 4mo ago
This is correct. The flexibility of the file system filter model does have a performance penalty and you will see that across file systems. This is why 'DevDrive' exists for ReFS, to reduce that penalty (though ReFS comes with it&
65.
by 0x1d7 4mo ago
NT does not have a fork-alike API. The NT internal APIs are all known.
66.
by 0x1d7 4mo ago
It's the file system filters that are an issue on Windows. It trades performance for extensibility. NTFS itself is a fast file system.
67.
by 0x1d7 4mo ago
IME edu operates much differently than [US] corporations which use a 3 - 5 year deprecation schedule. Edu is more 'run it until it doesn't'.
68.
by 0x1d7 4mo ago
Yes, but the Executive has a hard dependence on Win32 for service control.
69.
by 0x1d7 4mo ago
The NT kernel does not understand fork(). You can-sorta-fake-it, which is what WSL1 did. There's no equivalent to fork() in any version of Windows. From your link: > As an example, the Linux fork() syscall has no direct equivalent c
70.
by 0x1d7 4mo ago
POSIX was implemented as a subsystem. And it was never _fully_ implemented, as my post said. The NT kernel doesn't support certain POSIX semantics (fork).
71.
by 0x1d7 4mo ago
The NT kernel could never implement full POSIX semantics. It would have to be another UN*X clone to do so. And that would suck.
72.
by 0x1d7 4mo ago
NT shipped with USC-2 as UTF-8 (and -16) did not yet exist. USC-2 naturally translated to UTF-16, hence the choice. NT/Win32 is also designed for fixed-with code units, something UTF-8 doesn't support. You can use UTF-8 on a per-a