Different risk assessments. DTrace is a non-critical tool, and a totally standalone one. If it suddenly had to be yanked out of macOS because of licensing issues, there would be gnashing of teeth but life would ultimately go on. The filesystem is a different story: if something happened and it had to be immediately removed, Apple would be up shit creek.
I think the point is you can rip the kernel components out, and the (non-Dtrace using dev) user doesn't notice. Whereas removing a filesystem driver leaves users without their data.
You're still comparing, at most, a handful of applications that would need to be removed or updated vs. an entire filesystem that everything is built upon.
Different risk assessments. DTrace is a non-critical tool, and a totally standalone one. If it suddenly had to be yanked out of macOS because of licensing issues, there would be gnashing of teeth but life would ultimately go on. The filesystem is a different story: if something happened and it had to be immediately removed, Apple would be up shit creek.
Yep, this was more or less exactly how the conversation went.
What about this? Does this change anything?
https://gnu.wildebeest.org/blog/mjw/2018/02/14/dtrace-for-li...
2 replies →
It's not totally standalone (it has kernel components, for example), but yes, it's clearly something far easier to suddenly drop.
I think the point is you can rip the kernel components out, and the (non-Dtrace using dev) user doesn't notice. Whereas removing a filesystem driver leaves users without their data.
Mojave drops support for DTrace probes in Instruments, so this process may already have begun.
6 replies →
Doesn't instruments and activity monitor build on top of Dtrace in MacOS? Which if true doesn't seem so easy to rip out.
You're still comparing, at most, a handful of applications that would need to be removed or updated vs. an entire filesystem that everything is built upon.
1 reply →