Live data from Hacker News

How We Replaced React with Phoenix

robots.thoughtbot.com

1–10 of 11 posts

Re: How We Replaced React with Phoenix

#2
Not to bust on what they're doing, but it seems like React may not have been the best initial choice. However, it seems like the investment time aspect means the chance of learning is worth more than the "best tool" aspect.

I like that they were able to admit to not doing something the best way and then shared how they made it better. It makes me more curious to try out Phoenix as well.

Re: How We Replaced React with Phoenix

#9

Earlier quoted context omitted.

I always sprinkle my JavaScript

But how do you decide to stop sprinkling your JavaScript and go full blow React (serious question)?

When "sprinkling Javascript" turns into "making sauce for the spaghetti you've been cooking", it's probably time to consider React or something similar.

Re: How We Replaced React with Phoenix

#10

So a blog post complaining... about using the wrong tool for the job. So next post will be... "How We Replaced Phoenix with Rails".

> wrong tool for the job

> "...Phoenix with Rails"

Isn't Phoenix designed to be like Rails and do things Rails does? That'd make them pretty similar (though not the same, of course) tools.

Post reply on HN