3 Jul 2025 |
Zhaofeng Li | oh right, speaking of fancy filesystems, quickly checked on refs on windows and it's still nowhere to be seen? | 00:58:54 |
Katalin 🔪 | oh yeah, that’s microsoft’s supposed new FS, right? I remember hearing about that a while ago | 00:59:21 |
Katalin 🔪 | supposedly it was introduced with windows server 2012 | 01:00:03 |
Randy Eckenrode | Isn’t refs pretty old by now? | 01:00:05 |
Katalin 🔪 | I guess not that old, but post-NTFS | 01:00:15 |
Randy Eckenrode | I miss the fancy attribute stuff BeOS did. | 01:00:19 |
Katalin 🔪 | * | 01:00:19 |
Randy Eckenrode | Email is just files in the filesystem. | 01:00:24 |
Zhaofeng Li | yeah, not sure what the strategy is, why do they look like they want to paywall everything?
The ability to create ReFS volumes was removed in Windows 10's 2017 Fall Creators Update for all editions except Enterprise and Pro for Workstations.
but it does look like it's getting updated
https://en.wikipedia.org/wiki/ReFS
| 01:00:29 |
Zhaofeng Li | * yeah, not sure what the strategy is, why does it look like they want to paywall everything?
The ability to create ReFS volumes was removed in Windows 10's 2017 Fall Creators Update for all editions except Enterprise and Pro for Workstations.
oh actually should have read further down, looks like this refs-based "dev drive" feature is generally available now: https://learn.microsoft.com/en-us/windows/dev-drive/
https://en.wikipedia.org/wiki/ReFS
| 01:02:05 |
Randy Eckenrode | ReFS doesn’t support xattrs? | 01:05:34 |
samasaur | also i have hopes that the @unsafe attribute and corresponding keyword may mean that the verbosity of things like the Unsafe*Pointer family goes down | 01:06:09 |
samasaur | no official word on that and it'd be a ways out but I see a path where it could happen | 01:06:44 |
Zhaofeng Li | unsure, maybe it does? but I guess it's not the most important thing | 01:09:25 |
Zhaofeng Li | the more interesting things in "cool" filesystems nowadays being cow, snapshot, checksums, etc | 01:10:10 |
Katalin 🔪 | speaking of pointer stuff, behold: QString.init(string:)
extension QString {
public init(string: String?) {
#if os(macOS)
self = QString.fromNSString(string)
#else
guard let string else {
self = QString()
return
}
self = string.withCString(encodedAs: UTF16.self) { data in
QString(
UnsafeRawPointer(data).bindMemory(to: QChar.self, capacity: string.utf16.count),
qsizetype(string.utf16.count))
}
#endif
}
}
| 01:10:16 |
Katalin 🔪 | the other way around is actually a lot more ugly | 01:11:04 |
Zhaofeng Li | QString... qt? | 01:12:17 |
Katalin 🔪 | yeah | 01:12:24 |
Randy Eckenrode | Is that using C++ interop? | 01:12:46 |
Katalin 🔪 | yeah | 01:12:54 |
Zhaofeng Li | and you know what, I also get the use-case for non-macOS... | 01:13:06 |
Katalin 🔪 | the full thing: https://paste.sr.ht/~dblsaiko/ba4810c92637b0e3a3b56076e53b292c778f28ac | 01:13:24 |
| * Zhaofeng Li went into a rabbit hole with the android client of quassel a while ago, and it had a bespoke qt binding | 01:13:54 |
Zhaofeng Li | because the whole thing is based QDataStreams | 01:14:41 |
Zhaofeng Li | * because the whole thing is based on QDataStreams | 01:14:51 |
Katalin 🔪 | that has an android port? huh | 01:17:18 |
Katalin 🔪 | the IRC client? | 01:17:24 |
Zhaofeng Li | yeah, but it was the best bouncer that I had used before I tried IRCCloud | 01:18:05 |
Katalin 🔪 | ah, makes sense | 01:18:36 |