desc

15 ms·

1. 91.▲
   by desc 8y ago

   Lisp has these advantages too, to an infinite degree. It's a wonderful teaching language for this reason: you can literally express any concept any way, introspect upon it, and execute it however. The downside is that you end up buildi
2. 92.▲
   by desc 8y ago

   I wholeheartedly agree with this assessment. Metaprogramming is incredibly powerful, and has its place, but it generally comes down to 'defining your own language'. It cannot merely be Javascript any more: one must learn the idiom
3. 93.▲
   by desc 8y ago

   Indeed. It's doable, but requires a reasonably fast rollout tempo and a manageable level of technical debt. It is utterly impractical when you're deploying to individual customer sites, for customers who agree to an upgrade on tim
4. 94.▲
   by desc 8y ago

   This applies for languages which can do static type checks. In JavaScript, there's no assurance that the object you've got even means 'area' to be a number. It could be a string indicating which warehouse the Box is in.
5. 95.▲
   by desc 8y ago

   This feels incredibly broken to me. The 'how' should not change often, because it enforces rapid change on anything which depends upon it. Any system inevitably acquires dependencies. Maybe it's fine to break those dependenci
6. 96.▲
   by desc 8y ago

   No, this is not a good idea. Failures which are random are harder to diagnose. Something which works or not is much quicker to track down. The simple fact is that this sort of problem should've been dealt wiht a lot sooner, and a fai