CUJ Gone But Not Forgotten
-
The actual magazine has nothing in it that describes its demise. A cover letter got glued to the face of the magazine. It seems like no one at the magazine knew. All the columnists wrote "...in my next article..." conclusions. Oh, sorry, I looked at the wrong issue laying on the desk. The notice that I received did come with the February 2006 issue, the SECURITY issue. The headlines on the front read Validating C & C++ for Safety and Security Kerberos Authentication Useing GSSAPI & SSPI Recreational Operator Overloading But, of course, when you first get the magazine, all you see is the ugly white paper on front with the letter stating that CUJ has died. "we must lose precision to make significant statements about complex systems." -deKorvin on uncertainty
Curtis S. wrote:
But, of course, when you first get the magazine, all you see is the ugly white paper on front with the letter stating that CUJ has died.
The plot thickens; I have the February issue sitting before me now. There was no white paper stuck to it or anything loose in the mailbox, no remnants of anything stuck to it either. Very strange. I tried contacting customer service and was meet with error messages any which way I tried. I finally gave up and sent an email to one of the editors.
ZeePain! wrote:
This seems like one of those programs that started small, grew incrementally, building internal pressure, and finally barfed all over its source code sneakers. Or something.
-
The actual magazine has nothing in it that describes its demise. A cover letter got glued to the face of the magazine. It seems like no one at the magazine knew. All the columnists wrote "...in my next article..." conclusions. Oh, sorry, I looked at the wrong issue laying on the desk. The notice that I received did come with the February 2006 issue, the SECURITY issue. The headlines on the front read Validating C & C++ for Safety and Security Kerberos Authentication Useing GSSAPI & SSPI Recreational Operator Overloading But, of course, when you first get the magazine, all you see is the ugly white paper on front with the letter stating that CUJ has died. "we must lose precision to make significant statements about complex systems." -deKorvin on uncertainty
I haven't got my latest issue of CUJ. I hope I will be getting that today.. It is very sad to hear that CUJ is stopping.. Are you sure or is it some kind of joke??? -Madhu.
-
-
Indeed, new EU regulations related to reciclable paper lead to situation that this publication is no more allowed in EU. Saying this, the reasons of stopping publishing are clear. Unfortunately, I'm also looking for a replacement. :(
Don Miguel wrote:
Indeed, new EU regulations related to reciclable paper lead to situation that this publication is no more allowed in EU. Saying this, the reasons of stopping publishing are clear.
Huh. Unless the EU's banning magazines altogether this doesn't compute. If the regulation's just requiring a different type of paper than currently used there's no reason they couldn't've switched like all the other affected publications will have to do.
-
I haven't got my latest issue of CUJ. I hope I will be getting that today.. It is very sad to hear that CUJ is stopping.. Are you sure or is it some kind of joke??? -Madhu.
I don't think they would joke about this. Michael Goodman, Publisher, has his name at the bottom of the letter. The mailing label got affixed to this "we're no longer printing CUJ" letter rather than the issue. The refund address points to Boulder, CO, the mail clearing house of America (maybe the world!). If you get your issue and no letter got glued to the front, post here so that I can call CMP and investigate. "we must lose precision to make significant statements about complex systems." -deKorvin on uncertainty
-
Curtis S. wrote:
But, of course, when you first get the magazine, all you see is the ugly white paper on front with the letter stating that CUJ has died.
The plot thickens; I have the February issue sitting before me now. There was no white paper stuck to it or anything loose in the mailbox, no remnants of anything stuck to it either. Very strange. I tried contacting customer service and was meet with error messages any which way I tried. I finally gave up and sent an email to one of the editors.
ZeePain! wrote:
This seems like one of those programs that started small, grew incrementally, building internal pressure, and finally barfed all over its source code sneakers. Or something.
Just called CUJ Customer Service. February 2006 = the last issue of CUJ. So sad. "we must lose precision to make significant statements about complex systems." -deKorvin on uncertainty
-
Christian Graus wrote:
Although, I think more people still use VC6 than I find remotely reasonable.
Yep. Our local downloads for ResOrg (i.e. not including those from CP, for which we don't have metrics) show a 50% split, although that's admittedly a small sample. We're sufficiently concerned about it that we are preparing a version of Visual Lint which will run on VS6 and eVC 4.0 as well as VS2002 onwards. At the very least, it's proving to be an interesting excercise in interface abstraction and UI customisation. Subclassing, anyone? :doh: Anna :rose: Currently working mostly on: Visual Lint :cool: Anna's Place | Tears and Laughter "Be yourself - not what others think you should be" - Marcia Graesch "Anna's just a sexy-looking lesbian tart" - A friend, trying to wind me up. It didn't work.
Yeah, I am working on the Ultimate Grid code at the moment, same deal. Needs to support VC6,2002, 2003, 2005 with no warnings or errors. It's all fun and games. Christian Graus - Microsoft MVP - C++
-
Yeah, I am working on the Ultimate Grid code at the moment, same deal. Needs to support VC6,2002, 2003, 2005 with no warnings or errors. It's all fun and games. Christian Graus - Microsoft MVP - C++
I can imagine! Working with the VC6 version of STL again must be painful. X| We're a little luckier in that with Visual Lint we don't have to support VS6 at the code level - the compiled product just has to work with it. Even then, it's not at all easy, given the crappy automation interface VS6 and eVC 4 have! Anna :rose: Currently working mostly on: Visual Lint :cool: Anna's Place | Tears and Laughter "Be yourself - not what others think you should be" - Marcia Graesch "Anna's just a sexy-looking lesbian tart" - A friend, trying to wind me up. It didn't work.
-
I can imagine! Working with the VC6 version of STL again must be painful. X| We're a little luckier in that with Visual Lint we don't have to support VS6 at the code level - the compiled product just has to work with it. Even then, it's not at all easy, given the crappy automation interface VS6 and eVC 4 have! Anna :rose: Currently working mostly on: Visual Lint :cool: Anna's Place | Tears and Laughter "Be yourself - not what others think you should be" - Marcia Graesch "Anna's just a sexy-looking lesbian tart" - A friend, trying to wind me up. It didn't work.
Anna-Jayne Metcalfe wrote:
Working with the VC6 version of STL again must be painful.
Oh, yeah. I used a map, and I had to put it in an anonymous namespace instead of as a member variable, because we also can't be turning off warnings across the library, the stupid 'your mangled name is > 255 chars' warning is now only turned off within the one file. Christian Graus - Microsoft MVP - C++
-
Anna-Jayne Metcalfe wrote:
Working with the VC6 version of STL again must be painful.
Oh, yeah. I used a map, and I had to put it in an anonymous namespace instead of as a member variable, because we also can't be turning off warnings across the library, the stupid 'your mangled name is > 255 chars' warning is now only turned off within the one file. Christian Graus - Microsoft MVP - C++
Yuck. X| X| X| Anna :rose: Currently working mostly on: Visual Lint :cool: Anna's Place | Tears and Laughter "Be yourself - not what others think you should be" - Marcia Graesch "Anna's just a sexy-looking lesbian tart" - A friend, trying to wind me up. It didn't work.
-
Just called CUJ Customer Service. February 2006 = the last issue of CUJ. So sad. "we must lose precision to make significant statements about complex systems." -deKorvin on uncertainty
Curtis S. wrote:
Just called CUJ Customer Service.
Care to share thier number? If your not comfortable posting it send it via email. Thanks.
ZeePain! wrote:
This seems like one of those programs that started small, grew incrementally, building internal pressure, and finally barfed all over its source code sneakers. Or something.
-
I don't think they would joke about this. Michael Goodman, Publisher, has his name at the bottom of the letter. The mailing label got affixed to this "we're no longer printing CUJ" letter rather than the issue. The refund address points to Boulder, CO, the mail clearing house of America (maybe the world!). If you get your issue and no letter got glued to the front, post here so that I can call CMP and investigate. "we must lose precision to make significant statements about complex systems." -deKorvin on uncertainty
Curtis S. wrote:
If you get your issue and no letter got glued to the front, post here so that I can call CMP and investigate.
So far it only looks like me... :confused:
ZeePain! wrote:
This seems like one of those programs that started small, grew incrementally, building internal pressure, and finally barfed all over its source code sneakers. Or something.
-
Curtis S. wrote:
Just called CUJ Customer Service.
Care to share thier number? If your not comfortable posting it send it via email. Thanks.
ZeePain! wrote:
This seems like one of those programs that started small, grew incrementally, building internal pressure, and finally barfed all over its source code sneakers. Or something.
1-800-365-1364 "we must lose precision to make significant statements about complex systems." -deKorvin on uncertainty
-
1-800-365-1364 "we must lose precision to make significant statements about complex systems." -deKorvin on uncertainty
-
Funny you mention that - one of my image processing articles is basically one of the DDJ articles. The other was on Koenig lookup, and VC2002 come out while I was waiting, so the issue became moot. Although, I think more people still use VC6 than I find remotely reasonable. Christian Graus - Microsoft MVP - C++
Just wondering, are the Image Processing for Dummies series of articles here on Code Project along the lines of what you submitted to DDJ (perhaps under a different title, with "dummies" taken out)? Paul
-
Just wondering, are the Image Processing for Dummies series of articles here on Code Project along the lines of what you submitted to DDJ (perhaps under a different title, with "dummies" taken out)? Paul
The displacement filters article is essentially what I sent to DDJ. Christian Graus - Microsoft MVP - C++
-
The displacement filters article is essentially what I sent to DDJ. Christian Graus - Microsoft MVP - C++
The displacement filter article is really cool. Too bad they didn't publish it, but hey, it's on Code Project :) Paul
-
1-800-365-1364 "we must lose precision to make significant statements about complex systems." -deKorvin on uncertainty
Not that I doubted you but I called them and indeed they have canceled publication. I am now the proud subscriber to Dr Dobbs until 2010.
ZeePain! wrote:
This seems like one of those programs that started small, grew incrementally, building internal pressure, and finally barfed all over its source code sneakers. Or something.
-
Not that I doubted you but I called them and indeed they have canceled publication. I am now the proud subscriber to Dr Dobbs until 2010.
ZeePain! wrote:
This seems like one of those programs that started small, grew incrementally, building internal pressure, and finally barfed all over its source code sneakers. Or something.
Wow, that's really cool. I like Dr Dobb's and I have to renew it pretty soon myself :)
-
Wow, that's really cool. I like Dr Dobb's and I have to renew it pretty soon myself :)
computerguru92382 wrote:
I like Dr Dobb's
Dr Dobb's is good, just not quite CUJ, :shrugs: oh well its mostly bathroom reading material now days. :) :java: Again thanks for the heads up.
ZeePain! wrote:
This seems like one of those programs that started small, grew incrementally, building internal pressure, and finally barfed all over its source code sneakers. Or something.
