http://code.google.com/p/noop/What is Noop?
Noop (pronounced noh-awp, like the machine instruction) is a new language experiment that attempts to blend the best lessons of languages old and new, while syntactically encouraging what we believe to be good coding practices and discouraging the worst offenses. Noop is initially targeted to run on the Java Virtual Machine.
What is the status of Noop?
Right now, we are in an early design and development phase. You can't code anything interesting in Noop yet.
Why another language?
Our experience has been that developers often create code that's hard to test and maintain, without realizing it. On a large software project, this can create problems later on for the whole team. In analyzing this problem, we found that the root cause in many cases was language features - like globally visible state, misused subclassing, and API's that are easily misused. Noop will try to avoid these problems.
Who's behind Noop?
Noop is a side-project from a collection of like-minded developers and contributers. We hail from several companies, including (but not limited to) Google.
Noop is opinionated
The developers of Noop feel pretty strongly about good and bad practices in software development. Noop will support or deter these as best as possible. For example:
Noop says Yes to
* Dependency injection built into the language
* Testability - a seam between every pair of classes
* Syntax geared entirely towards readable code
* Executable documentation that's never out-of-date
* Properties, strong typing, and sensible modern standard library
Noop says No to
* Any statics whatsoever
* Implementation inheritance (subclassing)
* Unnecessary boilerplate
Dependency Injection changed the way we write software. Spring overtook EJB's in thoughtful enterprises, and Guice and PicoContainer are an important part of many well-written applications today.
Automated testing, especially Unit Testing, is also a crucial part of building reliable software that you can feel confident about supporting and changing over its lifetime. Any decent software shop should be writing some tests, the best ones are test-driven and have good code coverage.
Noop is a new language that will run on the Java Virtual Machine, and in source form will look similar to Java. The goal is to build dependency injection and testability into the language from the beginning, rather than rely on third-party libraries as other languages do.
Immutability and minimal variable scope are encouraged by making final/const behavior the default and providing easy access to a functional style. Testability is encouraged by providing Dependency Injection at the language level and a compact constructor injection syntax.
There are three proposed ways to use your Noop source files:
* Java translator: produces Java source. Allows you to use Noop without converting your codebase, but not all runtime features of the language are provided.
* Interpreter: reads and evaluates the Noop code through an interpreter. Slower, but will have a command-line interface
* Compiled: to Java bytecode.
* Join the mailing list: email@example.com
* Read about the Proposed features
* Read the detailed Proposals