Lesson plan

Fantom (programming language)

Fantom, formerly Fan, is a general-purpose object-oriented programming language, created by Brian Frank and Andy Frank. It runs on the Java Runtime Environment (JRE), JavaScript, and the .NET Common Language Runtime (CLR) (.NET support is considered "prototype" status). Its stated goal is to provide a standard library application programming interface (API). Fantom uses a curly brace syntax, supports functional programming through closures and concurrency through the actor model, and blends aspects of both static and dynamic typing. The original name of the Fantom programming language was Fan, named after the Fan District neighborhood in which the creators live in Richmond, Virginia. In November 2009, the name of the project was officially changed from Fan to Fantom due to searchability concerns raised by its community. Fantom is free and open-source software under Academic Free License 3.0 and is available for operating systems including Windows and Unix-like: Linux, macOS.

Back to article

Article summary

Fantom, formerly Fan, is a general-purpose object-oriented programming language, created by Brian Frank and Andy Frank. It runs on the Java Runtime Environment (JRE), JavaScript, and the .NET Common Language Runtime (CLR) (.NET support is considered "prototype" status). Its stated goal is to provide a standard library application programming interface (API). Fantom uses a curly brace syntax, supports functional programming through closures and concurrency through the actor model, and blends aspects of both static and dynamic typing. The original name of the Fantom programming language was Fan, named after the Fan District neighborhood in which the creators live in Richmond, Virginia. In November 2009, the name of the project was officially changed from Fan to Fantom due to searchability concerns raised by its community. Fantom is free and open-source software under Academic Free License 3.0 and is available for operating systems including Windows and Unix-like: Linux, macOS.

Key claims

No claims recorded.

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  3. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.