3 ms·
Great direction! One of the lesser known but really nifty bits of NeXTStep was DriverKit: http://www.nextcomputers.org/NeXTfiles/Software/OPENSTEP/Developer/D
by mpweiher 8y ago
Great direction! One of the lesser known but really nifty bits of NeXTStep was DriverKit:
http://www.nextcomputers.org/NeXTfiles/Software/OPENSTEP/Developer/DriverKit/DriverKit.pdf http://www.nextcomputers.org/NeXTfiles/Software/OPENSTEP/Dev...
Objective-C was a great match for driver development, devices tended to have a very natural OO flavour to them and naturally sorted into classes.
Putting things in user-space seemed a natural extension, that sadly didn't happen at the time even though Mach had the hooks for it (we never got user-level pagers either, which would have rocked together with garbage collected languages). There certainly didn't seem to be a good reason why I had to reboot the machine and wait for fsck when there was a minor bug in the little driver I was writing to talk to an EISA printer controller that had nothing to do with the basic functioning of the system...
(Why would a printer controller be on an EISA controller, you ask? It directly drove a Canon Laser Copier, so, yes!)
Oh, and not surprised by the abysmal Swift performance. Alas, Apple's marketing of Swift as a "high-performance" language has been very successful despite all the crushing evidence to the contrary.
- saagarjha 8y ago> Objective-C was a great match for driver development, devices tended to have a very natural OO flavour to them and naturally sorted into classes. How do you feel about the current state of driver development on macOS, with Objective-C basically being replaced with Embedded C++ with partial reflection?
- mpweiher 8y agoIt was part appeasement of the "never Objective-C" crowd (hello CoreFoundation, hello CocoaJava, hello Swift) and part the exact sentiment discussed here, that you cannot possibly do kernel development in a higher level language. What I heard (quite some time ago) is that this move is now seen as a mistake.
- mrpippy 8y agoObjC was definitely seen as a dead-end at the time: it would either be replaced with Java, or maybe Mac developers would just stick with Carbon and C/C++. Either way, all driver development (on classic Mac, Windows, Unix) was in C, and C++ would be much more familiar than the “weird obsolete square-brackets NeXT language” I made a post a few years ago discussing the issue: https://news.ycombinator.com/item?id=10006411 https://news.ycombinator.com/item?id=10006411