Timeline for New frontend for legacy code
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 2, 2021 at 14:17 | comment | added | Greg Burghardt | Related: I've inherited 200K lines of spaghetti code — what now?. | |
| Mar 2, 2021 at 14:15 | comment | added | Doc Brown | If both frontends will be required for controlling backend functionality which must be identical, and both will be maintained over years, you definitely don't want to maintain two code bases for two backends with heavily overlapping functionality. Situation could be different if the new backend would sooner or later replace the old one, but I guess that's not realistic. | |
| Mar 2, 2021 at 13:36 | comment | added | emajl | @DocBrown Yes, it has. The dream is to replace it with the mobile version. But for now, it will only be used for the most important features so they can be used on mobiles. But they would at least be runned in parallel for some years because it will take that much time to migrate over all the features. | |
| Mar 2, 2021 at 13:28 | comment | added | Doc Brown | So the old application has already a frontend. What is the intention with this - to replace it fully by the mobile version, or to keep the mobile and non-mobile versions both alive in parallel? | |
| Mar 2, 2021 at 13:26 | history | edited | Doc Brown | CC BY-SA 4.0 |
Formatting improved, numbers added for making referencing possible
|
| Mar 2, 2021 at 13:18 | review | Close votes | |||
| Mar 20, 2021 at 3:06 | |||||
| Mar 2, 2021 at 13:14 | answer | added | f222 | timeline score: 7 | |
| Mar 2, 2021 at 12:59 | comment | added | Philip Kendall | I don't think anyone outside your company can answer this question for you, only people close to the code can weigh up and advantages and disadvantages of each approach. | |
| Mar 2, 2021 at 12:42 | history | asked | emajl | CC BY-SA 4.0 |