Inertial Vs. Non inertial frames of reference

This video explains the difference between inertial and non-inertial reference frames and why they are called so.
Video Rating: 5 / 5

Advanced C#: Lesson 3 - Value types vs Reference types

NEW** Follow us on Twitter Advanced C#: Lesson 3 – Value types vs Reference types If you would like to see specific video…

21 thoughts on “Inertial Vs. Non inertial frames of reference

  1. Great video, little confused.. you said at 24th minute in video that
    student s has the address “2000” of the heap. The address “2000” on heap
    stores the “id” of that object, but you didn’t say anything about address
    “2004” that stores name, then how is the student s object holding a
    reference to the name ?? Please reply, thank you

  2. Man I love your videos. Only thing that caught me. And really this isn’t
    even something that is an issue but just kind of an observation. While this
    topic can be tricky, because even myself a few months ago really had to
    grasp my head around the different types and how the computer allocates
    memory stack/heap etc … Even though it can be tricky it is in my opinion
    that before getting too far into C# that Reference types and Value types is
    a day 2 fundamental in my opinion. I mean, understanding those
    relationships, while it may take a minute, is essential in understanding
    how your program operates. Do you agree as well? Keep up the good work!

  3. Great stuff: quick question: I am struggling about this for sometime: why
    the following 3 methods to assign a list to the other list generates two
    different result??

    class Program
    static void Main(string[] args)
    List listInt = new List(){1,3,5,9};
    ListInt2 = new List();
    //=== method 1:
    ListInt2 = listInt ;

    //==== method 2:
    List ListInt2 =listInt ;

    //=== method 3:
    List ListInt2 = new List(listInt );

    ListInt2[0] = 0;

    Console.WriteLine(“the 1st list of Int”);
    foreach (int i in listInt)

    Console.WriteLine(“the 2nd list of Int”);
    foreach (int i in ListInt2)


    Deeply appreciated!

  4. Jesse – Your videos are really good. I would be interested to hear more
    about when it is smart to pass value type variables “by reference.” Even
    though C# manages the memory for you, you can make your program less
    efficient if you make some bad memory decisions in your program design. I
    would be interested to hear your opinions on that topic. Keep up the good

  5. Thanks for your kind and warmhearted explanation..!! It’s very easy to
    understand what’s the difference between value and reference types. Thanks
    again and keep up great works…!!!

  6. Excellent tutorial. Please do put up an advanced lesson on value and
    reference types if you haven’t already. I’ll have a look through some of
    your other videos. Keep up the good work, Jesse!

  7. Please tell me there will be more in this series. I love how you make these
    intelligent without trying to sound too intelligent. This series is easier
    to follow than others.

  8. Also memory locations aren’t in hexadecimal. They may be represented by hex
    but that is because it is easier (and shorter) to represent large, power of
    2 numbers that way – in other words it’s for our convenience rather than
    them actually “being” hex. You can represent addresses in any base system
    that is easy for you.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.