2 ms·
> So, if you're going to have to rewrite your UI layer to disentangle it from your back-end anyway why not also bring it up to speed? So, if you're going to ha
by boomlinde 1mo ago
> So, if you're going to have to rewrite your UI layer to disentangle it from your back-end anyway why not also bring it up to speed?
So, if you're going to have to rewrite your back-end to disentangle it from your UI layer anyway why not also bring it up to speed?
- Sammi 1mo agoBecause they have 10 people working on it and they can't boil the ocean with that kinds of resources. If you try to do all the things at once, then you get nothing actually to the finish line. You'll be getting what you want in the next point release.
- boomlinde 1mo agoSo, as I said, a matter of priorities.
- TehCorwiz 1mo agoI don't think you understand the problem they were facing. If they rewrite the backend it would also REQUIRE rewriting the frontend because of how entangled they were. Whereas rewriting the frontend did not require changing the backend as dramatically. So their choices were: 1. Rewrite the whole thing, all at once, ship nothing for a long time. 2. Rewrite the frontend, ship changes incrementally, then move onto the backend once it's been excised from the tangled mess.