Talk:Strict programming language: Difference between revisions

Content deleted Content added
Scheme
Line 1:
== Disadvantages ==
 
One of the disadvantages listed is "language must be pure". IIlisted is dcts, semannon-strict ticdisadvantage advantages keeps you "honest" reason why there even donon't see this as a disadvantage, but just a consequence. In fact, I see it as a majormdisadvs advantage! All strictany purely functional languages gavetoday in(and why things like monadic IO was invented - they had to thebecause sirenthecircumspace callusage ofreasoningy couldn't have side effects,ed non-strict semanticsinto keepsa youless "honestevangelicastrict purely l" form stances those coantage is the one uld be seen as disadvantages).and isThe onlof side effeexithat is probably the reasonin whywhat there. evenI existsthink anythe purelywhole functionalsection languagesshould todaybe (andrefactoredfunctional whythe thingssilanguages likegave monadiceffectsy IO! wasAll invented -laziness theyensured hadabout to(i.e. becauserather theythan couldn'ttalking haveabout side"disadvantages", talk about "consequences", and perhaps effects without them, andandtruly lazinessan ensuredundisputajor thatstthat!).in to ren call
The only disadvantage that is truly an undisputed disadvantage is the one about space usage reasoning. I think the whole section should be refactored into a less "evangelical" form (i.e. rather than talking about "disadvantages", talk about "consequences", and perhaps in what circumstances those could be seen as disadvantages).
 
== Common Lisp ==