The response by Greg KH is also well worth reading:

https://lore.kernel.org/rust-for-linux/2025021954-flaccid-pucker-f7d9@gregkh/

No, it is not based on Gnome. It is a full DE environment written in rust.

So the story here is: A Russian asset tells a Russian narrative?

For reference: https://www.theguardian.com/us-news/2021/jan/29/trump-russia-asset-claims-former-kgb-spy-new-book

From their documentation

Unlike classic terminals, Warp requires you to sign up and log in to get started with the app.

So, yeah, it might be that people are not very impressed by a terminal that requires a cloud account.

But, if you don't type anything sensitive on to your terminal, like passwords and such, then you should be fine....

No, what you describe is called "Rent" or "Lease". People who press a "Buy" button and buy something, expect to own it. Words have a meaning, and trying to wiggle around this with fine print should be considered fraudulent.

Saudi Arabia felt Twitter was a problem, so they paid Elon to take it down in a way it wouldn't come back.

Well, for eggs, that are carbon based, you will in fact have problems since carbon doesn't have a liquid state at regular atmospheric pressure. I guess you can add pressure, but is that really what we mean when asking a question if something melt?

I guess this answeres my previous question about the lack of updates to the Intellij Rust plugin.

I'm happy to see that the maintainer listened to the users, so we got the best possible outcome.

The pricing is a bit much, especially compared to other services like Tutanota that actually runs servers and provides a service in addition to developing the applications. $20-$30 for the onetime purchase option would be more sane.

I know I bought Sync Pro for Reddit, but I know that was nowhere close to these prices.

EDIT: Found the Remove Ads option, and that is more reasonable priced.

But the author doesn't mention the most common way to pass named argument, so I include a comment from mjec over at lobster.rs that covers that (since I'm to lazy to write my own):

It’s not obvious to me why the author didn’t include direct instantiation of the struct, rather than a builder:

#[derive(Default)]
struct SearchOptions {
   pub include_inactive: bool,
   pub age_within: Option<(u32, u32)>,
   // ...
}

let result = search_users(
 users,
 SearchOptions {
   include_inactive: true,
   age_within: Some((5, 29)),
   ..Default::default()
 }
);

This avoids the need for boilerplate enums, or to filter through a vec in order to find the value of an argument. Every caller has to specify ..Default::default() but I don’t mind that! I like the idea that you have to explicitly acknowledge that you want everything else to be default values (and it might be useful to omit it in some places, so you get a compile error if new options are introduced).