Why do we use back and forward instead of backward and forward?












5














In some English language user interfaces, both virtual and physical, the words back and forward are used instead of backward and forward.



An easy example is the web browser, where the buttons to navigate the history of a tab are labelled back and forward. Why is it back and not backward?



In French, the words are "précédent" and "suivant", which means "previous" and "next" and are opposites contrary to back and forward.










share|improve this question















migrated from ux.stackexchange.com Sep 18 '14 at 0:25


This question came from our site for user experience researchers and experts.











  • 4




    Or why not "back" and "forth"? :)
    – guifa
    Sep 18 '14 at 2:31






  • 3




    This question appears to be off-topic because it is (only) about the choice of terms for user interfaces in software products (see the OP comment to this answer).
    – Drew
    Sep 19 '14 at 14:29






  • 2




    Strange that this was migrated here from UX, when I would have proposed a migration in the opposite direction, as it is about user interface conventions.
    – choster
    Sep 19 '14 at 15:10










  • @choster. (FWIW, I agree.) Perhaps because (a) folks over there are not that aware of what EL&U is about, or (b) folks there did not pay attention to this being about UI conventions, or (c) UI conventions are off-topic over there (?), or they don't care much about the history or past rationale for now-established UI conventions. Just guesses.
    – Drew
    Sep 21 '14 at 15:59






  • 3




    For what it's worth, since this question is here, I reckon it should be answered in regards to the difference (if there is any) between back in "Go back" and backward/backwards in "Go backward". That is a matter of English, although it's also relevant to UX.
    – Andrew Leach
    Sep 22 '14 at 21:48
















5














In some English language user interfaces, both virtual and physical, the words back and forward are used instead of backward and forward.



An easy example is the web browser, where the buttons to navigate the history of a tab are labelled back and forward. Why is it back and not backward?



In French, the words are "précédent" and "suivant", which means "previous" and "next" and are opposites contrary to back and forward.










share|improve this question















migrated from ux.stackexchange.com Sep 18 '14 at 0:25


This question came from our site for user experience researchers and experts.











  • 4




    Or why not "back" and "forth"? :)
    – guifa
    Sep 18 '14 at 2:31






  • 3




    This question appears to be off-topic because it is (only) about the choice of terms for user interfaces in software products (see the OP comment to this answer).
    – Drew
    Sep 19 '14 at 14:29






  • 2




    Strange that this was migrated here from UX, when I would have proposed a migration in the opposite direction, as it is about user interface conventions.
    – choster
    Sep 19 '14 at 15:10










  • @choster. (FWIW, I agree.) Perhaps because (a) folks over there are not that aware of what EL&U is about, or (b) folks there did not pay attention to this being about UI conventions, or (c) UI conventions are off-topic over there (?), or they don't care much about the history or past rationale for now-established UI conventions. Just guesses.
    – Drew
    Sep 21 '14 at 15:59






  • 3




    For what it's worth, since this question is here, I reckon it should be answered in regards to the difference (if there is any) between back in "Go back" and backward/backwards in "Go backward". That is a matter of English, although it's also relevant to UX.
    – Andrew Leach
    Sep 22 '14 at 21:48














5












5








5


1





In some English language user interfaces, both virtual and physical, the words back and forward are used instead of backward and forward.



An easy example is the web browser, where the buttons to navigate the history of a tab are labelled back and forward. Why is it back and not backward?



In French, the words are "précédent" and "suivant", which means "previous" and "next" and are opposites contrary to back and forward.










share|improve this question















In some English language user interfaces, both virtual and physical, the words back and forward are used instead of backward and forward.



An easy example is the web browser, where the buttons to navigate the history of a tab are labelled back and forward. Why is it back and not backward?



In French, the words are "précédent" and "suivant", which means "previous" and "next" and are opposites contrary to back and forward.







terminology direction






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Sep 20 '14 at 0:25









Ellie Kesselman

4,65832147




4,65832147










asked Sep 17 '14 at 17:08









qwertzguy

12815




12815




migrated from ux.stackexchange.com Sep 18 '14 at 0:25


This question came from our site for user experience researchers and experts.






migrated from ux.stackexchange.com Sep 18 '14 at 0:25


This question came from our site for user experience researchers and experts.










  • 4




    Or why not "back" and "forth"? :)
    – guifa
    Sep 18 '14 at 2:31






  • 3




    This question appears to be off-topic because it is (only) about the choice of terms for user interfaces in software products (see the OP comment to this answer).
    – Drew
    Sep 19 '14 at 14:29






  • 2




    Strange that this was migrated here from UX, when I would have proposed a migration in the opposite direction, as it is about user interface conventions.
    – choster
    Sep 19 '14 at 15:10










  • @choster. (FWIW, I agree.) Perhaps because (a) folks over there are not that aware of what EL&U is about, or (b) folks there did not pay attention to this being about UI conventions, or (c) UI conventions are off-topic over there (?), or they don't care much about the history or past rationale for now-established UI conventions. Just guesses.
    – Drew
    Sep 21 '14 at 15:59






  • 3




    For what it's worth, since this question is here, I reckon it should be answered in regards to the difference (if there is any) between back in "Go back" and backward/backwards in "Go backward". That is a matter of English, although it's also relevant to UX.
    – Andrew Leach
    Sep 22 '14 at 21:48














  • 4




    Or why not "back" and "forth"? :)
    – guifa
    Sep 18 '14 at 2:31






  • 3




    This question appears to be off-topic because it is (only) about the choice of terms for user interfaces in software products (see the OP comment to this answer).
    – Drew
    Sep 19 '14 at 14:29






  • 2




    Strange that this was migrated here from UX, when I would have proposed a migration in the opposite direction, as it is about user interface conventions.
    – choster
    Sep 19 '14 at 15:10










  • @choster. (FWIW, I agree.) Perhaps because (a) folks over there are not that aware of what EL&U is about, or (b) folks there did not pay attention to this being about UI conventions, or (c) UI conventions are off-topic over there (?), or they don't care much about the history or past rationale for now-established UI conventions. Just guesses.
    – Drew
    Sep 21 '14 at 15:59






  • 3




    For what it's worth, since this question is here, I reckon it should be answered in regards to the difference (if there is any) between back in "Go back" and backward/backwards in "Go backward". That is a matter of English, although it's also relevant to UX.
    – Andrew Leach
    Sep 22 '14 at 21:48








