Or, to put it another way: success looks like yet another "got the
defaults wrong", where people should default to B2 unless they need B1,
and "pure" joins the ranks of "final" and "private" of "I shoulda been
the default."
Right, that's what you're saying?
On 11/22/2021 4:07 PM, Kevin Bourrillion wrote:
On Mon, Nov 22, 2021 at 6:27 AM Dan Heidinga <heidi...@redhat.com> wrote:
I'll echo Brian's comment that I'd like to understand Kevin's use
cases better to see if there's something we're missing in the design /
a major use case that isn't being addressed that will cause useer
confusion / pain.
Sorry if I threw another wrench here!
What I'm raising is only the wish that users can reasonably /default/
to B2-over-B1 unless their use case requires something on our list of
"only B1 does this". And that list can be however long it needs to be,
just hopefully no longer. That's probably how we were looking at it
already.
And sure, "need" sometimes can mean "it would have made translation
/way too/ complex and clever". Even if all we can say is "in principle
this /could/ be supported, but it just isn't and click here if you
/really care a lot/ to know the reasons why", it works and I suspect
most users wouldn't even click.
Does that make perfect sense? Again, the thread just backed into the
topic sideways.
--
Kevin Bourrillion | Java Librarian | Google, Inc. |kev...@google.com
