https://github.com/thunderbird/thundercell
Forging only the strongest thunder
https://github.com/thunderbird/thundercell
Last synced: 12 months ago
JSON representation
Forging only the strongest thunder
- Host: GitHub
- URL: https://github.com/thunderbird/thundercell
- Owner: thunderbird
- License: mpl-2.0
- Created: 2023-06-15T08:58:46.000Z (almost 3 years ago)
- Default Branch: main
- Last Pushed: 2024-02-29T17:31:10.000Z (over 2 years ago)
- Last Synced: 2024-05-02T04:24:14.015Z (about 2 years ago)
- Language: Rust
- Size: 142 KB
- Stars: 12
- Watchers: 10
- Forks: 0
- Open Issues: 4
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Thundercell
Staging repository to assist the backend team with discovery, prototyping and documenting future
efforts to replace aging components.
Feel free to use namespaced directories within this project to carry out PoC / scoping work.
We will soon use issues and projects for meta-tracking before migrating approved works back
to Bugzilla (in a fully fleshed form)
Here, we forge only the strongest thunder.
## Oxidization
Where possible, we should look to Rust for replacement components to ensure memory safety and performance in the backend. This is especially important for critical components such as:
- protocols
- databases
- OS/system integration
## Planning ..
This repository provides a shared playground in which the entire team can experiment with and refine ideas before we commit resources to them, so we should keep the following mantra in mind:
> The backend sets the constraints, but the frontend sets the requirements.
As we begin to replace legacy components, we shouldn't limit ourselves exclusively to drop-in replacements. Instead, find out where the old ones went wrong and how we can make life easier (and thus more maintainable) for those making use of the features!