Bad array indexing is considered deadly

Jonathan M Davis via Digitalmars-d digitalmars-d at puremagic.com
Thu Jun 1 03:26:31 PDT 2017


On Thursday, June 01, 2017 06:13:25 Steven Schveighoffer via Digitalmars-d 
wrote:
> It just means that D is an inferior platform for a web framework, unless
> you use the process-per-request model so the entire thing doesn't go
> down for one page request. But that obviously is going to cause
> performance problems.
>
> Which is unfortunate, because vibe.d is a great platform for web
> development, other than this. You could go Adam's route and just put the
> blinders on, but I think that's not a sustainable practice.

Honestly, unless something about vibe.d prevents fixing bugs like bad array
indices, I'd just use vibe.d and program normally, and if a problem like you
hit occurs, I'd fix it, and then that wouldn't crash the program anymore.
Depending on how many such logic errors got passed the testing process, it
could take a while before the server was stable enough, or it could be very
little time at all, but in the long run, there wouldn't be any invalid array
indices, because those bugs would have been fixed, and there wouldn't be a
problem anymore.

Now, if there's something about vibe.d that outright prevents fixing these
bugs or makes them impossible to avoid, then that calls for a different
approach, but from what I understand of the situation, I don't see anything
here preventing using vibe.d's approach with fibers. It's just that missed
bugs will be very annoying until they're fixed, but that's true of most
programs.

- Jonathan M Davis



More information about the Digitalmars-d mailing list