[Development] [BB++] Now is 3.5x faster than Node.JS

[Thiago Macieira]

On Monday, 24 July 2017 05:47:34 PDT Phil Bouchard wrote:
> Thiago Macieira <thiago.macieira at intel.com> wrote:
> > On Sunday, 23 July 2017 15:13:50 PDT Phil Bouchard wrote:
> > But that's just it: the GC doesn't happen as often if you're not under
> > memory pressure. You can postpone the GC to later and run it less often,
> > when you're less busy. Your code can focus on being as fast as it can
> > while the user is paying attention. Cleanup can be left undone until the
> > user isn't paying attention.
> 
> Well I had a Samsung (Android) before and the damn garbage collector was
> kicking in everytime I had a phone call so it obviously failed to predict
> when to kick in or not.

How do you know it was the GC? What did you do to extract the evidence that it 
was the ART (Android Runtime) garbage collector kicking in?

How do you know it wasn't some other background process waking up and doing 
something? Like getting the device's location and sending to the cloud? Or the 
voice command parser?

> > But will they be 3.5x harder to write? 3.5x more error prone?
> 
> No. Like I was saying the errors are reported at compile time so you'll
> spend less time trying to reproduce a bug at run-time.

Have you ever talked to developers who prefer interpreted languages? "At 
compile time" does not mean "easier". On the contrary, for them it usually 
means "harder".

The timing of the report may make identifying issues easier, but it doesn't 
help if there are more issues due to a stricter language.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center