Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in or
create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
| Latest revision |
Your text |
| Line 1: |
Line 1: |
| '''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]]. | | '''Software requirements''' are so constrained by [[hardware requirements]] and [[protocol requirements]] that we should avoid choosing [[wiki code]] or even [[chat code]] until the whole [[healthy buying infrastructure]] is much better understood. This starts by understanding the [[healthy signal infrastructure]]. |
| | |
| 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]]
| |