Gosu (programming language): Difference between revisions

Revision as of 09:22, 6 September 2018

Revision as of 09:09, 7 September 2018

Line 33:

==Philosophy==

Gosu language creator and development lead, Scott McKinney, emphasizes pragmatism as the overriding principle in Gosu's design.<ref name=drdobbs>{{cite web|url=http://www.drdobbs.com/open-source/language-of-the-month-gosu/231001429#|title=Language of the Month: Gosu|date=2012-12-07|publisher=[[Dr. Dobb's Journal]]}}</ref> For instance, [[code readability]] iswon paramountout in design contests between readability and [[concision]]. WhileThis theemphasis Gosuwas teampartially triesdue to strikeMcKinney's need for a balance[[web betweentemplate concisenesssystem]]; and readability,Gosu's itis favorsinfluenced readabilityby asthat codeof tends[[Apache toVelocity|Velocity]] beand read[[JavaServer manyPages]]. times[[XML moreSchema thanDefinition]]s itare isalso written.heavily integrated Thisinto simplethe idealanguage, hasas helpedwell toas keep[[object-relational Gosumapping]]s, abecause low-ceremony,of pragmaticthe language.business requirements into which Gosu was born.

Discoverability is also a key principle that guides the language's design. With the aid of modern IDEs programmers must be able to quickly and deterministically apply static analysis to large Gosu codebases, some of them approaching 1M lines of code. As such Gosu's rich static type system is a necessary ingredient toward best of breed tooling via static analysis, rich parser feedback, intelligent code completion, deterministic refactoring, usage analysis, navigation, and the like. To that end the Gosu team is highly involved in both language and tooling/IDE design.

==Syntax and semantics==