Quick Search
Browse
Pages
Blog
Labels
Attachments
Mail
Advanced
What’s New
Space Directory
Feed Builder
Keyboard Shortcuts
Confluence Gadgets
Log In
Sign Up
Dashboard
Clojure Design
Copy Page
You are not logged in. Any changes you make will be marked as
anonymous
. You may want to
Log In
if you already have an account. You can also
Sign Up
for a new account.
This page is being edited by
.
Paragraph
Paragraph
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Preformatted
Quote
Bold
Italic
Underline
Colour
More colours
Strikethrough
Subscript
Superscript
Monospace
Clear Formatting
Bullet list
Numbered list
Outdent
Indent
Align left
Align center
Align right
Link
Table
Insert
Insert Content
Image
Link
Attachment
Symbol
Emoticon
Wiki Markup
Horizontal rule
tinymce.confluence.insert_menu.macro_desc
Info
JIRA Issue
Status
Gallery
Tasklist
Table of Contents
Other Macros
Undo
Redo
Keyboard Shortcuts Help
<p>Adding a feature to Clojure is not easy, for the following reasons:</p> <ol> <li>A programming language sits at the bottom, and impacts everything else. Rich is extremely conservative in adding new things.</li> <li>Features need to solve problems. Many things have features, but what problems do they solve? The purpose of this design wiki is to state problems, their possible solutions, and tradeoffs, prior to implementing anything.</li> <li>The language needs to provide things that can't (or can't easily) be provided elsewhere. Many proposed features are conveniences that should start their lives in libraries, not in the language.</li> <li>"Good" is not a sufficient reason. What would Clojure look like if every good idea+impl was added as a feature? The community is full of good ideas. Most of them will never be in Clojure.</li> </ol>
Attachments
Labels
Location
< Edit
Preview >
Loading…
Save
Cancel
Next hint
search
attachments
weblink
advanced