Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bZgVU-0002A7-BT for pgsql-hackers@arkaria.postgresql.org; Tue, 16 Aug 2016 15:42:24 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bZgVT-0005CQ-2s for pgsql-hackers@arkaria.postgresql.org; Tue, 16 Aug 2016 15:42:23 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bZgU5-0003gd-OB for pgsql-hackers@postgresql.org; Tue, 16 Aug 2016 15:40:57 +0000 Received: from newmail.postgrespro.ru ([93.174.131.138] helo=mail.postgrespro.ru) by magus.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bZgU1-0000Wm-Nx for pgsql-hackers@postgresql.org; Tue, 16 Aug 2016 15:40:57 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.postgrespro.ru (Postfix) with ESMTP id 59BB721C2DCB; Tue, 16 Aug 2016 18:40:53 +0300 (MSK) X-Virus-Scanned: Debian amavisd-new at postgrespro.ru Received: from mail.postgrespro.ru ([127.0.0.1]) by localhost (mail.postgrespro.ru [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4srS6YpWv6Ys; Tue, 16 Aug 2016 18:40:53 +0300 (MSK) Received: from e733 (unknown [192.168.27.1]) by mail.postgrespro.ru (Postfix) with ESMTPSA id 1D1E921C2DC7; Tue, 16 Aug 2016 18:40:53 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mail; t=1471362053; bh=SPTbo8nio7oFLArkr5BmIgaCMCJ0B3Hg1xrJ4ygnkwU=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=A7U/rbFrWL+v7/tv1s58c7TgO520ifZk0MG6Ux4WzhIkovDwEz/UsC+EBSSFOl7YV RNwDu5Ra38plhVfgL2osBk6SPq9k25OLszy/K5g/wot9l0oks+YW+QixwHo3C23KiH Sil7hdMrnTQKbHOvdj5IpcIh1JNU2F7elXJv6zJY= Date: Tue, 16 Aug 2016 18:39:40 +0300 From: Aleksander Alekseev To: Jim Nasby Cc: Gavin Flower , dandl , 'Adam Brusselback' , 'Joy Arulraj' , 'kang joni' , 'Dmitry Igrishin' , Pg Hackers , Peter Eisentraut Subject: Re: [GENERAL] C++ port of Postgres Message-ID: <20160816183940.4818d854@e733> In-Reply-To: References: <007001d1f786$d903fa90$8b0befb0$@andl.org> <00a52208-3199-5858-8846-2530b0bb34df@archidevsys.co.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.5 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Well, well, well. Another C vs C++ holly war, really? > > In both cases, part of the motivation to change from C was to > > appeal to new developers - from what I remember of the > > discussions. > > Moving this to -hackers. Original thread at [1]. > > tl;dr: A C++ port of Postgres has been created, and several folks on > general have commented that this makes it easier to work with the > Postgres codebase. This potentially attracts more developers to the > project. I hope we can find a way to pull these folks into the fold. Who are these "folks"? How many more developers it would attract _exactly_, not potentially? > People in core have complained that we don't have enough hackers > coming in (which I agree with). Part of that is lack of familiarity > with C. One again, which "people"? I've seen people complained that there is not enough code reviewers and testers. I doubt very much its something C++ will help with. > I think we can all agree that a C++ fork of Postgres would be a huge > waste of time, so the question becomes should core postgres start > supporting C++. > > Peter wrote a blog about this in 2013 that makes some good arguments > [2]; in particular "easing into" this by first officially supporting > C++ compilation. I also like the idea of investigating Rust. And I wrote a blog post (in Russian) [1] in 2016 why nobody should (if they can) write a new code in C++. In my opinion Rust looks way more promising. However I personally prefer to wait like 5 years before using a new and shiny technology. This is also something I blogged about (in Russian [2], translation [3]). > I realize there's little technical reason why we *need* C++ support. You are right, there is none. > The level if discipline applied to our codebase negates some of the > benefits of C++. But maintaining the discipline takes a lot of time > and effort, and makes it more difficult to attract new contributors. There are companies. They hire developers who write code. Doesn't really matters in which language. Long story short - I strongly believe you are trying to solve a problem that doesn't exist. And probably create a few new ones. [1] http://eax.me/c-vs-cpp/ [2] http://eax.me/cpp-will-never-die/ [3] http://www.viva64.com/en/b/0324/ -- Best regards, Aleksander Alekseev -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers