User talk:Daniel Kinzler (WMDE)/FauxRequest
Add topicLatest comment: 8 years ago by Anomie in topic "All functionality will be exposed via the web API" as a pro
| This page used the Structured Discussions extension to give structured discussions. It has since been converted to wikitext, so the content and history here are only an approximation of what was actually displayed at the time these comments were made. |
Production code
[edit]Using FauxRequest in Production code may be acceptable as a short term solution, but should be considered tech debt that needs to be addressed in a timely manner.
IMO change "Production" to "prototype". I know we already have a long history of prototypes becoming deployed as production solutions, but we shouldn't encourage that. Anomie (talk) 19:29, 18 July 2017 (UTC)
- The idea is not to encourage that. But people argue that there are advantages to using this in production, so I thought it fair to record them - and rebut them in the discussion section. We'll need to find someone else to argue in their favor, and rebut the con arguments ;) Daniel Kinzler (WMDE) (talk) 18:22, 24 July 2017 (UTC)
- But this is in the "conclusion" section. Anomie (talk) 19:20, 24 July 2017 (UTC)
"All functionality will be exposed via the web API" as a pro
[edit]While true, there's little guarantee that the functionality will be exposed in a manner that's useful for anything except the specific use case the person was writing for. If you're cutting corners on architecture, aren't you likely to cut corners when designing an API too? Anomie (talk) 19:33, 24 July 2017 (UTC)