One solution: normalize your abstractions so they're the same, but a bit awkward, on both sides. This is where isomorphic code takes you.
-
-
Replying to @sarahmei
Another solution, though, is to accept the differences and use abstractions in each environment that are the most appropriate.
1 reply 3 retweets 7 likes -
Replying to @sarahmei
To be sure, this makes moving between the environments more difficult, whether it's Ruby on one side and JS on the other, or JS on both.
1 reply 2 retweets 2 likes -
Replying to @sarahmei
However, it lets you use the abstractions that make sense, and ultimately leads to better, easier-to-understand code on both sides.
1 reply 1 retweet 3 likes -
Replying to @sarahmei
The more teams I see try for isomorphism, the more I suspect it's a phantom.
2 replies 5 retweets 9 likes -
Replying to @sarahmei
Isomorphism is an illusion, born of insufficient understanding of "the other side."
2 replies 22 retweets 25 likes -
Replying to @sarahmei
Giving up on isomorphism is painful but lets us, also, separate the schedules for front- and back-end changes.
7 replies 5 retweets 7 likes
@sarahmei Totally meant JMS there. Also for reference https://youtu.be/UlMpIHH1K5s at around 40m :)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.