Native (computing): Difference between revisions

Content deleted Content added
No edit summary
m Reverting possible vandalism by 2600:1700:B040:1650:3804:C654:A8F2:3BFE to version by Rhkramer. Report False Positive? Thanks, ClueBot NG. (3716297) (Bot)
Line 1:
{{Context|date=February 2016}}
 
NativeIn refers[[computing]], to'''Native''' thesoftware intendedor hardwaredata-formats onare whichthose athat program iswere designed to run on that [[operating system]]. For example, a [[Game Boy]] receives its software through a [[ROM cartridge|cartridge]] and on this cartridge, is the code that runs natively on the Game Boy.<ref>{{Cite web|url=http://www.computinghistory.org.uk/det/4033/Nintendo-Game-Boy/|title=Nintendo Game Boy - Game Console - Computing History|website=www.computinghistory.org.uk|access-date=2019-11-22}}</ref> In a more technical sense, native code is code written specifically for a certain [[Processor (computing)|processor]].<ref>{{Cite web|url=https://searchapparchitecture.techtarget.com/definition/native-code|title=What is native code? - Definition from WhatIs.com|website=SearchAppArchitecture|language=en|access-date=2019-11-22}}</ref> The only way to run this code on another processor is to use an [[emulator]], tricking the program into thinking it's using that same processor.<ref>{{Cite web|url=https://www.howtogeek.com/347530/the-importance-of-emulation-for-games-preservation/|title=Why Are Video Game Emulators So Important? (Because They Preserve Our History)|last=Pot|first=Justin|website=How-To Geek|language=en-US|access-date=2019-11-22}}</ref> This usually comes at the cost of speed.<ref>{{Cite web|url=https://www.makeuseof.com/tag/how-does-emulation-work/|title=How Does Emulation Work and Why Is It So Slow?|website=MakeUseOf|language=en-US|access-date=2019-11-22}}</ref>
In [[computing]], no one knows or can explain it's meaning for instance this garbage:[ '''Native''' software or data-formats are those that were designed to run on the [[operating system]] ]. WTF WIKIPEDIA!?
Native refers to the intended hardware on which a program is designed to run. For example, a [[Game Boy]] receives its software through a [[ROM cartridge|cartridge]] and on this cartridge, is the code that runs natively on the Game Boy.<ref>{{Cite web|url=http://www.computinghistory.org.uk/det/4033/Nintendo-Game-Boy/|title=Nintendo Game Boy - Game Console - Computing History|website=www.computinghistory.org.uk|access-date=2019-11-22}}</ref> In a more technical sense, native code is code written specifically for a certain [[Processor (computing)|processor]].<ref>{{Cite web|url=https://searchapparchitecture.techtarget.com/definition/native-code|title=What is native code? - Definition from WhatIs.com|website=SearchAppArchitecture|language=en|access-date=2019-11-22}}</ref> The only way to run this code on another processor is to use an [[emulator]], tricking the program into thinking it's using that same processor.<ref>{{Cite web|url=https://www.howtogeek.com/347530/the-importance-of-emulation-for-games-preservation/|title=Why Are Video Game Emulators So Important? (Because They Preserve Our History)|last=Pot|first=Justin|website=How-To Geek|language=en-US|access-date=2019-11-22}}</ref> This usually comes at the cost of speed.<ref>{{Cite web|url=https://www.makeuseof.com/tag/how-does-emulation-work/|title=How Does Emulation Work and Why Is It So Slow?|website=MakeUseOf|language=en-US|access-date=2019-11-22}}</ref>
 
== Applications ==