Re:From Rails to Clojure, Then to Java, Then Back to Rails
by NegativeLatency on Wednesday March 21, 2018 @03:59PM
(#16641768)
I think there's a valid case to be made that Spring and the rails auto-loader are pretty annoying/stupid in larger projects (or anytime you're going against the grain).
Every framework has its downsides. Personally I think rails is nice (I am very productive with it).
Re:From Rails to Clojure, Then to Java, Then Back to Rails
by kureikain on Wednesday March 21, 2018 @04:14PM
(#16641924)
This is a fair point.
Yes, I come into lots of issue with Spring autoloader to the point I have a zsh alias call `kill_rails` to make sure it kills all the rails and spring instances :(.
That's being said, Spring is an external tool to help solve the slowness of booting up Rails app. I have work in Java/Python and they are slow to bootup too just depend on how big the project is.
Tool like: https://github.com/Shopify/bootsnap help to speed up this as well.
Other option to look at: https://github.com/danielpclark/faster_path
These solves the issue of scanning path, address slowness in a different way compare to preload mechanism of Spring.
Re:From Rails to Clojure, Then to Java, Then Back to Rails
by mtarnovan on Friday March 23, 2018 @09:26AM
(#16657816)
GP was talking about this Spring: https://spring.io/ not the Rails preloader...
Re:From Rails to Clojure, Then to Java, Then Back to Rails
by jcadam on Friday March 23, 2018 @10:03AM
(#16658235)
Yes, I meant the Java uberframework beloved by architecture astronauts. I suppose I should have been more clear - I haven't uses RoR since version 3, so my knowledge of that ecosystem isn't very current :)
I have used and deploy Go/Elixir/Clojure to some certain success. One thing I feel is that no code is as beautiful as Ruby code to my own eye.
What make Rails bad in your opinion? Is its performance? I think Rails is just a framework with many utility/helper to help you out.