|
1 year ago | |
---|---|---|
dpetalc | 1 year ago | |
.gitignore | 1 year ago | |
.gitmodules | 1 year ago | |
README.md | 2 years ago | |
any.md | 2 years ago | |
designing.md | 2 years ago | |
dlang.md | 1 year ago | |
ecosystem.md | 2 years ago | |
genlogo.d | 1 year ago | |
metaprogramming.md | 1 year ago | |
openquestions.md | 2 years ago | |
organization.md | 2 years ago | |
petal.md | 2 years ago | |
petal.svg | 2 years ago | |
platforms.md | 2 years ago | |
ponderings.md | 2 years ago | |
style.md | 1 year ago | |
typesystem.md | 1 year ago |
For developing core libraries, OS kernels, or distributed lock stores scaling to a thousand requests a second, you want something with no overhead.
Let’s face it, most of the code we write is regular applications running at human scales in human time. We want to get something that works, fast. And we’d like something that works fast.
That’s where Petal comes in.