Timeline for "New" vs. "Create"
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 6, 2023 at 13:42 | comment | added | Dan Jacobson | All I know is a husband and wife make the decision to create a baby now, not nine months later. So for me the create button is the one you push when you start something. | |
| May 24, 2014 at 21:51 | comment | added | Jason A. | In English the action would be to "Create a new blank document". And "Add a record" to the record keeping system (database is now in the vernacular) or "Add a post" to a discussion. Potentially the distinction made in this answer may be system implementation leaking into the user domain. | |
| May 24, 2014 at 21:06 | comment | added | supercat | @AmeliaBR: I would expect that `Create..." would open a modal dialog box which would be used to describe the new thing to be created; the object should not actually be created until the user has approved such action by 'OK'ing (rather than cancelling) the dialog. | |
| May 22, 2014 at 14:41 | vote | accept | Yosef Waysman | ||
| May 22, 2014 at 2:46 | comment | added | AmeliaBR | This was my first instinct as well. "Create" implies that something is actually going to exist after you click the button, e.g., based on some input you've already entered. For working with a database, it's perfectly reasonable to me to have "New" button that opens a blank form and then a "Create" button to save the content of that form. The "Create" button would then be replaced with "Update" (or something similar) when editing an existing entry. | |
| May 20, 2014 at 13:53 | history | answered | Yosef Waysman | CC BY-SA 3.0 |