Easy example of a basic method that has been unstable for a really long time: [T]::as_slice [0] since 2024 [1]. Apparently, stabilization was attempted earlier this year [2] but was then rolled back [3]. While clearly it was not yet ready for stabilization, it still took over a year before the first attempt.

Another one: Option::zip_with [4] since 2020 because nobody's figured out if it's worth having over .zip(...).map(...). Option::zip was actually stabilized [5] later in 2020 but Option::zip_with has since been sitting in limbo for over five years.

Another one: <*const [T]>::as_ptr also since 2020 [6]. I can't remember if there's an alternative now but dealing with slice pointers without relying on unstable methods has historically been very difficult/annoying. I ran into a bunch of this kinda stuff while working on a crate for iterating over rows/columns of image buffer subregions, because I wanted to use and support slice pointers. (Specifically I think getting the length of the slice pointer was nearly impossible without invoking UB, because constructing a reference (which was the only safe way to access a len method) could break aliasing rules. However I think the len method on slice pointers was stabilized a while ago so that particular problem is no more.) Speaking of which, <*mut [T]>::split_at_mut has been unstable since 2022 [7]...

I'm not saying there's no reason for any of this, just that as a Rust developer it's been frustrating. There are enough of these all over the place that it feels like a real occurring problem, even if it's not reasonable to expect a volunteer open-source project to pay full attention to everything ever.

[0]: https://doc.rust-lang.org/std/primitive.slice.html#method.as...

[1]: https://github.com/rust-lang/rust/issues/130366

[2]: https://github.com/rust-lang/rust/pull/151603

[3]: https://github.com/rust-lang/rust/pull/152963

[4]: https://github.com/rust-lang/rust/issues/70086

[5]: https://github.com/rust-lang/rust/pull/72938

[6]: https://github.com/rust-lang/rust/issues/74265

[7]: https://github.com/rust-lang/rust/issues/95595

> Can't you tell it to use stable as the default target, and use nightly manually in cargo?

Are you saying it doesn't suggest unstable features when using a stable toolchain? That was not my experience before I started using nightly.

I most often encounter unstable features when I reach for a basic common-sense utility method and discover that it's not stable. Like just earlier today I would have reached for bool::toggle which not only is unstable, but is also newly added as of like a month ago! but some unstable methods have been sitting around for years.

And now that IntelliJ-Rust is proprietary, I can't even make a feature request anymore for the ability to exclude unstable features from the autocomplete. So they will taunt me forever, perfect little helpers just locked away.

oh man, imagine telling them "you don't want people like me breaking into your app! Just look at how I got into this call!"

AFAICT it has not changed.

Now, say I buy a MacBook Pro, and compromise on just a few things I didn't like, but that don't critically impact usability. I mean things like full-size function keys, or only 3 Thunderbolt ports (only one on the right!), small stuff. I don't feel especially limited by speed or memory capacity nowadays (although memory bandwidth is still about an order of magnitude off for local LLMs).

I'm still upset that it won't play games, but at least a capture card lets me pass through my Windows machine, and I heard Nvidia support in SteamOS might happen in the next year or two. Maybe Asahi might also grow to support my hardware before it expires (unlikely but possible)

- People who crave validation seek good looks. They want to be accepted.

- People who crave status seek good looks. They want to be awarded.

- People who crave admiration seek good looks. They want to be desired.

There are so, so many more possible reasons and motivations, and it highly depends on the individual. Someone could have all of the above or none of the above and still obsess over looks. Someone could obsess for different reasons in different contexts or with different moods.

It's not based on some infantile monkey-see-monkey-do obsession with media.

Also it's quite rude of you to dismiss an entire generation with this belittling rhetoric. Mental health is a really, really big deal.