On Fri, 28 Nov 2025 at 08:12, Simon Schröder via Std-Proposals
<std-proposals_at_[hidden]> wrote:
>
> Standardization is not engineering. Standardization is tedious and boring (for most people). If you are looking for a fun hobby, this is not for you. It could be a fun hobby to write about these ideas in a blog post (like a lot of people do).
>
> Just because you *can* implement something does not mean it *should* be in the standard. If you want to propose something it is your job to 1) motivate the proposal, 2) show how it is useful, 3) explain how it will improve a lot of code, and 4) how it will affect other parts of the standard. It would then be sufficient to state that there is an implementation. It would be much better if the implementation had been in real use for a couple of years to figure out all the things that are wrong with it. Or alternatively you don’t need an implementation if you can point at the same feature in another language.
>
> An implementation by itself is useless. Standardization is not engineering. Standardization of the C++ library mostly standardizes common behavior, i.e. something that is used in real code bases.

Oh, standardization is very much engineering. But cobbling up a
prototype implementation of what-ever and not documenting what the
idea behind
it is is not.