nealrichardson commented on a change in pull request #68:
URL: https://github.com/apache/arrow-site/pull/68#discussion_r462445420
##########
File path: _posts/2020-07-27-cpp-build-simplification.md
##########
@@ -0,0 +1,271 @@
+---
+layout: post
+title: "INSERT TITLE HERE"
+date: "2020-07-24 00:00:00 -0600"
+author: pmc
+categories: [application]
+---
+<!--
+{% comment %}
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to you under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+{% endcomment %}
+-->
+
+Over the last four and a half years, we've worked to build a
+"batteries-included" development platform for high-performance analytics
+applications in C++. As the scope of the project has grown, we have sometimes
+taken on additional library dependencies to support a wide variety of systems
+and data processing tasks.
+
+While these dependencies give us leverage on hard problems, in some cases their
+addition has caused extra complexity for projects that depend on Arrow, even if
+their use of Arrow is limited to basic interactions with the Arrow columnar
+format. Some projects have therefore been concerned about the implications of
+taking on the Arrow C++ library as a dependency if Arrow's build and runtime
+requirements spill over into their project's requirements. Indeed, in the
+earlier stages of the Arrow project development, dependency management issues
+did cause problems for early adopters.
+
+We want developers to trust that they can use and depend on our libraries, and
+that doing so doesn't add a burden for their own project maintenance or for
+their users. Over the last year, we have undertaken a number of significant
+projects to accommodate the different ways that people want to depend on Arrow
+C++. We've aimed to make the build process simple by default, without requiring
+special environment setup, yet also highly configurable for those who need to
+specialize. And we've worked to make builds faster and more compact, even as we
+continue to add new functionality.
+
+This post covers many of the efforts we've made, both in the C++ libraries and
+in the Arrow Python and R packages that depend on them. Compared to a year ago,
+the build experience is much more reliable on a wider range of platforms,
+requires fewer dependencies, and yields smaller package sizes.
+
+## Minimal default build options
+
+One rough edge for people using Arrow as a dependency was that many optional
+project components were enabled in the build by default, thus requiring any
+extra dependencies of those optional components. Rather than expecting users to
+disable optional components one by one, we have made the default for all
+optional components to be `OFF` so that the default configuration is a
+dependency-free minimal core build.
+
+The only third-party library enabled by default is jemalloc, the project's
Review comment:
Noted, thanks
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