4




4




Or why not "back" and "forth"? :)
– guifa
Sep 18 '14 at 2:31




Or why not "back" and "forth"? :)
– guifa
Sep 18 '14 at 2:31




3




3




This question appears to be off-topic because it is (only) about the choice of terms for user interfaces in software products (see the OP comment to this answer).
– Drew
Sep 19 '14 at 14:29




This question appears to be off-topic because it is (only) about the choice of terms for user interfaces in software products (see the OP comment to this answer).
– Drew
Sep 19 '14 at 14:29




2




2




Strange that this was migrated here from UX, when I would have proposed a migration in the opposite direction, as it is about user interface conventions.
– choster
Sep 19 '14 at 15:10




Strange that this was migrated here from UX, when I would have proposed a migration in the opposite direction, as it is about user interface conventions.
– choster
Sep 19 '14 at 15:10












@choster. (FWIW, I agree.) Perhaps because (a) folks over there are not that aware of what EL&U is about, or (b) folks there did not pay attention to this being about UI conventions, or (c) UI conventions are off-topic over there (?), or they don't care much about the history or past rationale for now-established UI conventions. Just guesses.
– Drew
Sep 21 '14 at 15:59




@choster. (FWIW, I agree.) Perhaps because (a) folks over there are not that aware of what EL&U is about, or (b) folks there did not pay attention to this being about UI conventions, or (c) UI conventions are off-topic over there (?), or they don't care much about the history or past rationale for now-established UI conventions. Just guesses.
– Drew
Sep 21 '14 at 15:59




3




3




For what it's worth, since this question is here, I reckon it should be answered in regards to the difference (if there is any) between back in "Go back" and backward/backwards in "Go backward". That is a matter of English, although it's also relevant to UX.
– Andrew Leach
Sep 22 '14 at 21:48




For what it's worth, since this question is here, I reckon it should be answered in regards to the difference (if there is any) between back in "Go back" and backward/backwards in "Go backward". That is a matter of English, although it's also relevant to UX.
– Andrew Leach
Sep 22 '14 at 21:48










6 Answers
6






active

oldest

votes


















4














I'll take a kick at this can, but it is pure speculation. Maybe someone can come up with a documented answer.



Firstly, we should understand that "back" and "backward" are both adverbs. Both have a meaning which is "away from the front; toward the back". In this definition, they are synonymous.



The implied verb in "back" and "forward" is go, as in "go back" or "go forward." The statement "go backward" is grammatically correct but idiomatically it's not how we would say it in English -- at least, the forms of English I'm familiar with. Native English speakers are more likely to say "go back." Look at this comparative chart of how often "go back" and "go backward" are used.



That being said, in English user interfaces we will also use "previous" and "next". This is used more for a sequence of pages, such as Google results pages.



As for French, "précédent" and "suivant" don't have a monopoly, either. I often see buttons like "< Retour" to mean "< Back". And in my Chrome interface right now, if I hover over the back and forward buttons, I get "Réculer d'une page" and "Avancer d'une page". Internet Explorer gives me a mix: "Retour" and "suivant".



At the end of the day, what matters from a UX perspective is:




  • Your label is clear. "Backward" meets this criterion. A user would expect to go backward.

  • Your label is natural. "Backward" could cause a momentary hesitation, just because the wording is not an established convention.


Hope that helps! Bonne chance !






share|improve this answer



















  • 3




    Plus, for me, Go back and Go backward(s) are a bit different. Go back is return from some starting point, go backward(s) implies moving — without a stopping point per se — in reverse. Oddly, neither go forward and go forth seem to have the same implication as go back does. Crazy English language.
    – guifa
    Sep 18 '14 at 2:19










  • Interestingly "go forth" used to be more mainstream but "go forward" took the lead around 1915: books.google.com/ngrams/…
    – qwertzguy
    Jan 29 '15 at 4:00










  • And small nit: your link to google ngrams is unfortunately broken, the quotes needs to be removed in the query.
    – qwertzguy
    Jan 29 '15 at 4:05



















2














We don't say back and forward. We say back and forth. ;-)



Forward and backward are directions. Back, as in a back button, refers to going back to a previous state/position. Yes, that often involves also moving backward, i.e., traversing a sequence backward.



But when you say "Go back" you are emphasizing the destination, a previous state or position. The direction and how you might get there are not important (not emphasized).



If I ask whether you are going back to France, I'm not necessarily asking how you will get there. And I probably do not care whether you are retracing your steps backward, from how you got here from France. ;-)



Driving backward means driving in reverse gear. Driving back home means returning home, whatever the route taken.






share|improve this answer





















  • When speaking between us yes and my question is precisely why is it different in user interfaces of computers or even devices? Like a DVD player would have buttons labelled: back and forward. Why?
    – qwertzguy
    Sep 19 '14 at 9:50






  • 1




    If your question is limited to why it is different in UIs then I believe that it is off-topic. But I'm no expert on that.
    – Drew
    Sep 19 '14 at 14:27










  • I originally posted this question in UXstack exchange -_-
    – qwertzguy
    Sep 21 '14 at 15:39






  • 1




    UX is where it belongs, IMO. The choice of terms to use for the UI was apparently not based on any English rules, but was likely based on some UI considerations (perhaps simply saving space!).
    – Drew
    Sep 21 '14 at 16:06



















