Menu
Forums
New posts
Search forums
What's new
New posts
New profile posts
Latest activity
Vault
Time Travel Schematics
T.E.C. Time Archive
The Why Files
Have You Seen...?
Chronovisor
TimeTravelForum.tk
TimeTravelForum.net
ParanormalNetwork.net
Paranormalis.com
ConspiracyCafe.net
Streams
Live streams
Featured streams
Multi-Viewer
Members
Current visitors
New profile posts
Search profile posts
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
Time Travel Forum
Time Machines & Experiments
Assembly Language
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="MODAT7" data-source="post: 244555" data-attributes="member: 13649"><p>I had a semester of assembly language at university. It's good to know to understand how the low levels of a processor works, but I'd never use it on any real project that I'd do.</p><p></p><p>You do have absolute control if you write in assembler, but you have to know EVERY NITTY GRITTY DETAIL ABOUT EVERYTHING to really pull it off... and that will drive most people insane... especially since many of those low level hardware capabilities are poorly documented and implemented. Game programmers will often use short chunks of assembler because they need something that executes very fast. Games have to execute in real time, so this is somewhat expected. The rest of the game is usually written in C or C++.</p><p></p><p>Most operating systems are written in C or C++ (at least the core pieces that need to execute fast). Properly written code can be close to assembler speeds. Other higher level languages are anywhere from 10-50x slower. Java and Python are some of the worst in terms of bloat and lack of speed.</p><p></p><p>What coding language a time machine would use would depend on how fast it needs to execute. Low level stuff handling frequencies and such in real time would need something fast. If there's recording, video and audio codecs would need something fast. Overall monitoring and reporting could be done in something slower. Most of the time, programmers will chose the language more on what existing libraries and code already exist, so they don't have to program what's already been done. This makes sense to an extent, but if performance is needed and a slow and bloated language is chosen out of laziness, this becomes a very bad choice... and then they start yelling and arguing that your brand new computer isn't fast enough... and then a holy war breaks out and gets nasty.</p></blockquote><p></p>
[QUOTE="MODAT7, post: 244555, member: 13649"] I had a semester of assembly language at university. It's good to know to understand how the low levels of a processor works, but I'd never use it on any real project that I'd do. You do have absolute control if you write in assembler, but you have to know EVERY NITTY GRITTY DETAIL ABOUT EVERYTHING to really pull it off... and that will drive most people insane... especially since many of those low level hardware capabilities are poorly documented and implemented. Game programmers will often use short chunks of assembler because they need something that executes very fast. Games have to execute in real time, so this is somewhat expected. The rest of the game is usually written in C or C++. Most operating systems are written in C or C++ (at least the core pieces that need to execute fast). Properly written code can be close to assembler speeds. Other higher level languages are anywhere from 10-50x slower. Java and Python are some of the worst in terms of bloat and lack of speed. What coding language a time machine would use would depend on how fast it needs to execute. Low level stuff handling frequencies and such in real time would need something fast. If there's recording, video and audio codecs would need something fast. Overall monitoring and reporting could be done in something slower. Most of the time, programmers will chose the language more on what existing libraries and code already exist, so they don't have to program what's already been done. This makes sense to an extent, but if performance is needed and a slow and bloated language is chosen out of laziness, this becomes a very bad choice... and then they start yelling and arguing that your brand new computer isn't fast enough... and then a holy war breaks out and gets nasty. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Time Travel Forum
Time Machines & Experiments
Assembly Language
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Accept
Learn more…
Top