Raku (programming language): Difference between revisions

Content deleted Content added
wl
Citation bot (talk | contribs)
Add: publisher. | Use this bot. Report bugs. | Suggested by Abductive | #UCB_webform 3033/3850
Line 32:
 
==History==
{{Quotation|text=In Perl 6, we decided it would be better to fix the language than fix the user.|author=Larry Wall<ref>{{cite book|title=Masterminds of Programming: Conversations with the Creators of Major Programming Languages|first1=Federico|last1=Biancuzzi|first2=Shane|last2=Warden|year=2009|publisher="O'Reilly Media, Inc." |isbn=978-0596515171|url=https://books.google.com/books?id=yB1WwURwBUQC&q=%22In%20Perl%206%2C%20we%20decided%20it%20would%20be%20better%20to%20fix%20the%20language%20than%20fix%20the%20user%22}}</ref>}}
 
The Raku design process was first announced on 19 July 2000, on the fourth day of that year's [[O'Reilly Open Source Convention|Perl Conference]],<ref>{{cite web | title=Report from the Perl Conference | url=http://www.perl.com/pub/a/2000/08/tpc4.html | author=Kline, Joe | date=2000-08-21 }}</ref> by [[Larry Wall]] in his ''[[Perl#State of the Onion|State of the Onion]] 2000'' talk.<ref>{{cite web | title=State of the Onion 2000 | author=Wall, Larry | publisher=O'Reilly Network | url=http://www.perl.com/pub/a/2000/10/23/soto2000.html | year=2000 | author-link=Larry Wall}}</ref> At that time, the primary goals were to remove "historical warts" from the language; "easy things should stay easy, hard things should get easier, and impossible things should get hard"; a general cleanup of the internal design and [[Application programming interface|APIs]]. The process began with a series of [[Request for Comments|requests for comments]] or "RFCs". This process was open to all contributors, and left no aspect of the language closed to change.<ref>{{cite web | title=About Perl 6 RFCs | author=The Perl Foundation | url=https://raku.org/archive/rfc/meta/ | year=2000}}</ref>