Display title | Software Porting |
Default sort key | Software Porting |
Page length (in bytes) | 4,099 |
Namespace ID | 0 |
Page ID | 8253 |
Page content language | en - English |
Page content model | wikitext |
Indexing by robots | Allowed |
Number of redirects to this page | 0 |
Counted as a content page | Yes |
Number of subpages of this page | 0 (0 redirects; 0 non-redirects) |
Edit | Allow all users (infinite) |
Move | Allow all users (infinite) |
Delete | Allow all users (infinite) |
Page creator | prefix>Import Bot |
Date of page creation | 21:27, 1 November 2013 |
Latest editor | MilkmanConspiracy (talk | contribs) |
Date of latest edit | 04:23, 31 March 2024 |
Total number of edits | 11 |
Recent number of edits (within past 180 days) | 2 |
Recent number of distinct authors | 1 |
Description | Content |
Article description: (description ) This attribute controls the content of the description and og:description elements. | The term porting is one that is feared by software developers, loved by management, and possibly thrown left and right by consumers. Software porting is when software written for one environment, which can be a particular hardware configuration, OS, API, etc., is written for another environment. The reality sets in when every environment is typically different from one another. It's like trying to make San Francisco Sourdough Bread when you're in another part of the world.[1] |