4 ms·
The worst thing about rails these days is ruby itself. If I'm going to use a non type-safe language, I may as well use the one that's on the client side as wel
by kaonashi 11y ago
The worst thing about rails these days is ruby itself. If I'm going to use a non type-safe language, I may as well use the one that's on the client side as well (and has first class functions).
- mattmcknight 11y agoRuby procs are first class.
- jrometty 11y agovery functional
- rimantas 11y agoAnd then you discover that Ruby was not so bad after all. With blocks and procs I doubt many miss those first class functions that much.
- pekk 11y agoType safety does not mean static typing.
- kaonashi 11y agoAre you trying to make the case that ruby is type-safe?