As seen in: https://www.techempower.com/benchmarks/#section=data-r18

vibe.d once again ranks terrible on the list.

With the power of D etc. it should be able to perform at the same level as the top frameworks but it just isn't so what are the reasons, where can it be improved and what areas do we as community need to look into and improve upon?

On Wed, Jul 10, 2019 at 9:20 PM bauss via Digitalmars-d < digitalmars-d@puremagic.com> wrote:

> As seen in: https://www.techempower.com/benchmarks/#section=data-r18
>
> vibe.d once again ranks terrible on the list.
>
> With the power of D etc. it should be able to perform at the same level as the top frameworks but it just isn't so what are the reasons, where can it be improved and what areas do we as community need to look into and improve upon?
>

Terrible? Really? I would say not perfect but still good. Main problem is with vibe-d:http package. I have try to use vibe-d without it, just use vibe-core and speed was simmilar to others frameworks on top.

On Wednesday, 10 July 2019 at 19:16:11 UTC, bauss wrote:
> As seen in: https://www.techempower.com/benchmarks/#section=data-r18
>
> vibe.d once again ranks terrible on the list.
>
> With the power of D etc. it should be able to perform at the same level as the top frameworks but it just isn't so what are the reasons, where can it be improved and what areas do we as community need to look into and improve upon?

There's more to performance than the language you choose.

On Wednesday, 10 July 2019 at 20:50:16 UTC, Exil wrote:
> On Wednesday, 10 July 2019 at 19:16:11 UTC, bauss wrote:
>> As seen in: https://www.techempower.com/benchmarks/#section=data-r18
>>
>> vibe.d once again ranks terrible on the list.
>>
>> With the power of D etc. it should be able to perform at the same level as the top frameworks but it just isn't so what are the reasons, where can it be improved and what areas do we as community need to look into and improve upon?
>
> There's more to performance than the language you choose.

Buut fast code fast!

On Wed, Jul 10, 2019 at 08:54:56PM +0000, JN via Digitalmars-d wrote:
> On Wednesday, 10 July 2019 at 20:50:16 UTC, Exil wrote:
> > On Wednesday, 10 July 2019 at 19:16:11 UTC, bauss wrote:
> > > As seen in: https://www.techempower.com/benchmarks/#section=data-r18
> > > 
> > > vibe.d once again ranks terrible on the list.
> > > 
> > > With the power of D etc. it should be able to perform at the same level as the top frameworks but it just isn't so what are the reasons, where can it be improved and what areas do we as community need to look into and improve upon?
> > 
> > There's more to performance than the language you choose.
> 
> Buut fast code fast!

That motto makes me cringe. Every time.


T

-- 
It won't be covered in the book. The source code has to be useful for something, after all. -- Larry Wall

On Wednesday, 10 July 2019 at 20:47:30 UTC, Daniel Kozak wrote:
> On Wed, Jul 10, 2019 at 9:20 PM bauss via Digitalmars-d < digitalmars-d@puremagic.com> wrote:
>
>> As seen in: https://www.techempower.com/benchmarks/#section=data-r18
>>
>> vibe.d once again ranks terrible on the list.
>>
>> With the power of D etc. it should be able to perform at the same level as the top frameworks but it just isn't so what are the reasons, where can it be improved and what areas do we as community need to look into and improve upon?
>>
>
> Terrible? Really? I would say not perfect but still good. Main problem is with vibe-d:http package. I have try to use vibe-d without it, just use vibe-core and speed was simmilar to others frameworks on top.

It is terrible! Whatever the excuse, there is no other way to look at it than to say that based on the tech-empower tests, you wouldn't really consider vibe-d for a web-framework.

On Wednesday, 10 July 2019 at 19:16:11 UTC, bauss wrote:
> As seen in: https://www.techempower.com/benchmarks/#section=data-r18
>
> vibe.d once again ranks terrible on the list.
>
> With the power of D etc. it should be able to perform at the same level as the top frameworks but it just isn't so what are the reasons, where can it be improved and what areas do we as community need to look into and improve upon?

Compare to C/C++/Rust/GO/Dart/JAVA/JavaScript/Erlang,   the Github D trending is empty for most time.

D has long history but small community,   producible feature but poor ecosystem.

In this forum,  people talk about to use D  in mobile almost decade ago,   until now the LDC Android developer and IOS developer both give up.   GDC/DMD not support mobile.

D use for web also start almost decade ago,   but in much better status compare to mobile support.

On Thu, Jul 11, 2019 at 12:10 AM sanjayss via Digitalmars-d < digitalmars-d@puremagic.com> wrote:

>
> It is terrible! Whatever the excuse, there is no other way to look at it than to say that based on the tech-empower tests, you wouldn't really consider vibe-d for a web-framework.
>

I disagree, there are many other more well known frameworks use all over the world which has much  terrible performance and there are still considered.

On Thursday, 11 July 2019 at 08:04:03 UTC, Daniel Kozak wrote:
> On Thu, Jul 11, 2019 at 12:10 AM sanjayss via Digitalmars-d < digitalmars-d@puremagic.com> wrote:
>
>>
>> It is terrible! Whatever the excuse, there is no other way to look at it than to say that based on the tech-empower tests, you wouldn't really consider vibe-d for a web-framework.
>>
>
> I disagree, there are many other more well known frameworks use all over the world which has much  terrible performance and there are still considered.

It's still terrible compared to what it should rank.

vibe.d should be ranking near the top since that's where D's usual performance is ranked.

Look at the difference between D's performance and then look at Rust,C and C++. D is not even near those. Rust ranks in the top.

Even .NET performs better than D in those benchmarks.

We need to just realize that D did terrible in this benchmark and perhaps the problem is something internally in vibe.d and then we need to focus on what exactly the issue is, locate it and fix that.

vibe.d can indeed rank just as high but it doesn't.

On Wednesday, 10 July 2019 at 20:50:16 UTC, Exil wrote:
> On Wednesday, 10 July 2019 at 19:16:11 UTC, bauss wrote:
>> As seen in: https://www.techempower.com/benchmarks/#section=data-r18
>>
>> vibe.d once again ranks terrible on the list.
>>
>> With the power of D etc. it should be able to perform at the same level as the top frameworks but it just isn't so what are the reasons, where can it be improved and what areas do we as community need to look into and improve upon?
>
> There's more to performance than the language you choose.

Yes there is BUT for a web framework to properly scale you need performance.

D is supposed to be powerful, it's supposed to have performance on pair with C / C++, so there's no excuse for why it ranks even worse than .NET.

Of course the problem here is most likely not D but vibe.d's infrastructure.

My post is not about "bashing" D. I have been using D primarily for all my projects for the past 6 years.

My post is about highlighting an issue and figuring out what we can do as a community to fix it and have D rank higher.