0














The other answers thoroughly explained the English usage for "go back" and "back" and "backward".



Given the context of the question and the specific inquiry, "Why do we use..." it is most likely due to user interface design considerations. "Back" has fewer letters than "backward". Brevity is preferable.






share|improve this answer





















  • But then why forward?
    – qwertzguy
    Sep 21 '14 at 14:55






  • 1




    See my guesses in a comment to your question. The folks on SE might not even realize that UI considerations entered into the choice of terms for this, for the UI. They might have guessed that this is about English conventions, grammar rules, or some such.
    – Drew
    Sep 21 '14 at 16:05










  • @Drew "Given the context of the question and the specific inquiry, "Why do we use..." it is most likely due to user interface design considerations."
    – Ellie Kesselman
    Oct 4 '14 at 14:45






  • 1




    @EllieKesselman: That's my guess too. My guess is specifically: to save space (screen real estate). Back is clear enough. Some browsers just reduce the space to what is needed for a left arrow (right arrow for forward). Abbreviations are common in UI, especially when clear enough.
    – Drew
    Oct 4 '14 at 15:48






  • 1




    @EllieKesselman: FWIW, took a look at your website - "Not enough Thorsten Veblen!" Indeed. Keep up the good work.
    – Drew
    Oct 6 '14 at 21:14



















0














Usually, when you go 'back' there is a destination in mind. As @Drew says - your precise route backwards is not usually the point. On the other hand, often, when you go ahead the destination is unclear and the route forwards is all you actually know. Strategists engage in forwards thinking without necessarily having a goal in mind. When you do know the position ahead that you are heading to, you go to the fore.






share|improve this answer





















  • But in the case of a web browser for example, we do know the destination, the goal when clicking the 'forward' button and it's precise, since if isn't then the button is disabled. (my question is about usage of the words in user interfaces, not in literature).
    – qwertzguy
    Jan 29 '15 at 3:51



















0














I propose it is analogous to pages in a book. Also, similar usage happens when playing a board game: roll the dice and move forward X spaces; draw a card and go back one space. Both are examples of a linear progression of positions.






