Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Garbage Collection

Garbage Collection

Scheduled Pinned Locked Moved The Lounge
questioncsharpannouncement
13 Posts 9 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • H homegrown

    No, it's not a programming question, but wasn't sure to either tag this as a joke or a rant :) I interviewed a programmer the other day... ME: "so what do you understand about garbage collection in .net?" CANDIDATE: (silence) "mmm.. yes. i read about that. it's something the compiler does to release objects" ME: :confused: "compiler?" CANDIDATE: "uhuh. for when you aren't referencing objects anymore" now my compiler apparently releases objects if they're not referenced anymore. pretty neat, eh? (sic) but i still don't understand. is the technical jargon we've created in the programming domain that mixed up (difficult) that we don't/can't say what we really mean...? or is the difference between a compiler/linker/interpreter/runtime just semantics these days anyway. i mean, who cares, right? we all know what he really means ;P

    <>< :: have the courage to use your own reason

    D Offline
    D Offline
    Daniel Grunwald
    wrote on last edited by
    #2

    homegrown wrote:

    or is the difference between a compiler/linker/interpreter/runtime just semantics these days anyway

    It's a bit mixed up in .NET due to the just-in-time compiler. But programmers who don't understand the difference between compile-time, load-time (JIT-time) and run-time? X|

    1 Reply Last reply
    0
    • H homegrown

      No, it's not a programming question, but wasn't sure to either tag this as a joke or a rant :) I interviewed a programmer the other day... ME: "so what do you understand about garbage collection in .net?" CANDIDATE: (silence) "mmm.. yes. i read about that. it's something the compiler does to release objects" ME: :confused: "compiler?" CANDIDATE: "uhuh. for when you aren't referencing objects anymore" now my compiler apparently releases objects if they're not referenced anymore. pretty neat, eh? (sic) but i still don't understand. is the technical jargon we've created in the programming domain that mixed up (difficult) that we don't/can't say what we really mean...? or is the difference between a compiler/linker/interpreter/runtime just semantics these days anyway. i mean, who cares, right? we all know what he really means ;P

      <>< :: have the courage to use your own reason

      L Offline
      L Offline
      leppie
      wrote on last edited by
      #3

      homegrown wrote:

      we all know what he really means

      Well technically, a compiler could aid with that ;P

      xacc.ide - now with TabsToSpaces support
      IronScheme - 1.0 alpha 4a out now (29 May 2008)

      1 Reply Last reply
      0
      • H homegrown

        No, it's not a programming question, but wasn't sure to either tag this as a joke or a rant :) I interviewed a programmer the other day... ME: "so what do you understand about garbage collection in .net?" CANDIDATE: (silence) "mmm.. yes. i read about that. it's something the compiler does to release objects" ME: :confused: "compiler?" CANDIDATE: "uhuh. for when you aren't referencing objects anymore" now my compiler apparently releases objects if they're not referenced anymore. pretty neat, eh? (sic) but i still don't understand. is the technical jargon we've created in the programming domain that mixed up (difficult) that we don't/can't say what we really mean...? or is the difference between a compiler/linker/interpreter/runtime just semantics these days anyway. i mean, who cares, right? we all know what he really means ;P

        <>< :: have the courage to use your own reason

        L Offline
        L Offline
        Lost User
        wrote on last edited by
        #4

        Too many engineers these days know nothing but what was new in the last 5 years. Even Microsoft. I was working on joint project with them and the guty didnt kow the term 'run time' in terms of a distributed SDK.

        Morality is indistinguishable from social proscription

        1 Reply Last reply
        0
        • H homegrown

          No, it's not a programming question, but wasn't sure to either tag this as a joke or a rant :) I interviewed a programmer the other day... ME: "so what do you understand about garbage collection in .net?" CANDIDATE: (silence) "mmm.. yes. i read about that. it's something the compiler does to release objects" ME: :confused: "compiler?" CANDIDATE: "uhuh. for when you aren't referencing objects anymore" now my compiler apparently releases objects if they're not referenced anymore. pretty neat, eh? (sic) but i still don't understand. is the technical jargon we've created in the programming domain that mixed up (difficult) that we don't/can't say what we really mean...? or is the difference between a compiler/linker/interpreter/runtime just semantics these days anyway. i mean, who cares, right? we all know what he really means ;P

          <>< :: have the courage to use your own reason

          C Offline
          C Offline
          Chris Maunder
          wrote on last edited by
          #5

          homegrown wrote:

          is the difference between a compiler/linker/interpreter/runtime just semantics these days anyway

          Absolutely not. I'd also be asking him to explain how many compilers are actually involved in creating and executing a program. Just to drive the nail home. This stuff is Comp Sci 101. There's no excuse for not knowing it

          cheers, Chris Maunder

          CodeProject.com : C++ MVP

          H P 2 Replies Last reply
          0
          • H homegrown

            No, it's not a programming question, but wasn't sure to either tag this as a joke or a rant :) I interviewed a programmer the other day... ME: "so what do you understand about garbage collection in .net?" CANDIDATE: (silence) "mmm.. yes. i read about that. it's something the compiler does to release objects" ME: :confused: "compiler?" CANDIDATE: "uhuh. for when you aren't referencing objects anymore" now my compiler apparently releases objects if they're not referenced anymore. pretty neat, eh? (sic) but i still don't understand. is the technical jargon we've created in the programming domain that mixed up (difficult) that we don't/can't say what we really mean...? or is the difference between a compiler/linker/interpreter/runtime just semantics these days anyway. i mean, who cares, right? we all know what he really means ;P

            <>< :: have the courage to use your own reason

            P Offline
            P Offline
            Pete OHanlon
            wrote on last edited by
            #6

            Sounds like interview nerves. It's the old "I misspoke" defense.

            Deja View - the feeling that you've seen this post before.

            My blog | My articles

            1 Reply Last reply
            0
            • C Chris Maunder

              homegrown wrote:

              is the difference between a compiler/linker/interpreter/runtime just semantics these days anyway

              Absolutely not. I'd also be asking him to explain how many compilers are actually involved in creating and executing a program. Just to drive the nail home. This stuff is Comp Sci 101. There's no excuse for not knowing it

              cheers, Chris Maunder

              CodeProject.com : C++ MVP

              H Offline
              H Offline
              homegrown
              wrote on last edited by
              #7

              Chris Maunder wrote:

              how many compilers are actually involved in creating and executing a program

              :laugh: mental note: i must remember to use that next time

              <>< :: have the courage to use your own reason

              1 Reply Last reply
              0
              • C Chris Maunder

                homegrown wrote:

                is the difference between a compiler/linker/interpreter/runtime just semantics these days anyway

                Absolutely not. I'd also be asking him to explain how many compilers are actually involved in creating and executing a program. Just to drive the nail home. This stuff is Comp Sci 101. There's no excuse for not knowing it

                cheers, Chris Maunder

                CodeProject.com : C++ MVP

                P Offline
                P Offline
                Pete OHanlon
                wrote on last edited by
                #8

                Chris Maunder wrote:

                I'd also be asking him to explain how many compilers are actually involved in creating and executing a program

                Depends if it's PE or not. Then the question is "How many compilers are involved in creating and executing the compiler, and how fast?"

                Deja View - the feeling that you've seen this post before.

                My blog | My articles

                1 Reply Last reply
                0
                • H homegrown

                  No, it's not a programming question, but wasn't sure to either tag this as a joke or a rant :) I interviewed a programmer the other day... ME: "so what do you understand about garbage collection in .net?" CANDIDATE: (silence) "mmm.. yes. i read about that. it's something the compiler does to release objects" ME: :confused: "compiler?" CANDIDATE: "uhuh. for when you aren't referencing objects anymore" now my compiler apparently releases objects if they're not referenced anymore. pretty neat, eh? (sic) but i still don't understand. is the technical jargon we've created in the programming domain that mixed up (difficult) that we don't/can't say what we really mean...? or is the difference between a compiler/linker/interpreter/runtime just semantics these days anyway. i mean, who cares, right? we all know what he really means ;P

                  <>< :: have the courage to use your own reason

                  H Offline
                  H Offline
                  Hamed Musavi
                  wrote on last edited by
                  #9

                  Back in college days and in first semester, a teachers asked students a question. I thought I knew the answer, since I had readings before going to college. I remembered I answered but made a mistake like this guy. After my answer the teacher said: "your problem with computer is that you've learned it in an slangy manner that makes your information useless; in computer science you cannot go on like this". The first lesson stayed in my mind and at least I tried to change myself. At the end of the semester, I got the best mark of that class. Maybe such a teacher was the missing gem in that candidates life. My 2 cents.

                  // "In the end it's a little boy expressing himself." Yanni while (I_am_alive)
                  {
                      cout<<"I love to do more than just programming.";
                  }

                  H 1 Reply Last reply
                  0
                  • H homegrown

                    No, it's not a programming question, but wasn't sure to either tag this as a joke or a rant :) I interviewed a programmer the other day... ME: "so what do you understand about garbage collection in .net?" CANDIDATE: (silence) "mmm.. yes. i read about that. it's something the compiler does to release objects" ME: :confused: "compiler?" CANDIDATE: "uhuh. for when you aren't referencing objects anymore" now my compiler apparently releases objects if they're not referenced anymore. pretty neat, eh? (sic) but i still don't understand. is the technical jargon we've created in the programming domain that mixed up (difficult) that we don't/can't say what we really mean...? or is the difference between a compiler/linker/interpreter/runtime just semantics these days anyway. i mean, who cares, right? we all know what he really means ;P

                    <>< :: have the courage to use your own reason

                    S Offline
                    S Offline
                    Single Step Debugger
                    wrote on last edited by
                    #10

                    The candidate answer is absolutely correct! The compiler “collects” your garbage code and assembled it in a crappy application. That’s why they call them “garbage collector”. I hope you hired the guy? It’s really strange that experience programmers like you guys don’t know such basic thinks. The next time I will talk about “smart pointers”. In a nutshell this is a mechanism which point your crappy program to some crappy libraries created from some other low qualified morons and this is the Linker job.

                    The narrow specialist in the broad sense of the word is a complete idiot in the narrow sense of the word.

                    J 1 Reply Last reply
                    0
                    • H Hamed Musavi

                      Back in college days and in first semester, a teachers asked students a question. I thought I knew the answer, since I had readings before going to college. I remembered I answered but made a mistake like this guy. After my answer the teacher said: "your problem with computer is that you've learned it in an slangy manner that makes your information useless; in computer science you cannot go on like this". The first lesson stayed in my mind and at least I tried to change myself. At the end of the semester, I got the best mark of that class. Maybe such a teacher was the missing gem in that candidates life. My 2 cents.

                      // "In the end it's a little boy expressing himself." Yanni while (I_am_alive)
                      {
                          cout<<"I love to do more than just programming.";
                      }

                      H Offline
                      H Offline
                      homegrown
                      wrote on last edited by
                      #11

                      Hamed Mosavi wrote:

                      your problem with computer is that you've learned it in an slangy manner

                      that's a pretty accurate assessment, methinks, and valuable insight. there does seem to be a lot of that, probably 'cos of the information overload (perceived or real?) that makes us summarise too quickly, and it will probably show up in code somewhere too- eventually. but i agree with you on one thing...

                      Hamed Mosavi wrote:

                      in computer science you cannot go on like this

                      also a great reminder to myself not to forget that either! ;)

                      <>< :: have the courage to use your own reason

                      1 Reply Last reply
                      0
                      • S Single Step Debugger

                        The candidate answer is absolutely correct! The compiler “collects” your garbage code and assembled it in a crappy application. That’s why they call them “garbage collector”. I hope you hired the guy? It’s really strange that experience programmers like you guys don’t know such basic thinks. The next time I will talk about “smart pointers”. In a nutshell this is a mechanism which point your crappy program to some crappy libraries created from some other low qualified morons and this is the Linker job.

                        The narrow specialist in the broad sense of the word is a complete idiot in the narrow sense of the word.

                        J Offline
                        J Offline
                        Jim Crafton
                        wrote on last edited by
                        #12

                        Hey, maybe you write article for all programmers like us that not understand these "smarty points"? Be would very helpfuly, plzzz?!

                        ¡El diablo está en mis pantalones! ¡Mire, mire! Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! VCF Blog

                        S 1 Reply Last reply
                        0
                        • J Jim Crafton

                          Hey, maybe you write article for all programmers like us that not understand these "smarty points"? Be would very helpfuly, plzzz?!

                          ¡El diablo está en mis pantalones! ¡Mire, mire! Real Mentats use only 100% pure, unfooled around with Sapho Juice(tm)! SELECT * FROM User WHERE Clue > 0 0 rows returned Save an Orange - Use the VCF! VCF Blog

                          S Offline
                          S Offline
                          Single Step Debugger
                          wrote on last edited by
                          #13

                          Article?!? I already published a whole book – “Very Smart Pointers and Smatter Logic” first edition. Unfortunately they publish it only in two copies – one for me and one for my psychiatrist. :sigh: But I could give you my copy.

                          The narrow specialist in the broad sense of the word is a complete idiot in the narrow sense of the word.

                          1 Reply Last reply
                          0
                          Reply
                          • Reply as topic
                          Log in to reply
                          • Oldest to Newest
                          • Newest to Oldest
                          • Most Votes


                          • Login

                          • Don't have an account? Register

                          • Login or register to search.
                          • First post
                            Last post
                          0
                          • Categories
                          • Recent
                          • Tags
                          • Popular
                          • World
                          • Users
                          • Groups