[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: james.sumners at gmail.com (James Sumners)
- Date: Sat, 20 Jul 2013 09:26:20 -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]>
If you're not, or the programmer doing the work is not, already a
competent Java developer, you shouldn't expect that to be the case. It
can take a long time just to get a Java project skeleton configured.
Then you have to be familiar with all of the libraries you'll need to
use.
Go with the language you _know_.
On Sat, Jul 20, 2013 at 9:15 AM, Geoffrey Myers
<lists at serioustechnology.com> wrote:
> Further fuel on the fire. Scalability is critical. This has to process a lot of data very quickly. Hence the idea of using C. There is one proponent of Java based of the expectation development will be faster.
>
> --
> From my iPhone
> Geoffrey Myers
--
James Sumners
http://james.roomfullofmirrors.com/
"All governments suffer a recurring problem: Power attracts
pathological personalities. It is not that power corrupts but that it
is magnetic to the corruptible. Such people have a tendency to become
drunk on violence, a condition to which they are quickly addicted."
Missionaria Protectiva, Text QIV (decto)
CH:D 59