Re:Rewrite It in Rails
by bubblyworld on Saturday November 02, 2024 @02:54AM
(#42024531)
A little gem of an article, thanks for posting. It's nice to see a pragmatic take on rewriting for a change. Feels like a good primer to read before considering a rewrite myself haha
Regarding rewrites, I'd love to have my code in such a shape that I could just copy over the business logic, maybe even put it into an independent library. The rest is just a user/api interface after all.
Re:Rewrite It in Rails
by probablybetter on Sunday November 03, 2024 @09:30PM
(#42037872)
i saw that... (gem, ruby... hahhaha)
When people nag about frameworks I usually think that have their “perfect” world idea they don’t want compromise. Lots of times it is not having full understanding of the framework and why’s.
But it is much more efficient working with the framework, knowing its limitations. Just spending time really understanding tools one work with.
Yes this was indeed the most important thing for me to realize. I am now much happier, not constantly thinking "if only I had Rust enums!"
For context that came after trying this:
> Meanwhile, I started building "version 2" of the application. I chose Rust as the language for the backend and SvelteKit for the frontend.
Since it started out as Rails in v1, the post is to beware abandoning a framework that's working for you.
Also try other languages for yourself and see if they are indeed as good as you think they might be. Or you might never realize that the grass isn't necessarily always greener on the other side. Unfortunately not everyone will have time to do that for longer than a couple of hours or days.
>> Interestingly, all of the things that used to annoy me about Ruby and Rails now annoy me much, much, much less. I have accepted that there is no perfect language or framework. You just have to know its strengths and weaknesses and deal with them.