Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
darker
Apply black reformatting to Python files only in regions changed since a given commit. For a practical usage example, see the blog post at https://dev.to/akaihola/improving-python-code-incrementally-3f7a
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Prettier Rust supports it! https://github.com/jinxdash/prettier-plugin-rust
I’m not sure they are? I don’t mean this to criticize anybody on the project — I’m sure they have other things going on — but there are a whole bunch of open PRs without even a single comment.
Backwards compatibility. Many of us want to enforce styling in CI and that means it can't change, see https://github.com/rust-lang/rfcs/pull/3338
For Python, Darker does that by applying Black only to changed areas of the code. Maybe the same approach could be used for rustfmt by creating a separate tool?
Instead, what I'm talking about is that there is a (generally large) cost to contributions that maintainers have to pay. Rarely is a contribution merge-ready on the first pass. Instead, a maintainer has to work with the person to get it ready. The amount this is needed varies according to the needs of a project. People generally underestimate the complexity of a project their are contributing to. Take cargo build --dependencies-only which people want for docker caching. Frequently people bump the thread, thinking its trivial, saying how to resolve it, and are annoyed that it isn't solved. Thankfully one person stepped back and looked at the bigger picture, realized what the maintainers were trying to say, and wrote up a great report on what the challenge is. Similar for XDG support. Each iteration for each PR is also represents a context switch for the maintainer. Keeping up on all of this across all of their projects, especially when its spare time, means they also need to come back up to speed on this each time.