This tag identifies tasks where architectural decisions must be made.
Details
Aug 4 2024
Jan 27 2017
Jan 6 2017
Aug 24 2016
We'll start with inline JSON and we'll advise when new formats pop. JSON is more and more universal.
Aug 19 2016
Aug 18 2016
JSON makes a lot of sense, there is no need to parse twice a JSON payload, once for our notification format, once for the source payload.
Aug 17 2016
Feb 14 2016
Dec 11 2015
Dec 10 2015
Le llvm style guide, c'est un style guide pour c++ par pour le c ?
Dec 9 2015
Where is the llvm C code style guide ?
For the remaining, we should also document an cross-languages set of recommendations, at least for C family.
Adding people having write some code in C in their life as bug CCs.
Nov 30 2015
Note: I'm only going to speak about the front-end, as the fact we code the back-end in Node.js or in Python doesn't matter a lot to this question.
About the browser stack, two questions (more or less related)
- Does a framework bring a lot comparing to vanilla javascript for the use ?
- Which browser we intend to support. A good target would be in my opinion Grade A support by mediawiki
Apr 8 2015
Mar 31 2015
List of (front-end) JS frameworks to consider
Mar 30 2015
If we don't rely on a PHP back-end, let's go for Django. For easy JS manipulation of .svg files, we should try and see if raphael.js suits our needs.