Porting some code from OCaml to Scheme, the amount of boilerplate that goes away is staggering. Of course, I am also losing a whole lot of safety and refactoring help. But this sure makes the cost visible.
-
-
13. Interactive state? Oops, all objects are opaque by default. That all makes debugging all the harder, and/or forces yet more boilerplate on you for string converters. 14. Parametricity is way cool, but makes data even more opaque, and then you need to break it for debugging.
-
15. Configuration files? User specified computations? In OCaml you'll soon reinvent your own crappy evaluators. All the advantages of static typing vanish, and all your tooling. Or you reinvent the world, badly. Meanwhile your users must use a crappy language.
- 11 more replies
New conversation -
-
-
This is a hugely under-appreciated aspect of many Lisp systems, even compared to the likes of usual Python dev workflows.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.
Read my blog!