#forth_language search results

AmForth, you say you do not understand what a unicorn is? 😎 #Forth_language #ForthLanguage #Forth

PeterMortensen's tweet image. AmForth, you say you do not understand what a unicorn is? 😎  #Forth_language #ForthLanguage #Forth

Chuck Moore's (inventor of Forth) "fireside chat" 2019 edition (real start at 01 min 14 secs): youtube.com/watch?v=3ML-pJ… #Forth #Forth_language


"And this is what makes Forth different than 'C'. I think this is one of the unique capabilities of Forth." --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"Local variables are not only useless, they are harmful." --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"Files are not a big part of any typical application, but it is a singularly useless part." --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"They have lost the ability to do some things in interpret mode in the course of compiling." --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"... and can lead to very compact code on the order of 1% of the kind of code you get if you don't have these three behaviors." --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"...if a small group of people got together and decided to challenge Microsoft. We could replicate their software in 1/10 of 1% of the code." --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"We could feasibly do that with a small team in a year or two. But again why destroy an industry? That is probably not a wise thing to do." --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"In addition to the two stacks, in addition to high factoring, the fact that you can move back and forth in the three behaviors of words is very important" --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"And I think that this has gotten lost in these mega-Forth systems. They have lost the ability to compile at runtime. All you can do is execute." --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"A Forth word should not have more than one or two arguments. This stack which people have so much trouble manipulating should never be more than three or four deep." --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"Get rid of all the double words. We don't need to do 64 bit arithmetic. Machines now are 32 bits or at least 20 bits and in no case are double precision arithmetic relevant." --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"For example, I wish I knew what to tell you that would lead you to write good Forth. I have demonstrated ... applications where I can reduce the amount of code by 90% percent and in some cases 99%" --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"Interprettng is more efficient than executing. In order to compile anything you have to interpret it first. ... may as well execute it and be done with it instead of ... looking at it again at execute time." --Chuck Moore ultratechnology.com/moore4th.htm #Forth #Forth_language


"Good Forth code shouldn't require you to read and reason out exactly what is happening ... It should convey the gist of what is happening on a high level and then you drill down if needed. It's a form of literate programming." github.com/ForthHub/discu… #Forth_language #Forth


Chuck Moore's (inventor of Forth) "fireside chat" 2019 edition (real start at 01 min 14 secs): youtube.com/watch?v=3ML-pJ… #Forth #Forth_language


"Good Forth code shouldn't require you to read and reason out exactly what is happening ... It should convey the gist of what is happening on a high level and then you drill down if needed. It's a form of literate programming." github.com/ForthHub/discu… #Forth_language #Forth


AmForth, you say you do not understand what a unicorn is? 😎 #Forth_language #ForthLanguage #Forth

PeterMortensen's tweet image. AmForth, you say you do not understand what a unicorn is? 😎  #Forth_language #ForthLanguage #Forth

"They have lost the ability to do some things in interpret mode in the course of compiling." --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"And I think that this has gotten lost in these mega-Forth systems. They have lost the ability to compile at runtime. All you can do is execute." --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"We could feasibly do that with a small team in a year or two. But again why destroy an industry? That is probably not a wise thing to do." --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"...if a small group of people got together and decided to challenge Microsoft. We could replicate their software in 1/10 of 1% of the code." --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"In addition to the two stacks, in addition to high factoring, the fact that you can move back and forth in the three behaviors of words is very important" --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"And this is what makes Forth different than 'C'. I think this is one of the unique capabilities of Forth." --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"... and can lead to very compact code on the order of 1% of the kind of code you get if you don't have these three behaviors." --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"For example, I wish I knew what to tell you that would lead you to write good Forth. I have demonstrated ... applications where I can reduce the amount of code by 90% percent and in some cases 99%" --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"Interprettng is more efficient than executing. In order to compile anything you have to interpret it first. ... may as well execute it and be done with it instead of ... looking at it again at execute time." --Chuck Moore ultratechnology.com/moore4th.htm #Forth #Forth_language


"Get rid of all the double words. We don't need to do 64 bit arithmetic. Machines now are 32 bits or at least 20 bits and in no case are double precision arithmetic relevant." --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"Local variables are not only useless, they are harmful." --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"Files are not a big part of any typical application, but it is a singularly useless part." --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"A Forth word should not have more than one or two arguments. This stack which people have so much trouble manipulating should never be more than three or four deep." --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


"Stacks are not a solve-all-problems concept, but they are very very useful, especially for information hiding and you have to have two of them." --Chuck Moore (inventor of Forth) ultratechnology.com/moore4th.htm #Forth #Forth_language


No results for "#forth_language"

AmForth, you say you do not understand what a unicorn is? 😎 #Forth_language #ForthLanguage #Forth

PeterMortensen's tweet image. AmForth, you say you do not understand what a unicorn is? 😎  #Forth_language #ForthLanguage #Forth

Loading...

Something went wrong.


Something went wrong.


United States Trends