Bureaucrats, developer, Administrators
9,842
edits
No edit summary |
|||
(5 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
'''Software requirements''' are so constrained by [[hardware requirements]] and [[ | '''Software requirements''' are so constrained by [[hardware requirements]], [[protocol requirements]] and (especially) [[performance requirements]] that we should avoid choosing any [[programming language]], production [[wiki code]] or even [[chat code]] until the whole [[healthy buying infrastructure]] is much better understood. This starts by understanding the [[healthy signal infrastructure]] and its low tolerance for [[e-waste]] or [[volunteer labour]]. | ||
Some questions to keep in mind as these concepts evolve: | |||
*[[audio]] vs. [[video]] as primary presentation of [[Consumerium buying signal]] | |||
:Text is the default still | |||
*[[Python]] vs. [[Java]] - consider [[mobile device]] and [[wiki code]] issues | |||
*[[response time]] - is [[HTTP]] an acceptable protocol for our purposes? If not, can some similar [[REST]] protocol be developed that will be? | |||
*[[PHP]] - useful tool or slow script-kiddie fluff? | |||
[[Category:Technology]] |