Draft:Pony (programming language): Difference between revisions
No edit summary |
No edit summary |
||
Line 60: | Line 60: | ||
* [http://www.ponylang.org Offical website] |
* [http://www.ponylang.org Offical website] |
||
* [https://medium.com/@KevinHoffman/composition-over-inheritance-in-pony-33bbe107914 Composition over Inheritance with Pony] |
* [https://medium.com/@KevinHoffman/composition-over-inheritance-in-pony-33bbe107914 Composition over Inheritance with Pony] |
||
* [https://qconlondon.com/ln2017/presentation/pony-co-designing-type-system-and-run-time QCon London: Co-Designing a Type System and Runtime] |
|||
* [https://www.infoq.com/interviews/clebsch-pony InfoQ Interview: Sylvan Clebsch on the Actor-Model Language Pony, Garbage Collection, Capabilities, Concurrency] |
* [https://www.infoq.com/interviews/clebsch-pony InfoQ Interview: Sylvan Clebsch on the Actor-Model Language Pony, Garbage Collection, Capabilities, Concurrency] |
||
* [https://c7.se/from-go-to-pony/ From Go to Pony] |
|||
* [https://www.infoq.com/news/2016/03/pony-fintech InfoQ: Using the Actor-model Language Pony for FinTech] |
* [https://www.infoq.com/news/2016/03/pony-fintech InfoQ: Using the Actor-model Language Pony for FinTech] |
||
* [https://www.youtube.com/watch?v=KvLjy8w1G_U Pony: Making it easy to write efficient, concurrent, data race free programs] at [http://curry-on.org/2015/sessions/pony-making-it-easier-to-write-efficient-concurrent-programs.html Curry On 2015] associated with [[ECOOP]] [http://2015.ecoop.org/ 2015] |
* [https://www.youtube.com/watch?v=KvLjy8w1G_U Pony: Making it easy to write efficient, concurrent, data race free programs] at [http://curry-on.org/2015/sessions/pony-making-it-easier-to-write-efficient-concurrent-programs.html Curry On 2015] associated with [[ECOOP]] [http://2015.ecoop.org/ 2015] |
Revision as of 15:53, 15 July 2017
Submission declined on 20 January 2017 by SwisterTwister (talk). This submission's references do not show that the subject qualifies for a Wikipedia article—that is, they do not show significant coverage (not just passing mentions) about the subject in published, reliable, secondary sources that are independent of the subject (see the guidelines on the notability of web content). Before any resubmission, additional references meeting these criteria should be added (see technical help and learn about mistakes to avoid when addressing this issue). If no additional references exist, the subject is not suitable for Wikipedia.
Where to get help
How to improve a draft
You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Editor resources
This draft has not been edited in over six months and qualifies to be deleted per CSD G13. Declined by SwisterTwister 7 years ago. Last edited by Autodidaddict 7 years ago. Reviewer: Inform author.This draft has been resubmitted and is currently awaiting re-review. |
- Comment: This would've needed all major reviews. SwisterTwister talk 19:29, 20 January 2017 (UTC)
Paradigm | Actor model |
---|---|
Designed by | Sylvan Clebsch |
First appeared | November 9, 2012 |
Stable release | 0.15.0
/ August 7, 2017 |
Typing discipline | strong, static, inferred, structural |
Implementation language | C |
License | BSD-2[1] |
Website | www |
Influenced by | |
E, Rust | |
Influenced | |
Encore |
Pony (often referred to as ponylang) is a free and open source, object-oriented, actor model, capabilities-secure, high performance programming language. Pony blends together the race-free guarantees of the Rust programming language, static typing, generics, traits, and the structural typing so well used by the Go programming language. Its reference capabilities[2] system allows developers to be explicit about how data is shared among components and actors, visually indicating what can and cannot be read from or written to.
This allows Pony to reside somewhere between the strict rules of Rust's borrow checker and Go's flexible structural typing while still being able to make race-free and data sharing guarantees.
History
In 2011, Sylvan Clebsch created a C-based actor library in order to solve some real problems for software he was creating. Ultimately this library became the first implementation of Pony in 2012.
Language design
At its core, Pony is a systems language designed around safety and performance.
- Type Safe - Pony is a very type safe language. For more details on why, check out the mathematical proof[3].
- Memory Safe - There are no dangling pointers and no buffer overruns. Like Rust, Pony does not even allow the concept of null.
- Exception-Safe -There are no runtime exceptions. All exceptions have defined semantics, and they are always caught.
- Data-race Free - Pony does not have locks or atomic operations. Instead, the type system ensures at compile time that your concurrent program can never have data races. This allows developers to write highly concurrent code with less change of problems occurring in the use of concurrency primitives.
- Deadlock-Free - Pony lacks language-level constructs to create locks. It is impossible to write code that compiles that will produce a deadlock.
- Native Code - Pony is an ahead-of-time (AOT) compiled language. There is no interpreter or virtual machine
- Compatible with C - Interop with C is enabled through FFI
- Garbage Collected - Each actor's heap is collected separately, there is no "stop the world" collection.
Examples
Here are a few examples of idiomatic Pony.
Hello World
In Pony, instead of a main function, there is a main actor. The creation of this actor serves as the entry point into the Pony program.
actor Main
new create(env: Env) =>
env.out.print("Hello, world!")
There are no global variables in Pony, everything must be contained within an instance of a class or an actor. As such, even the environment that allows for printing to stdout is passed as a parameter.
References
- ^ https://github.com/ponylang/ponyc/blob/master/LICENSE
- ^ "Deny capabilities for safe, fast actors". 2015-10-26.
{{cite web}}
: Unknown parameter|authors=
ignored (help) - ^ https://www.ponylang.org/media/papers/fast-cheap.pdf
External links
- Offical website
- Composition over Inheritance with Pony
- QCon London: Co-Designing a Type System and Runtime
- InfoQ Interview: Sylvan Clebsch on the Actor-Model Language Pony, Garbage Collection, Capabilities, Concurrency
- From Go to Pony
- InfoQ: Using the Actor-model Language Pony for FinTech
- Pony: Making it easy to write efficient, concurrent, data race free programs at Curry On 2015 associated with ECOOP 2015
Review waiting, please be patient.
This may take 8 weeks or more, since drafts are reviewed in no specific order. There are 1,781 pending submissions waiting for review.
Where to get help
How to improve a draft
You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Editor resources
Reviewer tools
|