On Sat, 2014-06-21 at 12:01 -0400, Steven Walters wrote:
> On Fri, Jun 20, 2014 at 8:54 AM, Russel Winder <rus...@winder.org.uk> wrote:
> >
> > As for assembly language, no applications programmer should ever have to
> > use it!
>
> Assembly always has a place, and that place more commonly appears in
> maximizing speed/performance.
> This is more frequent in applications that have a heavy mathematical
> background/focus.
> statistics/scientific analysis, and video/audio processing are some
> examples of this.
Those assembly language bits should be in libraries rather than
applications though. But I agree there is an important role for assembly
language in performance oriented systems. And operating systems for
things like context switching.
> > Someone on the Gradle native code team needs to write a short article
> > saying what Gradle beats Dub, SCons, Waf and CMake. If this argument
> > cannot be made convincingly then Gradle will have no future in the wider
> > world of native code build. From experience it is hard enough weaning
> > people off Make, and introducing Python is a battle. I suspect
> > introducing JVM is going to be an even bigger battle than introducing
> > PVM.
>
> I say that Gradle's (initial?) target audience for the native code
> support is not development teams that deal purely in native code.
> It'll be harder to convince them away from what they've been used to
> for years and it "works" enough for them.
> That is more summarily, those teams don't have a pain point that needs
> resolving.
>
> Instead Gradle's first goal should be targeting teams/"houses" that
> deal in a mixture of jvm and non-jvm based languages.
> In my opinion, this is because there isn't much in a good single
> solution for dealing with the combination of all of them.
> Often needing different build systems/frameworks to try and smudge
> together some final result.
> Or teams developing something in house to try and handle it more
> gracefully (but then the maintenance!)
>
> E.g. at my work, we are a multi-language house from being heavy in
> both PLM/PDM and CAD, so we're consistently dealing with all of Java,
> C, C++, and C#.
> Being able to use only a single build system to handle everything
> would be such a blessing and simplification of the mess that is the
> current state of things.
> That is, it would solve the pain point we've had for a rather long time.
There are a number of people using SCons in the mixed Java/C++ space. I
keep saying they should use Gradle, but… they keep wanting to fix SCons.
This is fine but I think it will be hard.
--
Russel.
=============================================================================
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net
41 Buckmaster Road m: +44 7770 465 077 xmpp: rus...@winder.org.uk
London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
