From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,3e9e2e402ed75bc3 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,UTF8 X-Received: by 10.180.198.210 with SMTP id je18mr14841322wic.1.1366701041892; Tue, 23 Apr 2013 00:10:41 -0700 (PDT) Path: p18ni15760wiv.0!nntp.google.com!goblin3!goblin1!goblin2!goblin.stu.neva.ru!aioe.org!.POSTED!not-for-mail From: =?utf-8?Q?Yannick_Duch=C3=AAne_=28Hibou57?= =?utf-8?Q?=29?= Newsgroups: comp.lang.ada Subject: Re: aws vs ruby rails or php? how much faster? Date: Tue, 23 Apr 2013 09:10:39 +0200 Organization: Ada @ Home Message-ID: References: <87vc7fm3lp.fsf@adaheads.sparre-andersen.dk> <517627a4$0$32104$14726298@news.sunsite.dk> NNTP-Posting-Host: MElZi/LkXjdV3cIyylAczw.user.speranza.aioe.org Mime-Version: 1.0 X-Complaints-To: abuse@aioe.org User-Agent: Opera Mail/12.15 (Linux) X-Notice: Filtered by postfilter v. 0.8.2 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Content-Transfer-Encoding: Quoted-Printable Date: 2013-04-23T09:10:39+02:00 List-Id: Le Tue, 23 Apr 2013 08:18:12 +0200, Thomas L=C3=B8cke = a = =C3=A9crit: > A few years ago I did a test[1] against node.js, mainly to prove that > the threading model of AWS was not as inferior to the event model of > node.js as many claimed. Asynchronous I/O can be achieved with Ada too, and that does not implies= = tasking, just wrapping what the OS provides for that. For the event = driven=E2=80=91model, that's a topic I don't know, so I'm not sure to un= derstand = what it means (neither I see if something prevent it to be designed in = Ada). Looking at the two snippets, I could not avoid thinking that's more = comparing implementation of basic control flow and binding to system cal= ls = than comparing anything else. Also, that's too small to tell anything = about a real sized application. Node.js may be fast with than very tiny = = example, but if that's really JavaScript, then that's probably still = unmaintainable as things become more complex and big. I wonder if this kind of benchmark really tells anything (the one with A= WS = vs Node.js). -- = =E2=80=9CSyntactic sugar causes cancer of the semi-colons.=E2=80=9D [1] =E2=80=9CStructured Programming supports the law of the excluded muddle.= =E2=80=9D [1] [1]: Epigrams on Programming =E2=80=94 Alan J. =E2=80=94 P. Yale Univers= ity