Re:Building Modular Rails Applications: A Deep Dive into Rai...
by henning on Monday July 14, 2025 @11:56AM
(#44561668)
This blog post just shows how libraries and frameworks often solve one problem but create another. This leads to the emission of ridiculous sentences like `One of the trickiest aspects of building engines is handling routing correctly` which would be a non-issue if you just wrote simple code to solve the problem in front of you instead of doing a bunch of "modular" "engine" framework-y compiler-y nonsense that adds boatloads of complexity just to accomplish one basic thing like handling file uploads.
[ Parent
| on HN ]
Re:Building Modular Rails Applications: A Deep Dive into Rai...
by adenta on Monday July 14, 2025 @11:58AM
(#44561686)
What problem was created?
Re:Building Modular Rails Applications: A Deep Dive into Rai...
by pqdbr on Monday July 14, 2025 @02:11PM
(#44563362)
"one basic thing like handling file uploads" - say no more.
Actually, the article isn't even about handling file uploads - it's about deliberately creating a modular admin panel for dealing with file uploads.
It's not modularity for "framework-y" sake, but to easily deploy that admin panel in other applications with literally a one-liner.
Re:Building Modular Rails Applications: A Deep Dive into Rai...
by giovapanasiti on Monday July 14, 2025 @02:23PM
(#44563529)
I couldn't have written this comment better myself. Thank you this is exactly the point