3 ms·
> shorter Yes, until the very first time you'd want to reuse some of the code. From then on, any initial advantage is melting into unmaintainable mess of semi-
by jablan 7y ago
> shorter
Yes, until the very first time you'd want to reuse some of the code. From then on, any initial advantage is melting into unmaintainable mess of semi-imperative, semi-declarative copy-paste horror.
- ruslan_talpa 7y agoreuse code where? In the db, why couldn't you? Or do you mean to reuse the logic in the db in some other place? By this logic one can say "ruby is bad becasue i can't reuse logic i wrote for the backend in my frontend SPA". This is the type of (data logic) that you should not need to reuse in other parts. Maybe this comment does a better job of explaing the architecture https://news.ycombinator.com/item?id=21436425 https://news.ycombinator.com/item?id=21436425