Display title | Porting Disaster |
Default sort key | Porting Disaster |
Page length (in bytes) | 177,540 |
Namespace ID | 0 |
Page ID | 125764 |
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 | 2 (0 redirects; 2 non-redirects) |
Page image | |
Edit | Allow all users (infinite) |
Move | Allow all users (infinite) |
Delete | Allow all users (infinite) |
Page creator | m>Import Bot |
Date of page creation | 21:27, 1 November 2013 |
Latest editor | Blakegripling ph (talk | contribs) |
Date of latest edit | 10:22, 15 January 2024 |
Total number of edits | 48 |
Recent number of edits (within past 180 days) | 1 |
Recent number of distinct authors | 1 |
Transcluded templates (9) | Templates used on this page:
|
Description | Content |
Article description: (description ) This attribute controls the content of the description and og:description elements. | Porting a program to another system is seldom an easy task. If you had the good fortune to be able to consistently use cross-platform libraries while writing the original program, you might be able to get away without having to do any code rewriting. Otherwise, you're looking at significant rewrites ahead. Multi Platform development can help avoid this, but if the developers are rushed, the version for system with which they're least-familiar will likely suffer. |