bloom VS Clippy

Static linking is remarkably easy: Creating small Docker images is a delight.

As a data point, I've served millions of HTTP requests using it, without problems.

For larger projects, I think that actix-web is the incontestable winner. That's why it's my choice for Bloom.

For me the worst part was not the job itself (I did ML related stuff) but the environment (commuting, artificial light all day long...).

Since I moved to the entrepreneurship track I'm way more happy. At first it doesn't pay so you need to have savings, but after some time (depends of the person) you start making a living and you can decide on what to work on.

Today, half of my time is dedicated to writing software that I genuinely believe have a positive impact on the world (https://github.com/skerkour/bloom), and half of my time is dedicated to writing and sharing (I'm writing a book).

The best thing that I've understood is that even if my primary skills are programming and architecture related stuff, it doesn't mean I have to code for a living. There are a lot of jobs related to programming that you can switch to.

Hi, I'm not a video game programmer, I mostly do network and web programming, but I do exactly this in Rust and it works very well. Here is an example for a mailer driver, which is a trait and then implemented for multiple "backends" such as AWS SES or SMTP https://github.com/skerkour/bloom/blob/main/bloom/kernel/src/drivers/mailer/mod.rs.

What do you think about degoogle project open source => https://bloom.sh/ " The simplest way to de-Google your life and business: Inbox, Calendar, Files, Contacts & much more ".

What do you think about degoogle project open source => bloom.sh " The simplest way to de-Google your life and business: Inbox, Calendar, Files, Contacts & much more ".

I couldn't find it in the API guidelines either. From what I understand, the idea is that any trait bounds, which includes generic type parameter bounds and lifetime bound on a type (struct or enum) would be repeated back in the impl block

there is a nice discussion on this issue here: https://github.com/rust-lang/rust-clippy/issues/1689

You should not blindly follow clippy lints. They are sometimes wrong. Another example https://github.com/rust-lang/rust-clippy/issues/9782 .

I often write () = f() to assert that f() is unit. Unfortunately clippy warns on such code ( https://github.com/rust-lang/rust-clippy/issues/9048 ). There are very recent pull requests for this bug, so hopefully this bug will be fixed very soon. But meanwhile I invented this workaround: [()] = [f()] :)

Apart from running clippy on many projects being essential, clippy is also an exceptionally welcoming project, no matter your prior knowledge.

clippy is a great place to get started :) though it isn't exactly new.

clippy is also pretty compiler-adjacent and unlike rust-analyzer uses rustc's internal APIs. Don't let the size of the code base scare you off! It's actually feasible for a newcomer to contribute even such a substantial change as a new lint, and we have issues labeled as "good first issue" that come with mentorship, so you don't need to go it alone.

Yes, you could use it to write a lint. Although you might find it easier to just fork Clippy and add your own lints to their existing framework.

Check out the readme for more information.

They are two of my favorite Rust tools. If you haven’t tried them yet, I highly recommend giving them a try. Clippy can detect various lints in your code and guide you towards writing more idiomatic code. To install Clippy, simply run rustup component add clippy, and to run it within your workspace, execute cargo clippy. For more details, visit Clippy’s GitHub repository.