• Nagesh (unregistered) in reply to anonymouser
    anonymouser:
    Nagesh:
    Here in Hyderabad, "taking dump" is youfamisim for defacation.

    Here it's a euphemism for going to Hyderabad.

    My home this is!

  • Luiz Felipe (unregistered) in reply to ɥsǝbɐu
    ɥsǝbɐu:
    L.:

    And for people who like to talk shit about C, please remember it is the only language that will still exist twenty years from now, because unlike Java, C#, ruby and others it meets its objectives : simple ASM translation - all others having various amount of fail and fancy stuff built-in, but none ultimately filling a purpose.

    Java will die because it's slow (anything slower than C++ is slow), heavy(private static final ultimate final again var of doom var1=0;), useless on Windows (no comment), and overall as Johnny said, the best way to create clueless programmers by protecting them from their major mistakes and misunderstandings.

    C++ will die because it's not modern enough and it's quite realistic to imagine a "better" C++.

    Countless others will die . but C will remain - unless anyone has a better idea of a programming language that is as efficient as C ?

    VB.NET is obvius going to stay.

    Basic will stay forever, same with C. Java, cSharp, c++ will die like cobol.

  • (cs) in reply to Luiz Felipe
    Luiz Felipe:
    ɥsǝbɐu:
    L.:

    And for people who like to talk shit about C, please remember it is the only language that will still exist twenty years from now, because unlike Java, C#, ruby and others it meets its objectives : simple ASM translation - all others having various amount of fail and fancy stuff built-in, but none ultimately filling a purpose.

    Java will die because it's slow (anything slower than C++ is slow), heavy(private static final ultimate final again var of doom var1=0;), useless on Windows (no comment), and overall as Johnny said, the best way to create clueless programmers by protecting them from their major mistakes and misunderstandings.

    C++ will die because it's not modern enough and it's quite realistic to imagine a "better" C++.

    Countless others will die . but C will remain - unless anyone has a better idea of a programming language that is as efficient as C ?

    VB.NET is obvius going to stay.

    Basic will stay forever, same with C. Java, cSharp, c++ will die like cobol.

    I think it's pretty safe to say that any programming langauge that was popular for any significant period of time will be around for a very long time simply for maintenance reasons.

    For example, there won't be any new development done in cobol or fortran, but there are countless organizations which still have apps written in these languages but the cost would be astronomical to replace (design, develop, test) with any given modern langauge/platform.

  • Nagesh (unregistered) in reply to C-Octothorpe
    C-Octothorpe:
    I think it's pretty safe to say that any programming langauge that was popular for any significant period of time will be around for a very long time simply for maintenance reasons.

    For example, there won't be any new development done in cobol or fortran, but there are countless organizations which still have apps written in these languages but the cost would be astronomical to replace (design, develop, test) with any given modern langauge/platform.

    This is good oportunity to be use code confurter. Questian to be: what langauge to be writing confurter in?

    Filed under: XML
  • (cs) in reply to Nagesh
    Nagesh:
    C-Octothorpe:
    I think it's pretty safe to say that any programming langauge that was popular for any significant period of time will be around for a very long time simply for maintenance reasons.

    For example, there won't be any new development done in cobol or fortran, but there are countless organizations which still have apps written in these languages but the cost would be astronomical to replace (design, develop, test) with any given modern langauge/platform.

    This is good oportunity to be use code confurter. Questian to be: what langauge to be writing confurter in?

    Filed under: XML
    Perl, of course...
  • (cs) in reply to Luiz Felipe
    Luiz Felipe:
    Basic will stay forever, same with C. Java, cSharp, c++ will die like cobol.
    Except that COBOL won't die!
  • É¥sǝbɐu (unregistered) in reply to C-Octothorpe
    C-Octothorpe:
    Luiz Felipe:
    ɥsǝbɐu:
    L.:

    And for people who like to talk shit about C, please remember it is the only language that will still exist twenty years from now, because unlike Java, C#, ruby and others it meets its objectives : simple ASM translation - all others having various amount of fail and fancy stuff built-in, but none ultimately filling a purpose.

    Java will die because it's slow (anything slower than C++ is slow), heavy(private static final ultimate final again var of doom var1=0;), useless on Windows (no comment), and overall as Johnny said, the best way to create clueless programmers by protecting them from their major mistakes and misunderstandings.

    C++ will die because it's not modern enough and it's quite realistic to imagine a "better" C++.

    Countless others will die . but C will remain - unless anyone has a better idea of a programming language that is as efficient as C ?

    VB.NET is obvius going to stay.

    Basic will stay forever, same with C. Java, cSharp, c++ will die like cobol.

    I think it's pretty safe to say that any programming langauge that was popular for any significant period of time will be around for a very long time simply for maintenance reasons.

    For example, there won't be any new development done in cobol or fortran, but there are countless organizations which still have apps written in these languages but the cost would be astronomical to replace (design, develop, test) with any given modern langauge/platform.

    Surely you're joking. The programming language might be around, but the businesses will be wise enough to pull the plug from any applications developed in it.

  • É¥sǝbɐu (unregistered) in reply to havokk
    havokk:
    Luiz Felipe:
    Basic will stay forever, same with C. Java, cSharp, c++ will die like cobol.
    Except that COBOL won't die!

    Truer words have never been spoken.

  • (cs) in reply to PedanticCurmudgeon
    PedanticCurmudgeon:
    L.:
    Countless others will die . but C will remain - unless anyone has a better idea of a programming language that is as efficient as C ?
    Why not Forth?

    Because in the Bible it says it's not as good as the tried-and-tested method of using the "times" arithmetical function.

    "Go, Forth, and multiply."

  • (cs) in reply to É¥sǝbɐu
    ɥsǝbɐu:
    C-Octothorpe:
    Luiz Felipe:
    ɥsǝbɐu:
    L.:

    And for people who like to talk shit about C, please remember it is the only language that will still exist twenty years from now, because unlike Java, C#, ruby and others it meets its objectives : simple ASM translation - all others having various amount of fail and fancy stuff built-in, but none ultimately filling a purpose.

    Java will die because it's slow (anything slower than C++ is slow), heavy(private static final ultimate final again var of doom var1=0;), useless on Windows (no comment), and overall as Johnny said, the best way to create clueless programmers by protecting them from their major mistakes and misunderstandings.

    C++ will die because it's not modern enough and it's quite realistic to imagine a "better" C++.

    Countless others will die . but C will remain - unless anyone has a better idea of a programming language that is as efficient as C ?

    VB.NET is obvius going to stay.

    Basic will stay forever, same with C. Java, cSharp, c++ will die like cobol.

    I think it's pretty safe to say that any programming langauge that was popular for any significant period of time will be around for a very long time simply for maintenance reasons.

    For example, there won't be any new development done in cobol or fortran, but there are countless organizations which still have apps written in these languages but the cost would be astronomical to replace (design, develop, test) with any given modern langauge/platform.

    Surely you're joking. The programming language might be around, but the businesses will be wise enough to pull the plug from any applications developed in it.

    Not at all. If the app works well enough, and the customer's happy with the service it provides, where's the reason to upgrade? Your buggy old shit written in C and C++ and Java, certainly, because you dipsticks can't write in that to save your pissy lives, so there's bound to be continual upgrades there. But a solid old application in an elderly 3gl e.g. COBOL and FORTRAN (particularly FORTRAN) needs a serious stresser to get the customer to agree to an upgrade.

  • (cs) in reply to É¥sǝbɐu
    ɥsǝbɐu:
    C-Octothorpe:
    Luiz Felipe:
    ɥsǝbɐu:
    L.:

    And for people who like to talk shit about C, please remember it is the only language that will still exist twenty years from now, because unlike Java, C#, ruby and others it meets its objectives : simple ASM translation - all others having various amount of fail and fancy stuff built-in, but none ultimately filling a purpose.

    Java will die because it's slow (anything slower than C++ is slow), heavy(private static final ultimate final again var of doom var1=0;), useless on Windows (no comment), and overall as Johnny said, the best way to create clueless programmers by protecting them from their major mistakes and misunderstandings.

    C++ will die because it's not modern enough and it's quite realistic to imagine a "better" C++.

    Countless others will die . but C will remain - unless anyone has a better idea of a programming language that is as efficient as C ?

    VB.NET is obvius going to stay.

    Basic will stay forever, same with C. Java, cSharp, c++ will die like cobol.

    I think it's pretty safe to say that any programming langauge that was popular for any significant period of time will be around for a very long time simply for maintenance reasons.

    For example, there won't be any new development done in cobol or fortran, but there are countless organizations which still have apps written in these languages but the cost would be astronomical to replace (design, develop, test) with any given modern langauge/platform.

    Surely you're joking. The programming language might be around, but the businesses will be wise enough to pull the plug from any applications developed in it.

    Why would they pull the plug from a working application? Becuase it's written in an old programming lanauge running on a mainframe? Have you ever heard of the phrase: If it ain't broke, don't fix it.

    Imagine I'm a wealthy investor whose IT expertise stops at "my emails are sent across the intertubes via unicorn farts". Now convince me that I need to pay to have an old, but reliable FORTRAN application rewritten because it's old. And don't forget the costs of design, development, testing and the very likely scenario that it won't perform any better and that you're potentially introducing many new bugs.

    Ready... GO!

  • (cs) in reply to C-Octothorpe
    C-Octothorpe:
    I think it's pretty safe to say that any programming langauge that was popular for any significant period of time will be around for a very long time simply for maintenance reasons.

    For example, there won't be any new development done in cobol or fortran, but there are countless organizations which still have apps written in these languages but the cost would be astronomical to replace (design, develop, test) with any given modern langauge/platform.

    +1, QFT. I once worked at a place (major supplier of financial information services) which had an enormous, and I mean tens of millions of LoC, codebase, mostly an unholy mix of Fortran and C, and with a growing amount of C++ and JavaScript. That's JavaScript on the server, running against a GTK binding to display information remotely. There was eventually a moratorium on new Fortran source files being added, but that just drove the Fortran-preferrers to add all their new code to existing files. Anyway, much of the C was written by Fortran programmers, and it showed.

    In fact, the fanboi-ism toward Fortran was such that one chap, on an internal forum, called C "the asbestos of programming languages" and asserted that Fortran was a vastly superior alternative. OK, C takes more discipline to use correctly than something like Java, but with Fortran as a superior alternative for general programming?!?

    This place also taught me that old data formats also don't die. Every machine that ran any part of the system had native IEEE754 floating point and yet the ancient history of the system meant that a large number of database layouts (term used loosely, mind you) and wire formats used what were known as "PE floats", but were actually in IBM System/360 format. (The old "PE" machines used S/360 floating point, that's why.)

  • DT (unregistered) in reply to Troll

    Noticed it too

  • L. (unregistered)

    Well .. of course Fortran rocks . but it's already dead so that's different ;)

  • (cs) in reply to L.
    L.:
    Well .. of course Fortran rocks . but it's already dead so that's different ;)

    I believe that it is in fact not dead. It is, for example, used throughout such establishments as the Meteorological Office, because it has significant advantages in the processing of large quantities of mathematical modelling information. While Java and c++ etc may have a few advantages in the realms of financial information where the emphasis is on where the data is and who can see it (rather than on the details of exactly what those numbers are and how they are calculated from other numbers), when it comes to pure numerical calcs, you can do considerably worse than an environment that runs massively-parallel processes running FORTRAN.

    Fanboi I'm not - I much prefer to write in Java nowadays - but for certain applications I would prefer FORTRAN over anything.

  • Nagesh (unregistered) in reply to C-Octothorpe
    C-Octothorpe:
    Why would they pull the plug from a working application? Becuase it's written in an old programming lanauge running on a mainframe? Have you ever heard of the phrase: If it ain't broke, don't fix it.

    Investors are being smart. Cost of manetenance on unown lanegauge often more than cost of manetenance on well-nown system (preferable Java).

    C-Octothorpe:
    Imagine I'm a wealthy investor whose IT expertise stops at "my emails are sent across the intertubes via unicorn farts".
    Not understand what ur saying.
    C-Octothorpe:
    Now convince me that I need to pay to have an old, but reliable FORTRAN application rewritten because it's old.
    Using f2c to convert from fortran to c, and then simplicity to convert c to Java.
    C-Octothorpe:
    And don't forget the costs of design, development, testing and the very likely scenario that it won't perform any better and that you're potentially introducing many new bugs.
    Identically situation as before. Evan legacy aplication have bugs.
    Don't be a H8R.

    I undertake project in java, if you need help with homework, contact me.

  • Nagesh (unregistered)

    Sem to me...real wtf is expect to have everyday artical.

    Don't be a H8R.

    I undertake project in java, if you need help with homework, contact me.

  • (cs) in reply to C-Octothorpe
    C-Octothorpe:
    Imagine I'm a wealthy investor whose IT expertise stops at "my emails are sent across the intertubes via unicorn farts". Now convince me that I need to pay to have an old, but reliable FORTRAN application rewritten because it's old. And don't forget the costs of design, development, testing and the very likely scenario that it won't perform any better and that you're potentially introducing many new bugs.

    Ready... GO!

    Easy. "The old application doesn't use unicorn farts." The said investor knows nothing of Fortran, application reliability, and the like, but he does know that to get any of that internet stuff, you need unicorn farts.

    I want my investors to understand something of what I do, at least at the broad strokes level. No, they don't need to understand where to put the semicolons in a C for() statement, but I want them to know that flatulent one-horned animals are not a component of any software-based system.

  • (cs) in reply to L.
    L.:
    And for people who like to talk shit about C, please remember it is the only language that will still exist twenty years from now, because unlike Java, C#, ruby and others it meets its objectives : simple ASM translation - all others having various amount of fail and fancy stuff built-in, but none ultimately filling a purpose.
    Hang on, what of Java's objectives aren't met? You could argue about performance, maybe, but simplicity, security, platform-independence... yup, all there.
    Java will die because it's slow (anything slower than C++ is slow), heavy(private static final ultimate final again var of doom var1=0;), useless on Windows (no comment), and overall as Johnny said, the best way to create clueless programmers by protecting them from their major mistakes and misunderstandings.
    Perhaps you haven't noticed, but Windows is on the decline, and things like iOS and Android are on the incline. And what again is Android based on? Riiiight.

    Also, because you have a problem with the discipline that Java's syntax requires from you, doesn't make it a bad language.

    "Java is slow", well, no. Would I write a 3D FPS in it? Most likely not. Would productivity software be quick enough with it? Of course it would. Java is fast enough for everything except the highest computational requirements, including stuff that runs on your bluray player. Or are you saying that you have a Core i7 in your bluray player?

    The major problem with Java (which ironically you didn't mention, presumably because you don't know WTF you're talking about) is its memory usage.

    C++ will die because it's not modern enough and it's quite realistic to imagine a "better" C++.
    C++ will not die completely, for the simple reason that there are already "better" C++-s. They're called Java and C#. But it does offer object-oriented programming and exception handling whilst retaining the attractive properties of Java, at the cost of complexity and lack of memory management.
    Countless others will die . but C will remain - unless anyone has a better idea of a programming language that is as efficient as C ?
    Writing the same thing in Java takes me far less time to develop and debug than it does in C, not to mention the time that the maintenance people have to spend. Perhaps you've been living under a rock for the past 20 years, but the people that pay your salary know that a good developer is a lot more expensive than some extra CPU power, memory, and air conditioning.

    Perhaps that's not the case for you as a developer, and that wouldn't surprise me at all, given the utter cluelessness you portray.

  • (cs) in reply to Steve The Cynic
    Steve The Cynic:
    C-Octothorpe:
    Imagine I'm a wealthy investor whose IT expertise stops at "my emails are sent across the intertubes via unicorn farts". Now convince me that I need to pay to have an old, but reliable FORTRAN application rewritten because it's old. And don't forget the costs of design, development, testing and the very likely scenario that it won't perform any better and that you're potentially introducing many new bugs.

    Ready... GO!

    Easy. "The old application doesn't use unicorn farts." The said investor knows nothing of Fortran, application reliability, and the like, but he does know that to get any of that internet stuff, you need unicorn farts.

    I want my investors to understand something of what I do, at least at the broad strokes level. No, they don't need to understand where to put the semicolons in a C for() statement, but I want them to know that flatulent one-horned animals are not a component of any software-based system.

    The point I was trying to get across was that for an investor, he/she would see a lot of variables: cost, time, effort, end product quality, etc., which spells a lot of risk for something that may or may not be a better product in the end.

    I develop all my stuff in .Net 4 (C#), and I think all new development should obviously be on a modern platform and language. But I even have a hard time convincing myself that an old app running on an AS400 should be rebuilt simply because it's old. If you think about it, that product has had decades of QA and is probably rock solid.

    Now if there is a solid reason like reliability issues or some technical limitation which presents as a high risk, then you'll obviously have to develop from something from scratch.

  • (cs) in reply to C-Octothorpe
    C-Octothorpe:
    Why would they pull the plug from a working application? Becuase it's written in an old programming lanauge running on a mainframe? Have you ever heard of the phrase: If it ain't broke, don't fix it.
    Don't be so sure. While I certainly agree with your sentiments and think it's ludicrous to replace a working application just because the technology is "outdated", consider how many in the industry make important multi-million dollar decisions based entirely on fashion. If the latest tech magazine says all our competitors are ditching their mainframes, you can bet my company's decision-makers will follow suit.
  • (cs) in reply to Severity One
    Severity One:
    L.:
    And for people who like to talk shit about C, please remember it is the only language that will still exist twenty years from now, because unlike Java, C#, ruby and others it meets its objectives : simple ASM translation - all others having various amount of fail and fancy stuff built-in, but none ultimately filling a purpose.
    Hang on, what of Java's objectives aren't met? You could argue about performance, maybe, but simplicity, security, platform-independence... yup, all there.
    Wait, what? Are you really saying that different programming languages were designed with entirely different objectives in mind?

    Yeah right, next you'll be saying that different problems call for different solutions.

  • (cs) in reply to Nagesh
    Nagesh (fake):
    C-Octothorpe:
    Imagine I'm a wealthy investor whose IT expertise stops at "my emails are sent across the intertubes via unicorn farts".
    Not understand what ur saying.
    I was trying to highlight the fact that investors, stakeholders, what have you are only interested in ROI and risk. Rewriting something because it's old presents a lot of risk without a lot of ROI.
    Nagesh (fake):
    C-Octothorpe:
    Now convince me that I need to pay to have an old, but reliable FORTRAN application rewritten because it's old.
    Using f2c to convert from fortran to c, and then simplicity to convert c to Java.
    I don't have hands-on exposure in migrating a FORTRAN codebase to anything else, so I can't really speak to this except to say, why would you do this? I can kind of see that it may be a little cheaper (auto-generated code is faster and easier to create), but all you have in the end is auto-generated code in C or Java that isn't OO at all... You still have the exact same functionality as the previous FORTRAN version, except it now runs on a slow-ass JVM [pukes].
    Nagesh (fake):
    C-Octothorpe:
    And don't forget the costs of design, development, testing and the very likely scenario that it won't perform any better and that you're potentially introducing many new bugs.
    Identically situation as before. Evan legacy aplication have bugs.
    Eh, I have to disagree with you on this. Imagine you have had a QA cycle lasting decades... I'm pretty sure that application is about as rock solid as it's ever gonna get.
    Nagesh (fake):
    Don't be a H8R.

    I undertake project in java, if you need help with homework, contact me.

    Can you please knock it off with this nonsense. You're selling yourself short by sounding like a moron.

  • Alex (unregistered)

    No comments !

    Comments = VIRUS !!!

  • Thewiseguy (unregistered)

    This forum is getting inundated with trolls. If Alex doesn't clean up, this site is going to look like a WTF.

  • Mike Starov (unregistered)

    I cannot believe anything in this article. Something like this just does not happen. Core dump file over fax? What's next? You need to create new section on your site and call it something like Fantasy Articles.

    Actually, here is an idea. Put a polling interface on each article so people can rate how believable/likely to happen it is. Have choices ranging from "Absolute Truth. I am a first hand witness" to "Absolute Bull". I don't have to guess what score this article would fetch.

  • Uncle Al (unregistered)

    I wonder how the PM would have reacted to the following classic piece of spam I received last year:

    DEAR RECEIVER,

    You have just received a Taliban virus. Since we are not so technologicaly advanced in Afghanistan, this is a MANUAL virus. Please delete all the files on your hard disk yourself and send this mail to everyone you know.

    Thank you very much for helping us.

    Thanks & Regards

    Miss Helen

  • iMalc (unregistered)

    The real WTF is indulging Vince's absurdity. Caving in only teaches the person that they were right. They'll have even more stupid ideas next time and be even more confident that they are right.

    When someone is that stupid, you either go above their head, go behind their back, or go and work elsewhere.

    However, in all liklihood with someone that idiotic, you could probably have convinced him that changing the file extension to .txt would have made it safe to transfer.

  • Ashish (unregistered)

    "The problem was an unitialized variable."

    Yeah, unitialized variables are often trouble. ;)

  • L. (unregistered) in reply to Severity One
    Severity One:
    L.:
    And for people who like to talk shit about C, please remember it is the only language that will still exist twenty years from now, because unlike Java, C#, ruby and others it meets its objectives : simple ASM translation - all others having various amount of fail and fancy stuff built-in, but none ultimately filling a purpose.
    Hang on, what of Java's objectives aren't met? You could argue about performance, maybe, but simplicity, security, platform-independence... yup, all there.
    Java will die because it's slow (anything slower than C++ is slow), heavy(private static final ultimate final again var of doom var1=0;), useless on Windows (no comment), and overall as Johnny said, the best way to create clueless programmers by protecting them from their major mistakes and misunderstandings.
    Perhaps you haven't noticed, but Windows is on the decline, and things like iOS and Android are on the incline. And what again is Android based on? Riiiight.

    Also, because you have a problem with the discipline that Java's syntax requires from you, doesn't make it a bad language.

    "Java is slow", well, no. Would I write a 3D FPS in it? Most likely not. Would productivity software be quick enough with it? Of course it would. Java is fast enough for everything except the highest computational requirements, including stuff that runs on your bluray player. Or are you saying that you have a Core i7 in your bluray player?

    The major problem with Java (which ironically you didn't mention, presumably because you don't know WTF you're talking about) is its memory usage.

    C++ will die because it's not modern enough and it's quite realistic to imagine a "better" C++.
    C++ will not die completely, for the simple reason that there are already "better" C++-s. They're called Java and C#. But it does offer object-oriented programming and exception handling whilst retaining the attractive properties of Java, at the cost of complexity and lack of memory management.
    Countless others will die . but C will remain - unless anyone has a better idea of a programming language that is as efficient as C ?
    Writing the same thing in Java takes me far less time to develop and debug than it does in C, not to mention the time that the maintenance people have to spend. Perhaps you've been living under a rock for the past 20 years, but the people that pay your salary know that a good developer is a lot more expensive than some extra CPU power, memory, and air conditioning.

    Perhaps that's not the case for you as a developer, and that wouldn't surprise me at all, given the utter cluelessness you portray.

    Who gives a **** about platform independence when Java mostly runs fine on Solaris and there's nothing as dumb as using a MS server for anything ?

    Java is slow, there is no excuse for a programming language to be slower than another.

    A better C++ would be as fast or faster than C++, while offering higher level stuff. So Java and msjava don't qualify. Especially since C# and .Net is one more useless MS technology (why would you write in C#instead of java ? oh right because you use a windows server ... lol fail calls for more fail indeed.).

    Good for you if Java makes it easier to develop, but how much of that matters when in reality it's 98% thought 2% dev ? A good developper is many times cheaper than CPU power,memory and air conditioning, simply because you write an application once, sell it 1k+ times and run it in 1k+ places.

    Besides, if you're so much quicker at java than C, you probably aren't a good point of comparison for both languages.

    It's not cluelessness it's idealism. You think it's normal that so many people around the world spend time writing the same stuff over and over with no quality increase on increasingly easy languages ? cool. I think it should be written once and optimized in one single fast language.

    Think for one second ... 99% of the code written so far has already been made redundant or is copies of copies of other copies .. . So divide the time by 100 and tell me you can't use C because it's slightly longer to write ... right.

    The only things we can really rely on is *nix OS's (not even all of them but w/e) . those are written in C. The fact that some toyOS like iOS is increasingly popular has nothing to do with a sane design decision (hacking an iOS is still a piece of cake compared to nix).

    People like you are the reason there is so much legacy in code today, you don't believe in optimization and you create, along with your peers, layers and layers of inefficiency which when stacked easily pass the 100x slower mark. (olololol there's a lot of CPU power, so let's write crap ...)

    You may have bought in the trend of the last 20 years, but you know that your managers don't understand dev more than you do and that they're probably less able than you to take those design decisions... I don't think mentioning them makes any sense in a theoretical discussion.

  • (cs) in reply to L.
    L.:
    It's not cluelessness it's idealism.
    I'm sorry, but this is IT. We don't have time for idealism.
    L.:
    You think it's normal that so many people around the world spend time writing the same stuff over and over with no quality increase on increasingly easy languages ?
    I'm pretty sure he never said that, but don't let that stop you from projecting onto him any ideas that are easier for you to refute.
    L.:
    People like you are the reason there is so much legacy in code today, you don't believe in optimization and you create, along with your peers, layers and layers of inefficiency which when stacked easily pass the 100x slower mark. (olololol there's a lot of CPU power, so let's write crap ...)
    Yep, just like that.
  • JonB (unregistered) in reply to Uncle Al
    Uncle Al:
    I wonder how the PM would have reacted to the following classic piece of spam I received last year:
    DEAR RECEIVER,

    You have just received a Taliban virus. Since we are not so technologicaly advanced in Afghanistan, this is a MANUAL virus. Please delete all the files on your hard disk yourself and send this mail to everyone you know.

    Thank you very much for helping us.

    Thanks & Regards

    Miss Helen

    There's a bug in that virus that fortunately prevents it from spreading. If I delete all the files on my hard disk my e-mail will no-longer work so I will be unable to spread it.

    Fortunate I spotted the error before I tried to run it or I wouldn't be able to warn you.

  • Jay (unregistered) in reply to Anketam
    Anketam:
    And as always: remember when a boss asks you to do something stupid or unethical always get it in writing. So when it comes out you can point to the email or chat log and take out your boss and reap some sense of retribution at their demise.

    This assumes that the boss's boss realizes that the boss is being stupid. I've generally found that in real life, if I went to the boss's boss with a case like this he'd say, "Absolutely, we have to protect the network against viruses. Are you saying that we should NOT protect against viruses?"

  • Jay (unregistered) in reply to Mason Wheeler
    Mason Wheeler:
    Paul:
    Or, two days a week you have to work and don't get paid for it. The rest of the week is yours to do as you please; earn an income and keep your pay. You're only 40% a slave.

    Hint: 40% combined tax rate between federal and state income taxes, sales tax etc.

    You mean you don't get money for it. (You really should talk to an economist sometime if you don't understand the difference.) Yes, we grumble about taxes, but we'd be in a really lousy state as a nation without the roads they build and the essential services they provide. It's not "slavery;" it's paying your share of what you use everyday.

    Hmmm ... If someone kidnapped you and forced you to work in a salt mine, would you say that as long as he provides you with a bunk in the slave quarters and some rags to wear and some gruel to eat, that he is then simply expecting you to work to pay for the food, clothing and shelter you consume, and that therefore the arrangement is completely fair and just?

    I think the key concept you are missing here is voluntary versus involuntary.

    I wouldn't call taxation "slavery" because I think there's more to the definition than involuntary contributions. But you have a curious justification for taxation: It's good and fair as long as the money is used to provide services that someone considers valuable. Who decides? What if I as the taxpayer don't consider these services valuable? What if I'd rather get them somewhere else, or have no desire to use this particular service at all? Like, I pay taxes to pay for food price supports. That is, I pay taxes whose stated purpose is to make the food I pay for more expensive. How do I benefit from that? I pay taxes to fund the Food & Drug Administration, whose stated goal is to decide what medicene I'm allowed to use. If I don't want to use a medicene, I can just not use it, so they only thing they do is prevent me from getting medicenes that may be beneficial to me. Etc. Even the services they provide that actually benefit me, like mail delivery for example, why am I forced to get it from the government rather than having a choice of where to get this service?

  • Ken Hagan (unregistered) in reply to Kuba
    Kuba:
    I think TRWTF is that C/C++ compilers can be at best expected to produce warnings about that. There should be a way to force a C/C++ compiler to simply initialize everything. It should only be disabled on the little (if any) code where benchmarks show significant and useful speed gains.

    Umm, every compiler I'm familiar with will warn and will let you treat those warnings as errors. Maybe that's just some new-fangled thing they've brought in since the 1980s.

  • Ken Hagan (unregistered) in reply to BlackBart
    BlackBart:
    Clearly this wasn't C or C++. C and C++ are not advanced enough to be configured to generate a dump file without a lot of work or adding a dump routine - which Vince would surely have disallowed as being too likely to catch a virus.

    Where I come from, dumps come from the OS and the OS neither knows nor cares what language the code was written in before it was compiled. If your dumps require effort on your part, you're doing it wrong.

  • John Muller (unregistered) in reply to Jay
    Jay:
    why am I forced to get it from the government rather than having a choice of where to get this service?

    Because the majority of people (including yourself) voted for it (or not against it at least), as opposed to a one sided use of force.

    Democracy is a terrible system, but it's the best I know of.

    Recall the origional Tea Party "No Taxation without Representation" (as opposed to the current teabaggers who conveniently forget the second half)

  • bob (unregistered)

    Vince is 100% correct and should be commended on his knowledge. It should also be pointed out that to protect the customer from viri, that all software should be faxed to the customer.

  • lokey (unregistered) in reply to My Name Is Missing
    My Name Is Missing:
    Sadly most of the PMs I've worked with are like this guy. People like this seem to have the combined IQ of all the peanuts in the world.

    Don't insult peanuts - at least they are good for Something.

  • lokey (unregistered) in reply to John Muller
    John Muller:
    Jay:
    why am I forced to get it from the government rather than having a choice of where to get this service?

    Because the majority of people (including yourself) voted for it (or not against it at least), as opposed to a one sided use of force.

    Democracy is a terrible system, but it's the best I know of.

    Recall the origional Tea Party "No Taxation without Representation" (as opposed to the current teabaggers who conveniently forget the second half)

    Not unlike the liberal democrats who always leave off the first word of that phrase - after years of doing just that, ("Taxation without Representation") I understand where all of the support for the Tea Party comes from!

  • Prachi (unregistered)

    I'm suprised that Rick survived the ordeal! I would have found a new job asap!

    I am also surprised that Vince's superior never figured out that Vince was such a moron!

    And I am even more surprised knowing that such companies survive!

  • eric bloedow (unregistered)

    this made me think of a Star Trek book called "battlestations!" where several people were stuck on a ship that had been programmed to fly on a set course and had the computer locked down. but the protagonist, Piper, ORDERED the computer to tell them how to override the lock-down! yes, this worked, after typing in the instructions it told them, they had control!

Leave a comment on “Taking a Dump”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article