Tarantool development patches archive
 help / color / mirror / Atom feed
From: Konstantin Osipov <kostja.osipov@gmail.com>
To: Kirill Yukhin <kyukhin@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org,
	Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Subject: Re: [Tarantool-patches] [PATCH] box: remove unicode_ci for functions
Date: Mon, 9 Dec 2019 16:39:55 +0300	[thread overview]
Message-ID: <20191209133955.GA8196@atlas> (raw)
In-Reply-To: <20191209132555.qn25wsxoa5lr4252@tarantool.org>

* Kirill Yukhin <kyukhin@tarantool.org> [19/12/09 16:28]:
> > Who is "we"?
> 
> We are team of Tarantool developers working for MailRU Group.

Actually this decision was made without any discussions - it was
quickly hacked in back in 2018. Maybe you and Nikita had some
discussion prompted by Peter's firm stance that we should
uppercase, but that was it. I protested several times while I
was still on board but had not anticipated how bad the solution
would turn out to be when it is implemented to follow through on
time. Now it is still not to late - bit it's getting more late
every day.

What we learned since then is that every single newbie trips over
it.


> We had pretty much discussions internally on the matter and
> came up with this decision: we won't break backward compatibility
> in order to add some sugar.

What backward compatibility do you think will be broken?


> 
> > I don't see this has been discussed & rejected, so why are you
> > thinking you can make this decision?
> 
> All I can see on the matter is issue #4467 which we agreed to
> be broken by design. I see no solid proposals neither in discussions
> nor in github issues on how it supposed to work. If it will occur -
> we'll happily consider it.
> 
> > Maybe "we" instead of making "decisions" goes to users and
> > customers and asks them what they expect?
> 
> Why not to ask if public demands free beer? Right now business
> dictates us to work on other things.

Like Chris patch?

-- 
Konstantin Osipov, Moscow, Russia

  reply	other threads:[~2019-12-09 13:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-29 23:39 Chris Sosnin
2019-11-30 20:34 ` Konstantin Osipov
2019-12-01 14:12   ` k.sosnin
2019-12-01 14:36   ` Vladislav Shpilevoy
2019-12-02  7:07     ` Konstantin Osipov
2019-12-02 14:36       ` Nikita Pettik
2019-12-02 14:49         ` Konstantin Osipov
2019-12-06 11:42       ` Kirill Yukhin
2019-12-06 20:17         ` Konstantin Osipov
2019-12-09 11:06           ` Kirill Yukhin
2019-12-09 11:24             ` Konstantin Osipov
2019-12-09 13:25               ` Kirill Yukhin
2019-12-09 13:39                 ` Konstantin Osipov [this message]
2019-12-09 14:07                   ` Nikita Pettik
2019-12-09 23:09                   ` Vladislav Shpilevoy
2019-12-10  8:19                     ` Konstantin Osipov
2019-12-10 12:44                       ` Kirill Yukhin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191209133955.GA8196@atlas \
    --to=kostja.osipov@gmail.com \
    --cc=kyukhin@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH] box: remove unicode_ci for functions' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox