2,455 karma · joined June 25, 2009
[1] http://www.cyprusembassy.fi/main/index.php?p=Consular_Sectio...
Tracing and telemetry. Debuggers are very useful, but only when they're needed. In fact, in large distributed systems 'debugging' end-to-end bugs is usually hindered with a debugger.
As an aside, even when I have to use a debugger during runtime, the largest part of my interaction with it is heavily scripted, and the debugging process is not interactive.
If that were true, it'd be one more reason not to try to give credence to unfalsifiable publications by linking them to experts of various fields, or even editors-who-once-took-a-course-on-T.
But I think it's not true at all. The thought process on most publications like Economist is one most people can follow for its validity, precisely because it's not state-of-the-art mathematics (or even economics). Even though the domain experts can immediately judge its correctness, I think it's important for anyone to be able to at least identify when they're reading something they can't verify as correct, and not take publication X's "word" for it.
> Editors are a thing.
Editors are there to make sure the news piece conforms to certain standards, but that's not the standards of the readers.
> If you already know whether or not the Economist is correct about something, what value are you getting from reading it?
That was nowhere near my point, and I don't see why you base your comment around it. My point is I am (or want to be) able to read a piece and judge it on its own, rather than who wrote it.
I think it's the content of a text, not its label, that displays understanding and experience. Arguing only experts should be writing for X because it puts on an air of expertise is getting causality backwards: a publication gets its reputation from its work.
I just fail to understand the logic exercised by some US residents. Norquist's argument is insane, and if you're not only trying to be kind to it and not call it as such, your stance towards it seems insane to me too.
Linux's NIH syndrome, however unfortunate it is, has not expanded into its unix roots. (yet?)
That's right. Threads share everything but their stack.
> Does this mean that there is a missed optimization on Linux to preserve some virtually-addressed caches and tables when switching to thread/process that shares the same address space?
I'm not entirely sure I understand your question. What scenario do you have in mind?
I think not.
I hope I don't have to go through all the reasons this is fundamentally disconnected from the problem described in the article now.
It's obvious to me we both can, so why the hell are you wasting our time with useless pedantry?