Vibe.d looks great on the surface but lack of documentation, commonly used functionality, and that it looks like it is dying suggests that putting any effort in to it will be a waste. Go, OTH, has tons of frameworks, most are actively support, very well documented(beego, revel, etc), and feature rich.

If I am going to put any work in to something, I want to make sure that I can depend on it in the future. It doesn't look like this is the case with vibe.d. Hopefully vibe.d will not die and will mature enough in the future so it actually provides a good alternative to the current web frameworks.

On Tuesday, 20 September 2016 at 19:14:41 UTC, Intersteller wrote:
> Vibe.d looks great on the surface but lack of documentation, commonly used functionality, and that it looks like it is dying suggests that putting any effort in to it will be a waste. Go, OTH, has tons of frameworks, most are actively support, very well documented(beego, revel, etc), and feature rich.
>
> If I am going to put any work in to something, I want to make sure that I can depend on it in the future. It doesn't look like this is the case with vibe.d. Hopefully vibe.d will not die and will mature enough in the future so it actually provides a good alternative to the current web frameworks.

What exactly makes you think vibe is dying?

Dne 20.9.2016 v 21:14 Intersteller via Digitalmars-d napsal(a):

> Vibe.d looks great on the surface but lack of documentation, commonly used functionality, and that it looks like it is dying suggests that putting any effort in to it will be a waste. Go, OTH, has tons of frameworks, most are actively support, very well documented(beego, revel, etc), and feature rich.
>
> If I am going to put any work in to something, I want to make sure that I can depend on it in the future. It doesn't look like this is the case with vibe.d. Hopefully vibe.d will not die and will mature enough in the future so it actually provides a good alternative to the current web frameworks.
Ok, can you link some of your request about what missing on vibe.d? It is easy to say this framework does not support this. this framework has bad doc and so on. But these are statements without any proof. So this post does not have any value until you add some specifics. It would be nice if you share what exactly do you miss from vibe.d and what doc need to be improved. For eg. from my POV vibe.d doc is ok and there is everything I need (OK I would prefer better async-event lib, but AFAIK Sonke works on a new one)

On Tuesday, 20 September 2016 at 19:16:04 UTC, cym13 wrote:
> What exactly makes you think vibe is dying?

it lacks the documentation?

On Tuesday, 20 September 2016 at 19:16:04 UTC, cym13 wrote:
>
> What exactly makes you think vibe is dying?

His first post is from 6 days ago, so I would guess that he doesn't seem to have much of a sense of its history.

On Tuesday, 20 September 2016 at 19:14:41 UTC, Intersteller wrote:
> Vibe.d looks great on the surface but lack of documentation, commonly used functionality, and that it looks like it is dying suggests that putting any effort in to it will be a waste. Go, OTH, has tons of frameworks, most are actively support, very well documented(beego, revel, etc), and feature rich.

What is vibe.d missing? It works great for me and the documentation is great imo too because it has everything I need. I use vibe.d at the company I work at and I use it for all my websites. I never had any problems with it

On Tuesday, 20 September 2016 at 19:47:01 UTC, jmh530 wrote:
> On Tuesday, 20 September 2016 at 19:16:04 UTC, cym13 wrote:
>>
>> What exactly makes you think vibe is dying?
>
> His first post is from 6 days ago, so I would guess that he doesn't seem to have much of a sense of its history.

Which makes him the perfect example of beginner with a newcommer's look :)

On Tuesday, 20 September 2016 at 19:47:12 UTC, WebFreak001 wrote:
> On Tuesday, 20 September 2016 at 19:14:41 UTC, Intersteller wrote:
>> Vibe.d looks great on the surface but lack of documentation, commonly used functionality, and that it looks like it is dying suggests that putting any effort in to it will be a waste. Go, OTH, has tons of frameworks, most are actively support, very well documented(beego, revel, etc), and feature rich.
>
> What is vibe.d missing? It works great for me and the documentation is great imo too because it has everything I need. I use vibe.d at the company I work at and I use it for all my websites. I never had any problems with it

Lets me say from a beginners perspective,
* How do I build a file upload form (single and multiple file uploads)
* How do I work with mongoDB to do CRUD.
* How do I use the Web API beyond hello world!
* Form validation?
* Data sanitization?
* How do I structure my application for real-world (reusable and maintainable code) e.g for a simple blog, simple CMS etc. :)
...

Some of these things may seem easy to figure-out but can be difficult for a beginner unless he/she has a copy of Kai's book at the moment (D Web Development) :)

Dne 20.9.2016 v 22:00 cym13 via Digitalmars-d napsal(a):

> On Tuesday, 20 September 2016 at 19:47:01 UTC, jmh530 wrote:
>> On Tuesday, 20 September 2016 at 19:16:04 UTC, cym13 wrote:
>>>
>>> What exactly makes you think vibe is dying?
>>
>> His first post is from 6 days ago, so I would guess that he doesn't seem to have much of a sense of its history.
>
> Which makes him the perfect example of beginner with a newcommer's look :)
Or a troll :). But I guess the first one is right

Dne 20.9.2016 v 22:01 Karabuta via Digitalmars-d napsal(a):
> On Tuesday, 20 September 2016 at 19:47:12 UTC, WebFreak001 wrote:
>> On Tuesday, 20 September 2016 at 19:14:41 UTC, Intersteller wrote:
>>> Vibe.d looks great on the surface but lack of documentation, commonly used functionality, and that it looks like it is dying suggests that putting any effort in to it will be a waste. Go, OTH, has tons of frameworks, most are actively support, very well documented(beego, revel, etc), and feature rich.
>>
>> What is vibe.d missing? It works great for me and the documentation is great imo too because it has everything I need. I use vibe.d at the company I work at and I use it for all my websites. I never had any problems with it
>
> Lets me say from a beginners perspective,
> * How do I build a file upload form (single and multiple file uploads)
> * How do I work with mongoDB to do CRUD.
> * How do I use the Web API beyond hello world!
> * Form validation?
> * Data sanitization?
> * How do I structure my application for real-world (reusable and maintainable code) e.g for a simple blog, simple CMS etc. :)
> ...
>
> Some of these things may seem easy to figure-out but can be difficult for a beginner unless he/she has a copy of Kai's book at the moment (D Web Development) :)
Nothing of this is specific for vibe.d, so I do not see any reason to have doc about this in vibe.d