Stacks: languages, frameworks, databases, interfaces, etc.?

[joelparkerhenderson]

Discuss ideas for implementation stacks, such as programming languages, application frameworks, databases and stores, application programming interfaces, etc.

Please read the stacks page.

Discuss programming languages and their frameworks such as:

• Popular tech e.g. React, Node, Ruby/Rails, C++
• Powerful tech e.g. Java, Kotlin, Clojure
• Progressive tech e.g. Ember, Elixir, Rust
• Mobile tech e.g. iOS, Android, React Native

Discuss databases such as:

• Relation-oriented e.g. MySQL, PostgreSQL, SQL Server
• Document-oriented e.g. Mongo
• Speed-oriented e.g. Redis, Memcached
• Graph-oriented e.g. Fauna, Neo4J
• Vendor-oriented e.g. Google Spanner, Amazon Aurora

Discuss application programming interfaces (APIs) such as:

• Resource-oriented e.g. REST-like
• Graph-oriented e.g. GraphQL-like
• Object-oriented e.g. RPC
• Wire-oriented e.g. protocol buffers, thrift
• Publishing-oriented e.g. RSS, Atom, Pub/Sub
• JSON-oriented e.g. JSON API, OpenAPI, LD
• Semantic-oriented e.g. RDF, SPARQL

Discuss platform areas such as:

• Mobile vs. desktop
• Phone size vs. tablet size vs. laptop size
• Distribution on Windows, Mac, Linux, iOS, Android, etc.
• Distribution via Apple App Store, Google Play, etc.

[prologic]

Rather than discuss specific implementation details; why don't we come up with a Design Specification for a Backend, Protocols and Frontends to implement. If we can come up with a suitable open spec design we can let the community at large build implementations rather than dictate technology stacks, languages, frameworks, etc.