Data should not be code. Code cannot be easily migrated to newer versions. Sometimes it seems our tools forget this.
-
-
-
My personal definition: data is something whose semantic can be statically analyzed
2 replies 0 retweets 1 like -
My personal pet-peeve are project dependencies. We have little tooling around static analysis of dependencies in Scala because they're normally expressed as code. Services like https://greenkeeper.io/ are then impossible, and I'm not sure we're getting much benefits in return
2 replies 0 retweets 3 likes -
Also, this is not a critique of sbt, all other tools in Scala have taken this path, with the only notable exception of Fury /cc
@propensive.2 replies 0 retweets 1 like -
I think there's actually more of a continuum between data and code. You can have complex data formats, or simple code languages.
1 reply 0 retweets 1 like
Take XSLT, for example. Is that code or data (or both!)? Arguably it's the worst of both...
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.