<html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body text="#000000" bgcolor="#FFFFFF"> Subject for discussion: <a class="moz-txt-link-freetext" href="http://firstround.com/article/The-one-cost-engineers-and-product-managers-dont-consider#">http://firstround.com/article/The-one-cost-engineers-and-product-managers-dont-consider#</a> Interesting sentence in the middle: <meta charset="utf-8"> <span style="color: rgb(0, 0, 0); font-family: sans-serif; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 16px; orphans: auto; text-align: left; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); display: inline !important; float: none;">Consider DSLs, abstractions and the attraction to being the one to build a framework that gets leveraged for years. <span style="color: rgb(0, 0, 0); font-family: sans-serif; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 16px; orphans: auto; text-align: left; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"> I think Racket is a different target: education vs. engineering (is this true?). As a software engineer, I really agree with the article. Complexity is almost always a terrible thing, whether it is a DSL, a complex implementation of a simple interface, or just the one additional thing requested by product management that didn't fit. For Racket: are DSLs a source of complexity? Or would you argue that they reduce the complexity normally introduced with DSLs? John </body> </html>