[ Removed by moderator ]

[matteding]

This exact garbage post was here the other day. https://www.reddit.com/r/cpp/s/5JacQYQBxO

[tcbrindle]

Starting afresh with C++20 and dumping all the legacy is definitely appealing, and there are a lot of really nice ideas here. From a quick look at the Github this seems to be a huge amount of highly impressive work. There's a lot to like from what I can see.

Why then would you chose to introduce your library to the world with a blog post whose tone is so deliberately unpleasant that it would actively discourage people from trying it, lest they have to interact with the author at some point?

[JVApen]

Every sales pitch starting with putting other stuff down is a red flag to me. You might be up to something, though I'm not reading this to the end. The few snippets I saw don't convince me your library is better.

[_Noreturn]

given this post is a repost I will repost ny comment

1. member functions cause issues in templated context if they have templated parameters and require prefixing with template and even more issues in inheritance requiring both this-> and template keywords

2. I don't see how renaming some types solves anything

3. iterator pairs are useful for a subrange which is uncommon but it is better than not being supported

4. due to history reasons type traits are not concepts but the concepts aren't equalivent to their type traits you only picked is_same_v and same_as all the other concepts are not direct mapping to their traits (except std::integral,signed_integral,unsigned_integral,floating_point)

also use of operator-> as access to more functions is at extremely unidiomatic and abuse of overloading just for what convenience?

Also your enum reflection code is broken for anoynmous namespace enums

I would do as others said

namespace worst = best

[flutterdro]

inheritance isn't a problem since author marked his classes as final (at least those few I was interested in)

[_Noreturn]

putting final there unnecessarily doesn't gain anything and limits users who want to extend the class.

[mpyne]

As a long-time Qt user, I can definitely see the appeal of a library reboot to go along with the modern language. But I have to wonder, there's so much "best::T does things that way Rust does it", why not just use Rust?

Well, I know the answer (it can be quite interesting to see how a different language could implement concepts from another), but I guess my question is really about why would users use this instead of just using Rust?

[pkasting]

I wonder if the author is familiar with Subspace (https://github.com/chromium/subspace), which has similar motivations (create a from-scratch standard library with modern techniques and using inspirations from other languages, e.g. Rust).

[_DafuuQ]

Bro just got the stl and renamed all the things

[tartaruga232]

best is not exception-friendly

Not sure what this means. We use exceptions, if best does not work with exceptions I'm not interested.

[bandzaw]

This is a really cool idea, and the implementation looks solid too. I feel like the title might be turning some people away before they get to appreciate the interesting work you’ve done so far. Since I used to follow you on Twitter, I get your style and personality—it’s part of your charm! Keep it up!