spec
sonyflake-rs
| spec | sonyflake-rs | |
|---|---|---|
| 9 | 2 | |
| 7,629 | 157 | |
| 0.2% | - | |
| 6.2 | 4.5 | |
| 4 months ago | 29 days ago | |
| Rust | ||
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
spec
-
What's the status of Open Application Model?
There was recently score.dev, but that is also just used by one tool.
- One YAML to rule them all
-
Best events/conferences to participate for an open-source project?
Yesterday I was thinking about the roadmap and the discussions that are happening in the community (you can check them here and feel free to open one or contribute to an active one) and I am excited to see how much we have to look forward in 2023.
-
Thoughts on my new OSS tool launch + twitter space happening today
A month ago we open sourced Score. The community response has been really great so far (just over 1k stars in 4 weeks) and we got many questions thrown at us:
-
One YAML to rule them all!
Hi all, I am Giulia, Community Manager and part of the team that launched Score.dev a week ago. My team and I believe that developers shouldnât fight with tooling and advocate for a workload-centric approach to development. Weâre on a mission to reduce cognitive load on developers, minimize configuration drift and mismanagement, and improve the developer experience. Want to join us as a contributor? Read the official announcement to learn more. Or check us out on GitHub!
- One YAML to rule them all. We just open sourced a new workload config spec so you can configure once and deploy to any environment (local, cloud, etc.)
-
The pros and cons of managing configuration for multiple environments
Last week we released score-spec and I asked a few communities for feedback on how you manage configuration between multiple environments and a lot of you (thanks!) came up with some answers and more questions. Here I wanted to list the pros and cons, in my humble opinion, of the top approaches suggested. Feel free to add yours as well!
- Trouble with consistent config across environments?
sonyflake-rs
What are some alternatives?
kuuid - K-sortable UUID - roughly time-sortable unique id generator
ksuid - K-Sortable Globally Unique IDs
ulid - Universally Unique Lexicographically Sortable Identifier (ULID) in Python 3
autocxx - Tool for safe ergonomic Rust/C++ interop driven from existing C++ headers
dynamodb-onetable - DynamoDB access and management for one table designs with NodeJS
schemafy - Crate for generating rust types from a json schema
python-ksuid - A pure-Python KSUID implementation
futures-batch - An adapter for futures, which chunks up elements and flushes them after a timeout â or when the buffer is full. (Formerly known as tokio-batch.)
uuid6-ietf-draft - Next Generation UUID Formats
logos - Create ridiculously fast Lexers
ulid-lite - Generate unique, yet sortable identifiers
serde-plain - A serde serializer that serializes a subset of types into plain strings