@propensive Absolutely, and for a library you never know if recompilation and redistribution is trivial. /cc @aloiscochard
-
This Tweet is unavailable.
-
-
Replying to @viktorklang
@viktorklang I don't see any good reason for the design you guys took. /cc@propensive2 replies 0 retweets 0 likes -
Replying to @aloiscochard
@aloiscochard Config is for things that vary w. deployment, decisions that the dev in genral does not control at buildtime. /cc@propensive1 reply 0 retweets 0 likes -
Replying to @viktorklang
@viktorklang@aloiscochard Library authors shouldn't decide which parts of my system are going to vary at deployment. Code should be default1 reply 2 retweets 2 likes -
Replying to @bmjames
@bmjames You are free to disallow anything to vary at deployment—you provide the config, and you can generate it with code./Cc@aloiscochard1 reply 0 retweets 0 likes -
Replying to @viktorklang
@viktorklang@aloiscochard wilfully missing the point, as usual1 reply 1 retweet 0 likes -
Replying to @bmjames
@bmjames pro tip: assume@viktorklang has thought things through; Akka just takes config thru one inlet, giving users complete freedom1 reply 0 retweets 0 likes -
Replying to @rolandkuhn
@bmjames@viktorklang that the one inlet has a type that supports parsing text files is unrelated (but generally well-liked)2 replies 0 retweets 1 like -
Replying to @rolandkuhn
@rolandkuhn I am well aware of the (crap) argument that stringly typed gives "freedom".2 replies 0 retweets 0 likes
@bmjames @rolandkuhn Try more assuming having thought it through pls.
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.