# Introduction ![Cheddar](https://2527000323-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MHghMx2GdJkKMz7uMGd%2Fsync%2Fb2adb9b7b2264c98696f71b470c46929fe9add73.png?generation=1600625477199384\&alt=media) **Cheddar** is a [high-level](https://en.wikipedia.org/wiki/High-level_programming_language), [dynamic](https://en.wikipedia.org/wiki/Dynamic_programming_language), [interpreted](https://en.wikipedia.org/wiki/Interpreted_language), [duck typed](https://en.wikipedia.org/wiki/Duck_typing) programming language. [JavaScript](https://en.wikipedia.org/wiki/JavaScript), [Ruby](https://en.wikipedia.org/wiki/Ruby_), and [Swift](http://swift.org) have been large influences on its development. ## The goal of Cheddar The goal of Cheddar is to be a **powerful**, **extensible** programming language. Cheddar puts the entire power of the language in your hands. This lets you develop powerful programs, with the least syntax overhead possible. We designed the syntax to be **beautiful** and **readable**. You should be able to understand the program at a glance. Lines should line up, and code blocks should be clear. You get **freedom** when using Cheddar. Cheddar promotes good practice through deterrents, but Cheddar never forces practices upon you. When you code in Cheddar, you can make the choice of how you'd like to design your code. You never need to worry about syntax or functionality. You **choose** how you want to code in Cheddar. Cheddar is designed for powerful, large-scale applications, but also quick scripting. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.cheddar.vihan.org/docs/master.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.