lukeh

6 ms·

31.
by lukeh 9mo ago
This is also my recollection.
32.
by lukeh 9mo ago
Small nitpick: malloc is not a system call.
33.
by lukeh 9mo ago
And Mach 3 vs 2.5. And a 4.4BSD (well, *BSD) user land, although in fairness the original, never released NEXTSTEP 4.0 also had this.
34.
by lukeh 9mo ago
Another approach is swift-java, which uses Swift macros and also supports Panama. https://github.com/swiftlang/swift-java
35.
by lukeh 9mo ago
That’s sad. One of the first pieces of (serious) software I wrote was licensed by HP for bundling with it. Didn’t use HP-UX a lot but it’s a pity we’re asymptoting towards a Unix monoculture.
36.
by lukeh 9mo ago
Sequential doesn’t mean reentrancy safe, something which has bitten me a few times in Swift concurrency.
37.
by lukeh 10mo ago
Not really! AES67 is essentially RTP with a PTP derived media clock. Connection description uses SDP and unicast signaling uses SIP. Just like VoIP. Also I imagine TDM was first used in telephony.
38.
by lukeh 10mo ago
Yup, similar for audio stuff.
39.
by lukeh 10mo ago
Hard to say. May be related to CarPlay.
40.
by lukeh 10mo ago
Oddly Swift appears to support QNX but there’s not much information about it. https://github.com/swiftlang/swift-testing/issues/868
41.
by lukeh 10mo ago
In the kernel’s process structure. See NOTES - https://man7.org/linux/man-pages/man2/chdir.2.html
42.
Breaking Free from RGB(youtube.com)
3 points by lukeh 10mo ago|0 comments
43.
by lukeh 10mo ago
The first version of MacOS X Server was based on an unreleased version of NEXTSTEP which in turn used 4.4BSD and Mach 2.5. Around BBB 1997-1998 a lot of userland was synced with bits from not just FreeBSD but the other BSD distributions, if
44.
by lukeh 10mo ago
I'm using it for the "business logic" (control plane) in an embedded device. Yocto integration may be useful to others doing same. [1] [1] https://github.com/jeremy-prater/meta-swift
45.
by lukeh 10mo ago
Still rocking a 2019 Mac Pro with 192GB RAM for audio work, because I need the slots and I can’t justify the expense of a new one. But I’m sure a M4 Mini is faster.
46.
by lukeh 11mo ago
Yes, this is correct.
47.
by lukeh 11mo ago
Yeah, emulating syscalls is fine until it isn’t. See WSL1.
48.
by lukeh 11mo ago
I did try to build a medium sized project with this today. Still a lot of dependencies that will need to be updated for the differences between glibc and libc.
49.
by lukeh 11mo ago
My understanding was Foundation and bits of CoreGraphics but not AppKit. Yellow Box required DPS.
50.
by lukeh 11mo ago
Source?
51.
by lukeh 11mo ago
I’m using it on Linux for an embedded product. No reason other than it’s a nice language that I am familiar with and productive in. The async/await features are quite nice too when you need to implement a lot of protocols / state
52.
by lukeh 11mo ago
I wrote one for Swift a few years ago, not sure if anyone else is using it but I am! https://github.com/PADL/IORingSwift
53.
by lukeh 1y ago
I think XMOS can do it (the ones without the GEMAC) but I'm not exactly sure how much hardware assistance they have.
54.
by lukeh 1y ago
AU plugins work, the AU framework itself spins up a separate process to host the translated Intel plugin.
55.
by lukeh 1y ago
And here I was thinking someone had resurrected NeXT's issue tracking system.
56.
by lukeh 1y ago
XMOS (spiritual successor to Inmos) is still kicking around, it’s not without its challenges though, for the reasons you mention.
57.
by lukeh 1y ago
I worked on a Swift ASN.1 compiler [1] a while back (not swift-asn1, mine used Codable). I saved myself some time by using the Heimdal JSON compiler, which can transform ASN.1 into a much more parseable JSON AST. [1] https://gith
58.
by lukeh 1y ago
Also, you can only deduct it in a single financial year if you are eligible for the Instant asset write-off program. I'm sure I'll get downvoted for this, but this common misunderstanding about tax deductions does remind me of a c
59.
by lukeh 1y ago
XMOS still very much alive. But CSP comes with its own set of challenges which ironically have force one back to using shared memory.
60.
by lukeh 1y ago
It was amusing to read the comment about the flat UID/GID namespace being a problem, identified as far back as 1984. This is something that DCE addressed by using a larger namespace (UUIDs), and Windows finally got right using a hierar

More ›