4 ms·
Finally had the opportunity to use Rails after not liking fat frameworks for over 10 years and kept using my own framework instead and learnt I never actually n
by h1d 8y ago
Finally had the opportunity to use Rails after not liking fat frameworks for over 10 years and kept using my own framework instead and learnt I never actually needed it.
It attracts non decent programmers and code is usually not great when you inherit a project which causes performance issues later on and things in Rails are just odd.
Variables and methods are predefined with unnecessary English plural/singular rules which you can't tell if it's a variable/method defined by the local developer or done by rails and had to google so much to know how to use it when that knowledge is completely useless once I leave Rails.
Always better to learn the actual underlying tech like SQL.
- schappim 8y agoI have to say I had the exact opposite (with the exception of performance). After 10 years as a Ruby developer I had resisted working w/ Rails (always opting to use Sinatra). This year I embraced Rails for a large project and I'm kicking myself for not doing it sooner. The documentation is great and the speed at which you can knock out features is second to none.