share|improve this answer





























    0














    I'll take a stab at this.



    The reasoning behind the usage of "Back" and "Forward" is to elicit the simplest response that will let the end user know exactly what the function of the button they're pressing does.



    The statement "Back" immediately upon hearing it brings to mind movement that one has already visited, and signifies a desire to "Return". (bonus points if you realize why the Enter key used to be referred to as the "Return" key.)



    Similarly, "Forward" implies to the end user that you have already visited a location which you have a desire to return to.



    There's little doubt that they were most likely chosen due to their monosyllabic conveyance. They are the words that are able to convey the largest amounts of meaning using the smallest amount of bits. In a time when internet browsers were new and hard drives were much, much smaller in size, "-wards" would have been considered an unnecessary allocation of bits, especially in a time when the commands for the equivalent "back" in MSDOS directory navigation was ".."






    share|improve this answer





















      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "97"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      noCode: true, onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fenglish.stackexchange.com%2fquestions%2f197012%2fwhy-do-we-use-back-and-forward-instead-of-backward-and-forward%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      6 Answers
      6






      active

      oldest

      votes








      6 Answers
      6






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      4














      I'll take a kick at this can, but it is pure speculation. Maybe someone can come up with a documented answer.



      Firstly, we should understand that "back" and "backward" are both adverbs. Both have a meaning which is "away from the front; toward the back". In this definition, they are synonymous.



      The implied verb in "back" and "forward" is go, as in "go back" or "go forward." The statement "go backward" is grammatically correct but idiomatically it's not how we would say it in English -- at least, the forms of English I'm familiar with. Native English speakers are more likely to say "go back." Look at this comparative chart of how often "go back" and "go backward" are used.



      That being said, in English user interfaces we will also use "previous" and "next". This is used more for a sequence of pages, such as Google results pages.



      As for French, "précédent" and "suivant" don't have a monopoly, either. I often see buttons like "< Retour" to mean "< Back". And in my Chrome interface right now, if I hover over the back and forward buttons, I get "Réculer d'une page" and "Avancer d'une page". Internet Explorer gives me a mix: "Retour" and "suivant".



      At the end of the day, what matters from a UX perspective is:




      • Your label is clear. "Backward" meets this criterion. A user would expect to go backward.

      • Your label is natural. "Backward" could cause a momentary hesitation, just because the wording is not an established convention.


      Hope that helps! Bonne chance !






      share|improve this answer



















      • 3




        Plus, for me, Go back and Go backward(s) are a bit different. Go back is return from some starting point, go backward(s) implies moving — without a stopping point per se — in reverse. Oddly, neither go forward and go forth seem to have the same implication as go back does. Crazy English language.
        – guifa
        Sep 18 '14 at 2:19










      • Interestingly "go forth" used to be more mainstream but "go forward" took the lead around 1915: books.google.com/ngrams/…
        – qwertzguy
        Jan 29 '15 at 4:00










      • And small nit: your link to google ngrams is unfortunately broken, the quotes needs to be removed in the query.
        – qwertzguy
        Jan 29 '15 at 4:05
















      4














      I'll take a kick at this can, but it is pure speculation. Maybe someone can come up with a documented answer.



      Firstly, we should understand that "back" and "backward" are both adverbs. Both have a meaning which is "away from the front; toward the back". In this definition, they are synonymous.



      The implied verb in "back" and "forward" is go, as in "go back" or "go forward." The statement "go backward" is grammatically correct but idiomatically it's not how we would say it in English -- at least, the forms of English I'm familiar with. Native English speakers are more likely to say "go back." Look at this comparative chart of how often "go back" and "go backward" are used.



      That being said, in English user interfaces we will also use "previous" and "next". This is used more for a sequence of pages, such as Google results pages.



      As for French, "précédent" and "suivant" don't have a monopoly, either. I often see buttons like "< Retour" to mean "< Back". And in my Chrome interface right now, if I hover over the back and forward buttons, I get "Réculer d'une page" and "Avancer d'une page". Internet Explorer gives me a mix: "Retour" and "suivant".



      At the end of the day, what matters from a UX perspective is:




      • Your label is clear. "Backward" meets this criterion. A user would expect to go backward.

      • Your label is natural. "Backward" could cause a momentary hesitation, just because the wording is not an established convention.


      Hope that helps! Bonne chance !






      share|improve this answer



















      • 3




        Plus, for me, Go back and Go backward(s) are a bit different. Go back is return from some starting point, go backward(s) implies moving — without a stopping point per se — in reverse. Oddly, neither go forward and go forth seem to have the same implication as go back does. Crazy English language.
        – guifa
        Sep 18 '14 at 2:19










      • Interestingly "go forth" used to be more mainstream but "go forward" took the lead around 1915: books.google.com/ngrams/…
        – qwertzguy
        Jan 29 '15 at 4:00










      • And small nit: your link to google ngrams is unfortunately broken, the quotes needs to be removed in the query.
        – qwertzguy
        Jan 29 '15 at 4:05














      4












      4








      4






      I'll take a kick at this can, but it is pure speculation. Maybe someone can come up with a documented answer.



      Firstly, we should understand that "back" and "backward" are both adverbs. Both have a meaning which is "away from the front; toward the back". In this definition, they are synonymous.



      The implied verb in "back" and "forward" is go, as in "go back" or "go forward." The statement "go backward" is grammatically correct but idiomatically it's not how we would say it in English -- at least, the forms of English I'm familiar with. Native English speakers are more likely to say "go back." Look at this comparative chart of how often "go back" and "go backward" are used.



      That being said, in English user interfaces we will also use "previous" and "next". This is used more for a sequence of pages, such as Google results pages.



      As for French, "précédent" and "suivant" don't have a monopoly, either. I often see buttons like "< Retour" to mean "< Back". And in my Chrome interface right now, if I hover over the back and forward buttons, I get "Réculer d'une page" and "Avancer d'une page". Internet Explorer gives me a mix: "Retour" and "suivant".



      At the end of the day, what matters from a UX perspective is:




      • Your label is clear. "Backward" meets this criterion. A user would expect to go backward.

      • Your label is natural. "Backward" could cause a momentary hesitation, just because the wording is not an established convention.


      Hope that helps! Bonne chance !






      share|improve this answer














      I'll take a kick at this can, but it is pure speculation. Maybe someone can come up with a documented answer.



      Firstly, we should understand that "back" and "backward" are both adverbs. Both have a meaning which is "away from the front; toward the back". In this definition, they are synonymous.



      The implied verb in "back" and "forward" is go, as in "go back" or "go forward." The statement "go backward" is grammatically correct but idiomatically it's not how we would say it in English -- at least, the forms of English I'm familiar with. Native English speakers are more likely to say "go back." Look at this comparative chart of how often "go back" and "go backward" are used.



      That being said, in English user interfaces we will also use "previous" and "next". This is used more for a sequence of pages, such as Google results pages.



      As for French, "précédent" and "suivant" don't have a monopoly, either. I often see buttons like "< Retour" to mean "< Back". And in my Chrome interface right now, if I hover over the back and forward buttons, I get "Réculer d'une page" and "Avancer d'une page". Internet Explorer gives me a mix: "Retour" and "suivant".



      At the end of the day, what matters from a UX perspective is:




      • Your label is clear. "Backward" meets this criterion. A user would expect to go backward.

      • Your label is natural. "Backward" could cause a momentary hesitation, just because the wording is not an established convention.


      Hope that helps! Bonne chance !







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited 2 days ago









      Community

      1




      1










      answered Sep 17 '14 at 17:38









      Tim FitzGerald

      1636




      1636








      • 3




        Plus, for me, Go back and Go backward(s) are a bit different. Go back is return from some starting point, go backward(s) implies moving — without a stopping point per se — in reverse. Oddly, neither go forward and go forth seem to have the same implication as go back does. Crazy English language.
        – guifa
        Sep 18 '14 at 2:19










      • Interestingly "go forth" used to be more mainstream but "go forward" took the lead around 1915: books.google.com/ngrams/…
        – qwertzguy
        Jan 29 '15 at 4:00










      • And small nit: your link to google ngrams is unfortunately broken, the quotes needs to be removed in the query.
        – qwertzguy
        Jan 29 '15 at 4:05














      • 3




        Plus, for me, Go back and Go backward(s) are a bit different. Go back is return from some starting point, go backward(s) implies moving — without a stopping point per se — in reverse. Oddly, neither go forward and go forth seem to have the same implication as go back does. Crazy English language.
        – guifa
        Sep 18 '14 at 2:19










      • Interestingly "go forth" used to be more mainstream but "go forward" took the lead around 1915: books.google.com/ngrams/…
        – qwertzguy
        Jan 29 '15 at 4:00










      • And small nit: your link to google ngrams is unfortunately broken, the quotes needs to be removed in the query.
        – qwertzguy
        Jan 29 '15 at 4:05








      3




      3




      Plus, for me, Go back and Go backward(s) are a bit different. Go back is return from some starting point, go backward(s) implies moving — without a stopping point per se — in reverse. Oddly, neither go forward and go forth seem to have the same implication as go back does. Crazy English language.
      – guifa
      Sep 18 '14 at 2:19




      Plus, for me, Go back and Go backward(s) are a bit different. Go back is return from some starting point, go backward(s) implies moving — without a stopping point per se — in reverse. Oddly, neither go forward and go forth seem to have the same implication as go back does. Crazy English language.
      – guifa
      Sep 18 '14 at 2:19












      Interestingly "go forth" used to be more mainstream but "go forward" took the lead around 1915: books.google.com/ngrams/…
      – qwertzguy
      Jan 29 '15 at 4:00




      Interestingly "go forth" used to be more mainstream but "go forward" took the lead around 1915: books.google.com/ngrams/…
      – qwertzguy
      Jan 29 '15 at 4:00












      And small nit: your link to google ngrams is unfortunately broken, the quotes needs to be removed in the query.
      – qwertzguy
      Jan 29 '15 at 4:05




      And small nit: your link to google ngrams is unfortunately broken, the quotes needs to be removed in the query.
      – qwertzguy
      Jan 29 '15 at 4:05













      2














      We don't say back and forward. We say back and forth. ;-)



      Forward and backward are directions. Back, as in a back button, refers to going back to a previous state/position. Yes, that often involves also moving backward, i.e., traversing a sequence backward.



      But when you say "Go back" you are emphasizing the destination, a previous state or position. The direction and how you might get there are not important (not emphasized).



      If I ask whether you are going back to France, I'm not necessarily asking how you will get there. And I probably do not care whether you are retracing your steps backward, from how you got here from France. ;-)



      Driving backward means driving in reverse gear. Driving back home means returning home, whatever the route taken.






      share|improve this answer





















      • When speaking between us yes and my question is precisely why is it different in user interfaces of computers or even devices? Like a DVD player would have buttons labelled: back and forward. Why?
        – qwertzguy
        Sep 19 '14 at 9:50






      • 1




        If your question is limited to why it is different in UIs then I believe that it is off-topic. But I'm no expert on that.
        – Drew
        Sep 19 '14 at 14:27










      • I originally posted this question in UXstack exchange -_-
        – qwertzguy
        Sep 21 '14 at 15:39






      • 1




        UX is where it belongs, IMO. The choice of terms to use for the UI was apparently not based on any English rules, but was likely based on some UI considerations (perhaps simply saving space!).
        – Drew
        Sep 21 '14 at 16:06
















      2














      We don't say back and forward. We say back and forth. ;-)



      Forward and backward are directions. Back, as in a back button, refers to going back to a previous state/position. Yes, that often involves also moving backward, i.e., traversing a sequence backward.



      But when you say "Go back" you are emphasizing the destination, a previous state or position. The direction and how you might get there are not important (not emphasized).



      If I ask whether you are going back to France, I'm not necessarily asking how you will get there. And I probably do not care whether you are retracing your steps backward, from how you got here from France. ;-)



      Driving backward means driving in reverse gear. Driving back home means returning home, whatever the route taken.






      share|improve this answer





















      • When speaking between us yes and my question is precisely why is it different in user interfaces of computers or even devices? Like a DVD player would have buttons labelled: back and forward. Why?
        – qwertzguy
        Sep 19 '14 at 9:50






      • 1




        If your question is limited to why it is different in UIs then I believe that it is off-topic. But I'm no expert on that.
        – Drew
        Sep 19 '14 at 14:27










      • I originally posted this question in UXstack exchange -_-
        – qwertzguy
        Sep 21 '14 at 15:39






      • 1




        UX is where it belongs, IMO. The choice of terms to use for the UI was apparently not based on any English rules, but was likely based on some UI considerations (perhaps simply saving space!).
        – Drew
        Sep 21 '14 at 16:06














      2












      2








      2






      We don't say back and forward. We say back and forth. ;-)



      Forward and backward are directions. Back, as in a back button, refers to going back to a previous state/position. Yes, that often involves also moving backward, i.e., traversing a sequence backward.



      But when you say "Go back" you are emphasizing the destination, a previous state or position. The direction and how you might get there are not important (not emphasized).



      If I ask whether you are going back to France, I'm not necessarily asking how you will get there. And I probably do not care whether you are retracing your steps backward, from how you got here from France. ;-)



      Driving backward means driving in reverse gear. Driving back home means returning home, whatever the route taken.






      share|improve this answer












      We don't say back and forward. We say back and forth. ;-)



      Forward and backward are directions. Back, as in a back button, refers to going back to a previous state/position. Yes, that often involves also moving backward, i.e., traversing a sequence backward.



      But when you say "Go back" you are emphasizing the destination, a previous state or position. The direction and how you might get there are not important (not emphasized).



      If I ask whether you are going back to France, I'm not necessarily asking how you will get there. And I probably do not care whether you are retracing your steps backward, from how you got here from France. ;-)



      Driving backward means driving in reverse gear. Driving back home means returning home, whatever the route taken.







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Sep 18 '14 at 2:24









      Drew

      13.9k93055




      13.9k93055












      • When speaking between us yes and my question is precisely why is it different in user interfaces of computers or even devices? Like a DVD player would have buttons labelled: back and forward. Why?
        – qwertzguy
        Sep 19 '14 at 9:50






      • 1




        If your question is limited to why it is different in UIs then I believe that it is off-topic. But I'm no expert on that.
        – Drew
        Sep 19 '14 at 14:27










      • I originally posted this question in UXstack exchange -_-
        – qwertzguy
        Sep 21 '14 at 15:39






      • 1




        UX is where it belongs, IMO. The choice of terms to use for the UI was apparently not based on any English rules, but was likely based on some UI considerations (perhaps simply saving space!).
        – Drew
        Sep 21 '14 at 16:06


















      • When speaking between us yes and my question is precisely why is it different in user interfaces of computers or even devices? Like a DVD player would have buttons labelled: back and forward. Why?
        – qwertzguy
        Sep 19 '14 at 9:50






      • 1




        If your question is limited to why it is different in UIs then I believe that it is off-topic. But I'm no expert on that.
        – Drew
        Sep 19 '14 at 14:27










      • I originally posted this question in UXstack exchange -_-
        – qwertzguy
        Sep 21 '14 at 15:39






      • 1




        UX is where it belongs, IMO. The choice of terms to use for the UI was apparently not based on any English rules, but was likely based on some UI considerations (perhaps simply saving space!).
        – Drew
        Sep 21 '14 at 16:06
















      When speaking between us yes and my question is precisely why is it different in user interfaces of computers or even devices? Like a DVD player would have buttons labelled: back and forward. Why?
      – qwertzguy
      Sep 19 '14 at 9:50




      When speaking between us yes and my question is precisely why is it different in user interfaces of computers or even devices? Like a DVD player would have buttons labelled: back and forward. Why?
      – qwertzguy
      Sep 19 '14 at 9:50




      1




      1




      If your question is limited to why it is different in UIs then I believe that it is off-topic. But I'm no expert on that.
      – Drew
      Sep 19 '14 at 14:27




      If your question is limited to why it is different in UIs then I believe that it is off-topic. But I'm no expert on that.
      – Drew
      Sep 19 '14 at 14:27












      I originally posted this question in UXstack exchange -_-
      – qwertzguy
      Sep 21 '14 at 15:39




      I originally posted this question in UXstack exchange -_-
      – qwertzguy
      Sep 21 '14 at 15:39




      1




      1




      UX is where it belongs, IMO. The choice of terms to use for the UI was apparently not based on any English rules, but was likely based on some UI considerations (perhaps simply saving space!).
      – Drew
      Sep 21 '14 at 16:06




      UX is where it belongs, IMO. The choice of terms to use for the UI was apparently not based on any English rules, but was likely based on some UI considerations (perhaps simply saving space!).
      – Drew
      Sep 21 '14 at 16:06











      0














      The other answers thoroughly explained the English usage for "go back" and "back" and "backward".



      Given the context of the question and the specific inquiry, "Why do we use..." it is most likely due to user interface design considerations. "Back" has fewer letters than "backward". Brevity is preferable.






      share|improve this answer





















      • But then why forward?
        – qwertzguy
        Sep 21 '14 at 14:55






      • 1




        See my guesses in a comment to your question. The folks on SE might not even realize that UI considerations entered into the choice of terms for this, for the UI. They might have guessed that this is about English conventions, grammar rules, or some such.
        – Drew
        Sep 21 '14 at 16:05










      • @Drew "Given the context of the question and the specific inquiry, "Why do we use..." it is most likely due to user interface design considerations."
        – Ellie Kesselman
        Oct 4 '14 at 14:45






      • 1




        @EllieKesselman: That's my guess too. My guess is specifically: to save space (screen real estate). Back is clear enough. Some browsers just reduce the space to what is needed for a left arrow (right arrow for forward). Abbreviations are common in UI, especially when clear enough.
        – Drew
        Oct 4 '14 at 15:48






      • 1




        @EllieKesselman: FWIW, took a look at your website - "Not enough Thorsten Veblen!" Indeed. Keep up the good work.
        – Drew
        Oct 6 '14 at 21:14
















      0














      The other answers thoroughly explained the English usage for "go back" and "back" and "backward".



      Given the context of the question and the specific inquiry, "Why do we use..." it is most likely due to user interface design considerations. "Back" has fewer letters than "backward". Brevity is preferable.






      share|improve this answer





















      • But then why forward?
        – qwertzguy
        Sep 21 '14 at 14:55






      • 1




        See my guesses in a comment to your question. The folks on SE might not even realize that UI considerations entered into the choice of terms for this, for the UI. They might have guessed that this is about English conventions, grammar rules, or some such.
        – Drew
        Sep 21 '14 at 16:05










      • @Drew "Given the context of the question and the specific inquiry, "Why do we use..." it is most likely due to user interface design considerations."
        – Ellie Kesselman
        Oct 4 '14 at 14:45






      • 1




        @EllieKesselman: That's my guess too. My guess is specifically: to save space (screen real estate). Back is clear enough. Some browsers just reduce the space to what is needed for a left arrow (right arrow for forward). Abbreviations are common in UI, especially when clear enough.
        – Drew
        Oct 4 '14 at 15:48






      • 1




        @EllieKesselman: FWIW, took a look at your website - "Not enough Thorsten Veblen!" Indeed. Keep up the good work.
        – Drew
        Oct 6 '14 at 21:14














      0












      0








      0






      The other answers thoroughly explained the English usage for "go back" and "back" and "backward".



      Given the context of the question and the specific inquiry, "Why do we use..." it is most likely due to user interface design considerations. "Back" has fewer letters than "backward". Brevity is preferable.






      share|improve this answer












      The other answers thoroughly explained the English usage for "go back" and "back" and "backward".



      Given the context of the question and the specific inquiry, "Why do we use..." it is most likely due to user interface design considerations. "Back" has fewer letters than "backward". Brevity is preferable.







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Sep 20 '14 at 1:10









      Ellie Kesselman

      4,65832147




      4,65832147












      • But then why forward?
        – qwertzguy
        Sep 21 '14 at 14:55






      • 1




        See my guesses in a comment to your question. The folks on SE might not even realize that UI considerations entered into the choice of terms for this, for the UI. They might have guessed that this is about English conventions, grammar rules, or some such.
        – Drew
        Sep 21 '14 at 16:05










      • @Drew "Given the context of the question and the specific inquiry, "Why do we use..." it is most likely due to user interface design considerations."
        – Ellie Kesselman
        Oct 4 '14 at 14:45






      • 1




        @EllieKesselman: That's my guess too. My guess is specifically: to save space (screen real estate). Back is clear enough. Some browsers just reduce the space to what is needed for a left arrow (right arrow for forward). Abbreviations are common in UI, especially when clear enough.
        – Drew
        Oct 4 '14 at 15:48






      • 1




        @EllieKesselman: FWIW, took a look at your website - "Not enough Thorsten Veblen!" Indeed. Keep up the good work.
        – Drew
        Oct 6 '14 at 21:14


















      • But then why forward?
        – qwertzguy
        Sep 21 '14 at 14:55






      • 1




        See my guesses in a comment to your question. The folks on SE might not even realize that UI considerations entered into the choice of terms for this, for the UI. They might have guessed that this is about English conventions, grammar rules, or some such.
        – Drew
        Sep 21 '14 at 16:05










      • @Drew "Given the context of the question and the specific inquiry, "Why do we use..." it is most likely due to user interface design considerations."
        – Ellie Kesselman
        Oct 4 '14 at 14:45






      • 1




        @EllieKesselman: That's my guess too. My guess is specifically: to save space (screen real estate). Back is clear enough. Some browsers just reduce the space to what is needed for a left arrow (right arrow for forward). Abbreviations are common in UI, especially when clear enough.
        – Drew
        Oct 4 '14 at 15:48






      • 1




        @EllieKesselman: FWIW, took a look at your website - "Not enough Thorsten Veblen!" Indeed. Keep up the good work.
        – Drew
        Oct 6 '14 at 21:14
















      But then why forward?
      – qwertzguy
      Sep 21 '14 at 14:55




      But then why forward?
      – qwertzguy
      Sep 21 '14 at 14:55




      1




      1




      See my guesses in a comment to your question. The folks on SE might not even realize that UI considerations entered into the choice of terms for this, for the UI. They might have guessed that this is about English conventions, grammar rules, or some such.
      – Drew
      Sep 21 '14 at 16:05




      See my guesses in a comment to your question. The folks on SE might not even realize that UI considerations entered into the choice of terms for this, for the UI. They might have guessed that this is about English conventions, grammar rules, or some such.
      – Drew
      Sep 21 '14 at 16:05












      @Drew "Given the context of the question and the specific inquiry, "Why do we use..." it is most likely due to user interface design considerations."
      – Ellie Kesselman
      Oct 4 '14 at 14:45




      @Drew "Given the context of the question and the specific inquiry, "Why do we use..." it is most likely due to user interface design considerations."
      – Ellie Kesselman
      Oct 4 '14 at 14:45




      1




      1




      @EllieKesselman: That's my guess too. My guess is specifically: to save space (screen real estate). Back is clear enough. Some browsers just reduce the space to what is needed for a left arrow (right arrow for forward). Abbreviations are common in UI, especially when clear enough.
      – Drew
      Oct 4 '14 at 15:48




      @EllieKesselman: That's my guess too. My guess is specifically: to save space (screen real estate). Back is clear enough. Some browsers just reduce the space to what is needed for a left arrow (right arrow for forward). Abbreviations are common in UI, especially when clear enough.
      – Drew
      Oct 4 '14 at 15:48




      1




      1




      @EllieKesselman: FWIW, took a look at your website - "Not enough Thorsten Veblen!" Indeed. Keep up the good work.
      – Drew
      Oct 6 '14 at 21:14




      @EllieKesselman: FWIW, took a look at your website - "Not enough Thorsten Veblen!" Indeed. Keep up the good work.
      – Drew
      Oct 6 '14 at 21:14











      0














      Usually, when you go 'back' there is a destination in mind. As @Drew says - your precise route backwards is not usually the point. On the other hand, often, when you go ahead the destination is unclear and the route forwards is all you actually know. Strategists engage in forwards thinking without necessarily having a goal in mind. When you do know the position ahead that you are heading to, you go to the fore.






      share|improve this answer





















      • But in the case of a web browser for example, we do know the destination, the goal when clicking the 'forward' button and it's precise, since if isn't then the button is disabled. (my question is about usage of the words in user interfaces, not in literature).
        – qwertzguy
        Jan 29 '15 at 3:51
















      0














      Usually, when you go 'back' there is a destination in mind. As @Drew says - your precise route backwards is not usually the point. On the other hand, often, when you go ahead the destination is unclear and the route forwards is all you actually know. Strategists engage in forwards thinking without necessarily having a goal in mind. When you do know the position ahead that you are heading to, you go to the fore.






      share|improve this answer





















      • But in the case of a web browser for example, we do know the destination, the goal when clicking the 'forward' button and it's precise, since if isn't then the button is disabled. (my question is about usage of the words in user interfaces, not in literature).
        – qwertzguy
        Jan 29 '15 at 3:51














      0












      0








      0






      Usually, when you go 'back' there is a destination in mind. As @Drew says - your precise route backwards is not usually the point. On the other hand, often, when you go ahead the destination is unclear and the route forwards is all you actually know. Strategists engage in forwards thinking without necessarily having a goal in mind. When you do know the position ahead that you are heading to, you go to the fore.






      share|improve this answer












      Usually, when you go 'back' there is a destination in mind. As @Drew says - your precise route backwards is not usually the point. On the other hand, often, when you go ahead the destination is unclear and the route forwards is all you actually know. Strategists engage in forwards thinking without necessarily having a goal in mind. When you do know the position ahead that you are heading to, you go to the fore.







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Jan 28 '15 at 22:58









      Dan

      14.8k32157




      14.8k32157












      • But in the case of a web browser for example, we do know the destination, the goal when clicking the 'forward' button and it's precise, since if isn't then the button is disabled. (my question is about usage of the words in user interfaces, not in literature).
        – qwertzguy
        Jan 29 '15 at 3:51


















      • But in the case of a web browser for example, we do know the destination, the goal when clicking the 'forward' button and it's precise, since if isn't then the button is disabled. (my question is about usage of the words in user interfaces, not in literature).
        – qwertzguy
        Jan 29 '15 at 3:51
















      But in the case of a web browser for example, we do know the destination, the goal when clicking the 'forward' button and it's precise, since if isn't then the button is disabled. (my question is about usage of the words in user interfaces, not in literature).
      – qwertzguy
      Jan 29 '15 at 3:51




      But in the case of a web browser for example, we do know the destination, the goal when clicking the 'forward' button and it's precise, since if isn't then the button is disabled. (my question is about usage of the words in user interfaces, not in literature).
      – qwertzguy
      Jan 29 '15 at 3:51











      0














      I propose it is analogous to pages in a book. Also, similar usage happens when playing a board game: roll the dice and move forward X spaces; draw a card and go back one space. Both are examples of a linear progression of positions.






      share|improve this answer


























        0














        I propose it is analogous to pages in a book. Also, similar usage happens when playing a board game: roll the dice and move forward X spaces; draw a card and go back one space. Both are examples of a linear progression of positions.






        share|improve this answer
























          0












          0








          0






          I propose it is analogous to pages in a book. Also, similar usage happens when playing a board game: roll the dice and move forward X spaces; draw a card and go back one space. Both are examples of a linear progression of positions.






          share|improve this answer












          I propose it is analogous to pages in a book. Also, similar usage happens when playing a board game: roll the dice and move forward X spaces; draw a card and go back one space. Both are examples of a linear progression of positions.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 2 days ago









          already puzzled

          1675




          1675























              0














              I'll take a stab at this.



              The reasoning behind the usage of "Back" and "Forward" is to elicit the simplest response that will let the end user know exactly what the function of the button they're pressing does.



              The statement "Back" immediately upon hearing it brings to mind movement that one has already visited, and signifies a desire to "Return". (bonus points if you realize why the Enter key used to be referred to as the "Return" key.)



              Similarly, "Forward" implies to the end user that you have already visited a location which you have a desire to return to.



              There's little doubt that they were most likely chosen due to their monosyllabic conveyance. They are the words that are able to convey the largest amounts of meaning using the smallest amount of bits. In a time when internet browsers were new and hard drives were much, much smaller in size, "-wards" would have been considered an unnecessary allocation of bits, especially in a time when the commands for the equivalent "back" in MSDOS directory navigation was ".."






              share|improve this answer


























                0














                I'll take a stab at this.



                The reasoning behind the usage of "Back" and "Forward" is to elicit the simplest response that will let the end user know exactly what the function of the button they're pressing does.



                The statement "Back" immediately upon hearing it brings to mind movement that one has already visited, and signifies a desire to "Return". (bonus points if you realize why the Enter key used to be referred to as the "Return" key.)



                Similarly, "Forward" implies to the end user that you have already visited a location which you have a desire to return to.



                There's little doubt that they were most likely chosen due to their monosyllabic conveyance. They are the words that are able to convey the largest amounts of meaning using the smallest amount of bits. In a time when internet browsers were new and hard drives were much, much smaller in size, "-wards" would have been considered an unnecessary allocation of bits, especially in a time when the commands for the equivalent "back" in MSDOS directory navigation was ".."






                share|improve this answer
























                  0












                  0








                  0






                  I'll take a stab at this.



                  The reasoning behind the usage of "Back" and "Forward" is to elicit the simplest response that will let the end user know exactly what the function of the button they're pressing does.



                  The statement "Back" immediately upon hearing it brings to mind movement that one has already visited, and signifies a desire to "Return". (bonus points if you realize why the Enter key used to be referred to as the "Return" key.)



                  Similarly, "Forward" implies to the end user that you have already visited a location which you have a desire to return to.



                  There's little doubt that they were most likely chosen due to their monosyllabic conveyance. They are the words that are able to convey the largest amounts of meaning using the smallest amount of bits. In a time when internet browsers were new and hard drives were much, much smaller in size, "-wards" would have been considered an unnecessary allocation of bits, especially in a time when the commands for the equivalent "back" in MSDOS directory navigation was ".."






                  share|improve this answer












                  I'll take a stab at this.



                  The reasoning behind the usage of "Back" and "Forward" is to elicit the simplest response that will let the end user know exactly what the function of the button they're pressing does.



                  The statement "Back" immediately upon hearing it brings to mind movement that one has already visited, and signifies a desire to "Return". (bonus points if you realize why the Enter key used to be referred to as the "Return" key.)



                  Similarly, "Forward" implies to the end user that you have already visited a location which you have a desire to return to.



                  There's little doubt that they were most likely chosen due to their monosyllabic conveyance. They are the words that are able to convey the largest amounts of meaning using the smallest amount of bits. In a time when internet browsers were new and hard drives were much, much smaller in size, "-wards" would have been considered an unnecessary allocation of bits, especially in a time when the commands for the equivalent "back" in MSDOS directory navigation was ".."







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered 2 days ago









                  Sandwich

                  40824




                  40824






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to English Language & Usage Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.





                      Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                      Please pay close attention to the following guidance:


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fenglish.stackexchange.com%2fquestions%2f197012%2fwhy-do-we-use-back-and-forward-instead-of-backward-and-forward%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

                      Alcedinidae

                      RAC Tourist Trophy