4 ms·
Two things here: - If you use Dtrace to troubleshoot a problem it's way beyond your scope of knowledge as a web developer. Dtrace is too deep and very specific
by Thaxll 12y ago
Two things here:
- If you use Dtrace to troubleshoot a problem it's way beyond your scope of knowledge as a web developer. Dtrace is too deep and very specific to certain problems that you will never see because your regular nginx + php works fine in all cases.
- Not everyone wants and should be good at everything.
Just be good at what your doing well, I'm not saying that one shouldn't be curious but Dtrace isn't "an excuse" to install *BSD as a web dev.
- 4ad 12y agoIf you don't use DTrace to debug php, you're missing a lot: http://php.net/manual/en/features.dtrace.dtrace.php http://php.net/manual/en/features.dtrace.dtrace.php. Same for python and ruby and node.js. All these have DTrace support. DTrace is not hard, it's essential; and it's significantly easier, than say, awk, which is another crucial tool.
- bitroliest 12y agoUnder OSX it seems that DTrace support is incomplete thanks to OSX' dtrace implementation [1]. [1] https://github.com/joyent/node/issues/3617 https://github.com/joyent/node/issues/3617 I think only Solaris has full support?