My typical Emacs session has 3-4 Shell Mode buffers, each typically with tens of thousands of lines of input and output (often spanning weeks or months of work). I watch co-workers running in xterms (or equivalent), running commands repeatedly to see their output or using "more" (or "less"), or not catching or remembering some error message or whatever and I just cringe internally. I want to scream "It's 2016--you can have a searchable record of more than the last screenful of output!". But I don't:-)
I explicitly try to extend my Emacs skills periodically and it's had great pay-off. Earlier this year a co-worker introduced me to Magit (a Git UI that runs inside Emacs). It took a little while to get the hang of it, but it's been a life-changer. Check it out.
-- Happy Emacs user since 1980.
OK, so in my previous life I was one of the lead architects, project leads, and implementers of the DCE. I was "present at the creation". (Actually, present before the creation, having served the same role at Apollo for NCS, the predecessor of DCE RPC.) Which is all a way of saying that (modulo brain cells lost in the intervening 10+ years), I think my account of this topic should be reasonably good.
Like Microsoft or not, but they in no way "stole" DCE RPC any more than anyone who implements RFC 793 "stole" TCP. Microsoft read publicly available protocol and API specifications and wrote their implementation based on it. (They probably got some help understanding those specs from Digital Equipment Corp., a partner of theirs at the time and a co-developer of DCE RPC.) A willingness on Microsoft's part to not design the whole thing from scratch counts in their favor, I think.
In contrast to all the companies that funded the development of DCE RPC, Microsoft actually put their implementation of the specs to good use themselves, building much of their distributed system infrastructure around it. (It has at least the small benefit that it makes me feel less like my years of effort on DCE were a complete waste of time:-)
Slashdot Mirror
My typical Emacs session has 3-4 Shell Mode buffers, each typically with tens of thousands of lines of input and output (often spanning weeks or months of work). I watch co-workers running in xterms (or equivalent), running commands repeatedly to see their output or using "more" (or "less"), or not catching or remembering some error message or whatever and I just cringe internally. I want to scream "It's 2016--you can have a searchable record of more than the last screenful of output!". But I don't :-)
I explicitly try to extend my Emacs skills periodically and it's had great pay-off. Earlier this year a co-worker introduced me to Magit (a Git UI that runs inside Emacs). It took a little while to get the hang of it, but it's been a life-changer. Check it out.
-- Happy Emacs user since 1980.
Like Microsoft or not, but they in no way "stole" DCE RPC any more than anyone who implements RFC 793 "stole" TCP. Microsoft read publicly available protocol and API specifications and wrote their implementation based on it. (They probably got some help understanding those specs from Digital Equipment Corp., a partner of theirs at the time and a co-developer of DCE RPC.) A willingness on Microsoft's part to not design the whole thing from scratch counts in their favor, I think.
In contrast to all the companies that funded the development of DCE RPC, Microsoft actually put their implementation of the specs to good use themselves, building much of their distributed system infrastructure around it. (It has at least the small benefit that it makes me feel less like my years of effort on DCE were a complete waste of time :-)