This repository offers practical guidelines for selecting technology stacks across both prototype and production stages.
It spans multiple languages and environments, highlighting their strengths, limitations, and recommended use cases.
This guide is rooted in a research‑driven methodology, where programming serves as a tool to explore the problem space.
Unlike conventional industry workflows that move directly from requirements to implementation, this approach introduces an additional modeling phase before prototyping.
The modeling stage acts as a filter: it helps identify unsuitable directions early, ensuring that only viable problems advance to prototype and eventually to production.
By design, the guide emphasizes both prototype and production stages, reflecting a workflow that balances the rigor of research with the pragmatism of engineering.
- README.md — Project overview and quick reference.
- docs/guide.md — Guide in English (formal technical style).
- docs/guide-zh.md — Guide in Chinese (original notes).
- Models
- Prototypes
- Production Systems
- POSIX sh
- Perl / Python / Ruby
- OCaml / Rust
- Java / C#
- JavaScript
- PHP
- F#
- Dart
- C / C++
- Go (Golang)
This guide is intended for open‑source projects in general.
It focuses on technology stack choices across different stages:
- Modeling stage — abstract exploration and problem filtering
- Prototype stage — fast iteration and concept validation
- Production stage — long‑term stability and maintainability
- Specific deployment environments — browser, content sites, enterprise, mobile
- Legacy projects — maintenance and migration strategies
Contributions are welcome.
Please open an Issue or Pull Request, and follow the style and structure in docs/guide.md.
© 2026 ByteBard
Licensed under the Creative Commons Attribution 4.0 International License.