Date: Mon, 27 Oct 2025 19:47:58 +0200
As it's still an MVP in C++26, the key decision to make for now is whether
to use contracts at all. It's not that unfortunate having to wait 3 more
years for a riper product if the 1st *minimal* edition doesn't yet fit your
use cases. Some of us though will be able to use them, and we should be
allowed to.
I should have made an effort to come up with some proper pun for you
calling over two decades of contract work (including half a decade of SG21)
"as fast as possible", but I know I'm no match for your linguistic
skills. 😉
On Mon, Oct 27, 2025 at 7:38 PM Ville Voutilainen <
ville.voutilainen_at_[hidden]> wrote:
> On Mon, 27 Oct 2025 at 19:31, Andrei Zissu <andrziss_at_[hidden]> wrote:
> >
> > And how does having no contracts at all for at least 3 more years help
> you gain that missing functionality earlier than the current expectation?
>
> It doesn't. The goal isn't to get some functionality as fast as
> possible, but to get cohesive and correct functionality so that we
> don't run into
> a situation where programmers have unfortunate choices to make, and
> then some need to deal with the support, review, policy and product
> management consequences of those choices.
>
to use contracts at all. It's not that unfortunate having to wait 3 more
years for a riper product if the 1st *minimal* edition doesn't yet fit your
use cases. Some of us though will be able to use them, and we should be
allowed to.
I should have made an effort to come up with some proper pun for you
calling over two decades of contract work (including half a decade of SG21)
"as fast as possible", but I know I'm no match for your linguistic
skills. 😉
On Mon, Oct 27, 2025 at 7:38 PM Ville Voutilainen <
ville.voutilainen_at_[hidden]> wrote:
> On Mon, 27 Oct 2025 at 19:31, Andrei Zissu <andrziss_at_[hidden]> wrote:
> >
> > And how does having no contracts at all for at least 3 more years help
> you gain that missing functionality earlier than the current expectation?
>
> It doesn't. The goal isn't to get some functionality as fast as
> possible, but to get cohesive and correct functionality so that we
> don't run into
> a situation where programmers have unfortunate choices to make, and
> then some need to deal with the support, review, policy and product
> management consequences of those choices.
>
Received on 2025-10-27 17:48:11
