On Tuesday, November 8, 2016 at 2:28:54 AM UTC-6, Colin Yates wrote:
>
> The ship has indeed sailed. However, it is exactly these moments when 
> software starts to degrade - there are many examples of crufty 
> software crippled by legacy decisions. 
>

I completely disagree with this idea, particularly in the realm of 
programming languages. Java did not become one of the most popular 
languages ever by redoing and breaking things every release. The stability 
of the Java APIs is an essential ingredient in their success. Clojure leans 
far, far in this direction. I'll refer you to Brian Goetz's Conj keynote a 
couple years ago:

https://www.youtube.com/watch?v=2y5Pv4yN0b0
 

> I would much rather have ruthless application of 'good' engineering, 
> deprecating where necessary than continue to pay the cost of a poor 
> decision with every new person. 


In my opinion, 'good' engineering involves making progress while working 
within your constraints.
 

> Just remember that every 'yeah, it has 
> always worked like that' or 'yeah, I know, just accept it' a puppy 
> riding on the back of a unicorn led by an angel dies. 
>
> Optimise for the current users or optimise for the new user? Almost 
> always optimising for the new user is the right decision. 
>

Rich has done talks about his perspective on this.

https://github.com/matthiasn/talk-transcripts/blob/master/Hickey_Rich/DesignCompositionPerformance.md

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to