Difference: MecrispCube (3 vs. 4)

Revision 42020-02-18 - PeterSchmid

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
%DASHBOARD{ section="banner"
Line: 297 to 297
 

What's good about Forth

Changed:
<
<
  • small
  • easy to understand
  • extendable
  • adaptable to programmer
  • interactive
>
>
  • small
  • easy to understand
  • extendable
  • adaptable to programmer
  • interactive
 
  • open compiler/interpreter
  • simple architecture
  • source code available
Line: 309 to 309
 

What's bad about Forth

  • NIH (not invented here)
Changed:
<
<
  • cryptic reverse polish notation
>
>
  • cryptic reverse polish notation
 
  • difficult to learn
  • documentation sometimes lacking or unavailable
Changed:
<
<
  • unconventional syntax
  • no linkage with other languages
>
>
  • unconventional syntax
  • no linkage with other languages
 
  • getting more complex
Changed:
<
<
  • lack of data typing
>
>
  • lack of data typing
 
  • source (proprietary protection problem)

What 21st Century Forth should be

Changed:
<
<
  • work in embedded applications
>
>
  • work in embedded applications
 
  • work with networks and Internet
  • work with large systems (operating systems, graphic user interface)
  • be able to be taught to programmers and engineers
Line: 334 to 334
 
  • better gui/window editor w/more information
  • package confidence
  • more debugger integration
Changed:
<
<
  • works with newer CPUs
>
>
  • works with newer CPUs (embedded systems, MCU)
 
  • publications
  • big daddy $$$
  • educational opportunities
Changed:
<
<
  • more types of multitasking/multiprocessing
>
>
  • more types of multitasking/multiprocessing pre-emtive multitasking
 

21st Century Forth desires and vision

  • real/virtual machines/core
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback