@fogus @buwilliams But when we use the same syntax for both we tell an engineer "this important" and often they can do a better job at it.
-
-
Replying to @nouswaves1 reply 0 retweets 0 likes
-
Replying to @buwilliams
@buwilliams@fogus Hahaha. Sorry, still learning how to explain myself!1 reply 0 retweets 0 likes -
Replying to @nouswaves
@buwilliams@fogus A small point - in Java the syntax for code and data are different so some of the work of separating them is done for me.1 reply 0 retweets 0 likes -
Replying to @nouswaves
@buwilliams@fogus That is they look visually different and perhaps there are different interfaces to the data.1 reply 0 retweets 0 likes -
Replying to @nouswaves
@buwilliams@fogus Because this is the case I probably put less thought into separating them further. It feels like my work has been done.1 reply 0 retweets 0 likes -
Replying to @nouswaves
@buwilliams@fogus So I have more of a tendency to complect them in the nasty way with state, etc.1 reply 0 retweets 0 likes -
Replying to @nouswaves
@buwilliams@fogus On the other hand homoiconic languages like Lisp (or those with good functional principles) make me understand that1 reply 0 retweets 0 likes -
Replying to @nouswaves
@buwilliams@fogus separating code and data isn't just about syntax/readability, but also other things like state/purity, etc.2 replies 0 retweets 0 likes -
Replying to @nouswaves
@sebinsua@buwilliams State and purity was what the original tweet was about.(Correct me if I'm wrong) And the point of the book also.1 reply 0 retweets 0 likes
@fogus @buwilliams Oh, I've not read the book (yet!) but I will at some point. I've heard good things.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.