Gentlemen, the time has come for a serious discussion on whether or not to continue using C for serious programming projects. As I will explain, I feel that C needs to be retired, much the same way that Fortran, Cobol and Perl have been. Furthermore, allow me to be so bold as to suggest a superior replacement to this outdated language.
To give you a little background on this subject, I was recently asked to develop a client/server project on a Unix platform for a Fortune 500 company. While I've never coded in C before I have coded in VB for fifteen years, and in Java for over ten, I was stunned to see how poorly C fared compared to these two, more low-level languages.
C's biggest difficulty, as we all know, is the fact that it is by far one of the slowest languages in existance, especially when compared to more modern languages such as Java. Although the reasons for this are varied, the main reasons seems to be the way C requires a programmer to laboriously work with chunks of memory.
Requiring a programmer to manipulate blocks of memory is a tedious way to program. This was satisfactory back in the early days of coding, but then again, so were punchcards. By using what are called "pointers" a C programmer is basically requiring the computer to do three sets of work rather than one. The first time requires the computer to duplicate whatever is stored in the memory space "pointed to" by the pointer. The second time requires it to perform the needed operation on this space. Finally the computer must delete the duplicate set and set the values of the original accordingly.
Clearly this is a horrendous use of resources and the chief reason why C is so slow. When one looks at a more modern (and a more serious) programming language like Java or, even better, Visual Basic, that lacks such archaic coding styles, one will also note a serious speed increase over C.
So what does this mean for the programming community? I think clearly that C needs to be abandonded. There are two candidates that would be a suitable replacement for it. Those are Java and Visual Basic.
Having programmed in both for many years, I believe that VB has the edge. Not only is it slightly faster than Java its also much easier to code in. I found C to be confusing, frightening and intimidating with its non-GUI-based coding style. Furthermore, I like to see the source code of the projects I work with. Java's source seems to be under the monopolistic thumb of Sun much the way that GCC is obscured from us by the marketing people at the FSF. Microsoft's "shared source" under which Visual Basic is released definately seems to be the most fair and reasonable of all the licenses in existance, with none of the harsh restrictions of the BSD license. It also lacks the GPLs requirement that anything coded with its tools becomes property of the FSF.
I hope to see a switch to VB very soon. I've already spoken with various luminaries in the *nix coding world and most are eager to begin to transition. Having just gotten off the phone with Mr. Alan Cox, I can say that he is quite thrilled with the speed increases that will occur when the Linux kernel is completely rewritten in Visual Basic. Richard Stallman plans to support this, and hopes that the great Swede himself, Linus Torvaldis, won't object to renaming Linux to VB/Linux. Although not a C coder himself, I'm told that Slashdot's very own Admiral Taco will support this on his web site.
This would be a perfect question to pose to Ask Slashdot. While you could look it up yourself using Google and other search engines, you shouldn't be bothered to do such laborious work yourself. By posting to Ask Slashdot, you can cause all the other Slashbots to do your work for you! Ingenious!!
See, most Slashbots fear anything that doesn't have a command line. This is why they love Linux so much, even though it is a vastly inferior OS. This also explains their refusal to recognize OSX as the BEST FUCKING OS EVER RELEASED!!
This is the last post on this thread. By posting after this you're confessing your homosexuality and that you want to felch Jon Katz. Post are your own peril!
Everyone needs to rush to judgement. Patience and rationality aren't to be found here. If they were, people would realize that Open Source is shit and Slashdot would collapse under the weight of its own self-righteousness.
Gentlemen, the time has come for a serious discussion on whether or not to continue using C for serious programming projects. As I will explain, I feel that C needs to be retired, much the same way that Fortran, Cobol and Perl have been. Furthermore, allow me to be so bold as to suggest a superior replacement to this outdated language.
To give you a little background on this subject, I was recently asked to develop a client/server project on a Unix platform for a Fortune 500 company. While I've never coded in C before I have coded in VB for fifteen years, and in Java for over ten, I was stunned to see how poorly C fared compared to these two, more low-level languages.
C's biggest difficulty, as we all know, is the fact that it is by far one of the slowest languages in existance, especially when compared to more modern languages such as Java. Although the reasons for this are varied, the main reasons seems to be the way C requires a programmer to laboriously work with chunks of memory.
Requiring a programmer to manipulate blocks of memory is a tedious way to program. This was satisfactory back in the early days of coding, but then again, so were punchcards. By using what are called "pointers" a C programmer is basically requiring the computer to do three sets of work rather than one. The first time requires the computer to duplicate whatever is stored in the memory space "pointed to" by the pointer. The second time requires it to perform the needed operation on this space. Finally the computer must delete the duplicate set and set the values of the original accordingly.
Clearly this is a horrendous use of resources and the chief reason why C is so slow. When one looks at a more modern (and a more serious) programming language like Java or, even better, Visual Basic, that lacks such archaic coding styles, one will also note a serious speed increase over C.
So what does this mean for the programming community? I think clearly that C needs to be abandonded. There are two candidates that would be a suitable replacement for it. Those are Java and Visual Basic.
Having programmed in both for many years, I believe that VB has the edge. Not only is it slightly faster than Java its also much easier to code in. I found C to be confusing, frightening and intimidating with its non-GUI-based coding style. Furthermore, I like to see the source code of the projects I work with. Java's source seems to be under the monopolistic thumb of Sun much the way that GCC is obscured from us by the marketing people at the FSF. Microsoft's "shared source" under which Visual Basic is released definately seems to be the most fair and reasonable of all the licenses in existance, with none of the harsh restrictions of the BSD license. It also lacks the GPLs requirement that anything coded with its tools becomes property of the FSF.
I hope to see a switch to VB very soon. I've already spoken with various luminaries in the *nix coding world and most are eager to begin to transition. Having just gotten off the phone with Mr. Alan Cox, I can say that he is quite thrilled with the speed increases that will occur when the Linux kernel is completely rewritten in Visual Basic. Richard Stallman plans to support this, and hopes that the great Swede himself, Linus Torvaldis, won't object to renaming Linux to VB/Linux. Although not a C coder himself, I'm told that Slashdot's very own Admiral Taco will support this on his web site.
So you bought a fan too heavy for your motherboard and now you come to Slashdot to bitch about it. Maybe next time you should do some investigating first.
Thank you, thank you. But there are many here who are far better than me. So let me give a shoutout to cyborg_monkey, spork nation, trollman 5000, trolligula, trollaxor and sunken kursk! god bless you all!
Da fuck were you using for a fan? A fucking commercial HVAC unit or somethign? I've never seen a fan that weighed more than a couple of ounces at the most. Explain yourself, before I make Jon Katz post again!
Boot into Windows. Sinec you're a Slashdot reader, you're probably already running Windows. A dirty secret: very very few Slashdot readers actually run Linux as their primary platform. Why? Because they know just how much Microsoft sucks. Its the truth that they jealously try to keep from the general public. They're much like some defense contractor that sells that Navy a boat that won't float, or something.
So anyways, view it in Windows (the superior OS!) and you'll be fine!
Slashdot Mirror
Gentlemen, the time has come for a serious discussion on whether or not to continue using C for serious programming projects. As I will explain, I feel that C needs to be retired, much the same way that Fortran, Cobol and Perl have been. Furthermore, allow me to be so bold as to suggest a superior replacement to this outdated language.
To give you a little background on this subject, I was recently asked to develop a client/server project on a Unix platform for a Fortune 500 company. While I've never coded in C before I have coded in VB for fifteen years, and in Java for over ten, I was stunned to see how poorly C fared compared to these two, more low-level languages.
C's biggest difficulty, as we all know, is the fact that it is by far one of the slowest languages in existance, especially when compared to more modern languages such as Java. Although the reasons for this are varied, the main reasons seems to be the way C requires a programmer to laboriously work with chunks of memory.
Requiring a programmer to manipulate blocks of memory is a tedious way to program. This was satisfactory back in the early days of coding, but then again, so were punchcards. By using what are called "pointers" a C programmer is basically requiring the computer to do three sets of work rather than one. The first time requires the computer to duplicate whatever is stored in the memory space "pointed to" by the pointer. The second time requires it to perform the needed operation on this space. Finally the computer must delete the duplicate set and set the values of the original accordingly.
Clearly this is a horrendous use of resources and the chief reason why C is so slow. When one looks at a more modern (and a more serious) programming language like Java or, even better, Visual Basic, that lacks such archaic coding styles, one will also note a serious speed increase over C.
So what does this mean for the programming community? I think clearly that C needs to be abandonded. There are two candidates that would be a suitable replacement for it. Those are Java and Visual Basic.
Having programmed in both for many years, I believe that VB has the edge. Not only is it slightly faster than Java its also much easier to code in. I found C to be confusing, frightening and intimidating with its non-GUI-based coding style. Furthermore, I like to see the source code of the projects I work with. Java's source seems to be under the monopolistic thumb of Sun much the way that GCC is obscured from us by the marketing people at the FSF. Microsoft's "shared source" under which Visual Basic is released definately seems to be the most fair and reasonable of all the licenses in existance, with none of the harsh restrictions of the BSD license. It also lacks the GPLs requirement that anything coded with its tools becomes property of the FSF.
I hope to see a switch to VB very soon. I've already spoken with various luminaries in the *nix coding world and most are eager to begin to transition. Having just gotten off the phone with Mr. Alan Cox, I can say that he is quite thrilled with the speed increases that will occur when the Linux kernel is completely rewritten in Visual Basic. Richard Stallman plans to support this, and hopes that the great Swede himself, Linus Torvaldis, won't object to renaming Linux to VB/Linux. Although not a C coder himself, I'm told that Slashdot's very own Admiral Taco will support this on his web site.
Thank you for your time. Happy coding.
Egg Troll
No.
This would be a perfect question to pose to Ask Slashdot. While you could look it up yourself using Google and other search engines, you shouldn't be bothered to do such laborious work yourself. By posting to Ask Slashdot, you can cause all the other Slashbots to do your work for you! Ingenious!!
See, most Slashbots fear anything that doesn't have a command line. This is why they love Linux so much, even though it is a vastly inferior OS. This also explains their refusal to recognize OSX as the BEST FUCKING OS EVER RELEASED!!
Iomega, cornerning the market on even more useless shit.
Hit her in the shitter, Dick!!
This is the last post on this thread. By posting after this you're confessing your homosexuality and that you want to felch Jon Katz. Post are your own peril!
Hahaha! I'll always laugh at a Klein Bottle joke, like the time someone once said that Jon Katz could molest a Klein Bottle.
Sounds like an easy way for NAMBLA to find its victims.
Oh now *that* is some seriously beautiful work there. I swear if I had two dead mice right now, I'd give you one.
Everyone needs to rush to judgement. Patience and rationality aren't to be found here. If they were, people would realize that Open Source is shit and Slashdot would collapse under the weight of its own self-righteousness.
Gentlemen, the time has come for a serious discussion on whether or not to continue using C for serious programming projects. As I will explain, I feel that C needs to be retired, much the same way that Fortran, Cobol and Perl have been. Furthermore, allow me to be so bold as to suggest a superior replacement to this outdated language.
To give you a little background on this subject, I was recently asked to develop a client/server project on a Unix platform for a Fortune 500 company. While I've never coded in C before I have coded in VB for fifteen years, and in Java for over ten, I was stunned to see how poorly C fared compared to these two, more low-level languages.
C's biggest difficulty, as we all know, is the fact that it is by far one of the slowest languages in existance, especially when compared to more modern languages such as Java. Although the reasons for this are varied, the main reasons seems to be the way C requires a programmer to laboriously work with chunks of memory.
Requiring a programmer to manipulate blocks of memory is a tedious way to program. This was satisfactory back in the early days of coding, but then again, so were punchcards. By using what are called "pointers" a C programmer is basically requiring the computer to do three sets of work rather than one. The first time requires the computer to duplicate whatever is stored in the memory space "pointed to" by the pointer. The second time requires it to perform the needed operation on this space. Finally the computer must delete the duplicate set and set the values of the original accordingly.
Clearly this is a horrendous use of resources and the chief reason why C is so slow. When one looks at a more modern (and a more serious) programming language like Java or, even better, Visual Basic, that lacks such archaic coding styles, one will also note a serious speed increase over C.
So what does this mean for the programming community? I think clearly that C needs to be abandonded. There are two candidates that would be a suitable replacement for it. Those are Java and Visual Basic.
Having programmed in both for many years, I believe that VB has the edge. Not only is it slightly faster than Java its also much easier to code in. I found C to be confusing, frightening and intimidating with its non-GUI-based coding style. Furthermore, I like to see the source code of the projects I work with. Java's source seems to be under the monopolistic thumb of Sun much the way that GCC is obscured from us by the marketing people at the FSF. Microsoft's "shared source" under which Visual Basic is released definately seems to be the most fair and reasonable of all the licenses in existance, with none of the harsh restrictions of the BSD license. It also lacks the GPLs requirement that anything coded with its tools becomes property of the FSF.
I hope to see a switch to VB very soon. I've already spoken with various luminaries in the *nix coding world and most are eager to begin to transition. Having just gotten off the phone with Mr. Alan Cox, I can say that he is quite thrilled with the speed increases that will occur when the Linux kernel is completely rewritten in Visual Basic. Richard Stallman plans to support this, and hopes that the great Swede himself, Linus Torvaldis, won't object to renaming Linux to VB/Linux. Although not a C coder himself, I'm told that Slashdot's very own Admiral Taco will support this on his web site.
Thank you for your time. Happy coding.
Egg Troll
I am in bed. With your mom. She's playing my rusty trombone as we speak! Having your mom rim me while she jerks me off is great! Good woman, your mom.
Its the highest praise on Slashdotter can heap upon another. Its like the Congressional Medal of Honor for /.
Please, please for the love of God buy some new glasses. Those things are hideous!! No one will take you serious while you wear such eyesores!
TSSIA.
So you bought a fan too heavy for your motherboard and now you come to Slashdot to bitch about it. Maybe next time you should do some investigating first.
Thank you, thank you. But there are many here who are far better than me. So let me give a shoutout to cyborg_monkey, spork nation, trollman 5000, trolligula, trollaxor and sunken kursk! god bless you all!
Yes I will! I'll be your boyfriend *or* your girlfriend, but you have to buy the lingere and pay for my hormones if you want me to be your g/f.
Da fuck were you using for a fan? A fucking commercial HVAC unit or somethign? I've never seen a fan that weighed more than a couple of ounces at the most. Explain yourself, before I make Jon Katz post again!
You go, girlfriend!!
YHBT. YHL. HAND.
Lameness filter encountered. Post aborted!
Reason: Don't use so many caps. It's like YELLING.
What user would be gay enough to use
the nick DankNinja?
Boot into Windows. Sinec you're a Slashdot reader, you're probably already running Windows. A dirty secret: very very few Slashdot readers actually run Linux as their primary platform. Why? Because they know just how much Microsoft sucks. Its the truth that they jealously try to keep from the general public. They're much like some defense contractor that sells that Navy a boat that won't float, or something.
So anyways, view it in Windows (the superior OS!) and you'll be fine!
Isn't that the full name of the Fonz? Arthur Mozzarelli or something like that?