[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ale] Thread safe coding, Java or C
- Subject: [ale] Thread safe coding, Java or C
- From: philip at turmel.org (Phil Turmel)
- Date: Sat, 20 Jul 2013 11:02:17 -0400
- In-reply-to: <[email protected]>
- References: <[email protected]> <CAAt=rgDLBef8daDgH4R5nz-5QCKqJ=Ct2e3BqT7iSkbhT3R7jQ@mail.gmail.com> <CADvA-d=+3c56zunDTkjVEKmMfkkBBie++8zp1K3=o7VzoPJqRQ@mail.gmail.com> <CAHWNiXyqXFtZPXF3iJ5we0DFnGb+psny7DY=7E+Zj2kOi6Opdw@mail.gmail.com> <[email protected]> <[email protected]> <CAAt=rgAhtfSe-W7Nh9NctJZByr4GgUtd700p6qKnpru3KGXu8g@mail.gmail.com> <[email protected]>
On 07/20/2013 10:38 AM, Geoffrey Myers wrote:
> One developer is a seasoned Java programmer, the other a seasoned C programmer.
That being the case, you might want to focus on your application's use
of memory... I found the following article generally useful in spite of
its target audience (android, iOS):
http://sealedabstract.com/rants/why-mobile-web-apps-are-slow/
You have to do all your own memory management in C, but in doing so, you
are avoiding all of the disruptions of garbage collection. But if your
program's data-structures are expected to be long-lived, java won't be
at a disadvantage.
Of course, C++ has many of the object orientation advantages that java
has, but doesn't do garbage collection (natively). If you want both
programmers to work together and be productive quickly, C++ might be the
best compromise. The C guy brings manual memory management skills to
the table, while the java guy brings polymorphism and related skills.
HTH,
Phil