Re: Should the specs be forked and maintained elsewhere? from Ryan B on 2023-03-24 (public-swicg@w3.org from March 2023)

From: Ryan B <w3c@ryanb.org>
Date: Fri, 24 Mar 2023 09:29:29 -0700
To: Melvin Carvalho <melvincarvalho@gmail.com>
Cc: aaronngray@gmail.com, Benjamin Goering <ben@bengo.co>, a <a@trwnh.com>, Bob Wyman <bob@wyman.us>, Jacky Alcine <yo@jacky.wtf>, public-swicg@w3.org, Dmitri Zagidulin <dzagidulin@gmail.com>, Aaron Parecki <aaron@parecki.com>
Message-ID: <CA+caGh9nHzG_a68wW+TiOJ2hms=J=Y09v5hoMdYf2JaqpHYL0w@mail.gmail.com>

On Fri, Mar 24, 2023 at 9:18 AM Melvin Carvalho <melvincarvalho@gmail.com>
wrote:

>
> We used "content negotiation" in Solid, and unfortunately, it has been a
> source of bugs for me. In my opinion, it was a non optimal design decision
> that added a lot of complexity.
>

Strong +1. Content negotiation is the classic example of an idea that
sounds good in theory but turns out to be net harmful in practice, for at
least the vast majority of implementors, even if not necessarily all.

Received on Friday, 24 March 2023 16:32:43 UTC