Re: [OT] Re: Why I am switching to Go
On Friday, 23 September 2016 at 01:52:51 UTC, Nick Sabalausky wrote: They've now renamed Syphilis, et al. after Subaru's highest-end Impreza? *shakes head*. Who wants to bet *that* little bit of PC rubble-bouncing was spearheaded by someone with a vested interest in the Viper or Corvette or something? Fine, ok, so who wants to put together the PR to update Phobos's package name accordingly? Any takers? I wonder will programmers be called `digitally oriented persons` one day? And `laptop` sounds too patriarchic for my liking. Let's rename it. How about `mobtop` (mobile desktop)?
Re: [OT] Re: Why I am switching to Go
On 09/22/2016 11:41 AM, Chris wrote:
Around every two years they come up with something new, give or take a
year depending on the topic. In general, I got the impression that once
I've finally got used to using a certain term, it's no longer
(politically or otherwise) correct, e.g. "STD" => "STI" ("disease" is
obviously a bad bad word - unless you want to sell useless drugs for
made-up diseases). It happens all the time.
They've now renamed Syphilis, et al. after Subaru's highest-end Impreza?
*shakes head*. Who wants to bet *that* little bit of PC rubble-bouncing
was spearheaded by someone with a vested interest in the Viper or
Corvette or something?
Fine, ok, so who wants to put together the PR to update Phobos's package
name accordingly? Any takers?
Re: [OT] Re: Why I am switching to Go
On Thursday, 22 September 2016 at 15:22:57 UTC, Nick Sabalausky
wrote:
On 09/22/2016 07:43 AM, Steven Schveighoffer wrote:
On 9/20/16 3:14 PM, Intersteller wrote:
TL;DR: I like and have used Go extensively. I glanced at D for
20
minutes and didn't like it.
Grumpy old curmudgeon says: "Harumpf...Why back in my day, we
pronounced 'TL;DR' as 'summary'...or 'abstract' if we wanted to
be really really fancy" ;)
Never much understood "bouncing rubble" English changes like
that, or "internet"->"cloud", "preteen"->"tween", etc. Can't
tell if the trend is accelerating or it's just me getting old.
Around every two years they come up with something new, give or
take a year depending on the topic. In general, I got the
impression that once I've finally got used to using a certain
term, it's no longer (politically or otherwise) correct, e.g.
"STD" => "STI" ("disease" is obviously a bad bad word - unless
you want to sell useless drugs for made-up diseases). It happens
all the time.
[OT] Re: Why I am switching to Go
On 09/22/2016 07:43 AM, Steven Schveighoffer wrote: On 9/20/16 3:14 PM, Intersteller wrote: TL;DR: I like and have used Go extensively. I glanced at D for 20 minutes and didn't like it. Grumpy old curmudgeon says: "Harumpf...Why back in my day, we pronounced 'TL;DR' as 'summary'...or 'abstract' if we wanted to be really really fancy" ;) Never much understood "bouncing rubble" English changes like that, or "internet"->"cloud", "preteen"->"tween", etc. Can't tell if the trend is accelerating or it's just me getting old.
Re: Why I am switching to Go
On 9/20/16 3:14 PM, Intersteller wrote: TL;DR: I like and have used Go extensively. I glanced at D for 20 minutes and didn't like it. -Steve
Re: Why I am switching to Go
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. lol, no generics
Re: Why I am switching to Go
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. You can try hunt framework: git clone https://github.com/putaolabs/hunt-skeleton.git myproject cd myproject dub run Open the URL with the browser: http://localhost:8080/ OK, you seccessed. You can edit config/application.conf to change http port. You can edit config/routes to setting your router options, like: GET/index.index POST /index.hello You can add yourself Controller to source app/controller directory. You can like use java's play framework / php's laravel / ruby's rails / python's django framework to use dlang's hunt framework ( https://github.com/putaolabs/hunt/ ). We are not perfect, but we will continue to update, together to create a perfect D programming language framework.
Re: Why I am switching to Go
On Wednesday, 21 September 2016 at 18:00:14 UTC, Chris wrote: tldr; vibe.d helps you to set up web servers, but you have to know web related stuff too - or be willing to learn it as you go along. It's not straight out of the box. The tutorials page is not the prettiest page in the world. Among other things, it probably couldn't hurt to have an introductory paragraph at the top. It could potentially include a line that knowing networking and servers helps in understanding vibe (and maybe including links to a few good resources).
Re: Why I am switching to Go
On Wednesday, 21 September 2016 at 17:22:26 UTC, bachmeier wrote:
I agree, but it is easier to learn those things if you're using
a different language, due to the assumption with vibe.d that
you've got that background.
Yeah, I think that's the basic problem with people's expectations
of vibe.d. What is hard is not vibe.d but to know how to set up a
web project properly, which is a different kettle of fish. Maybe
we should make this clear to everyone: vibe.d helps you to set up
a server/web service, if you are already familiar with or willing
to learn web stuff.
Nice additions to vibed.org would be:
1. (more) template projects (chat room etc.)
2. a section that addresses common problems (cross origin access
and whatnot)
The web is a never ending source of grief for developers. Did you
know that to be able to play sound files more than once in Chrome
you have to `addField("Accept-Ranges", "bytes")` whenever a sound
file is requested? Not so with FF. It just never ends, and I
think sooner or later you will run into problems like that with
any framework.
tldr; vibe.d helps you to set up web servers, but you have to
know web related stuff too - or be willing to learn it as you go
along. It's not straight out of the box.
Re: Why I am switching to Go
On Wednesday, 21 September 2016 at 16:13:13 UTC, bachmeier wrote: On Wednesday, 21 September 2016 at 13:56:01 UTC, Nick Sabalausky wrote: On 09/20/2016 03:14 PM, Intersteller wrote: Vibe.d looks great on the surface but lack of documentation, http://vibed.org/docs http://vibed.org/api There's also two examples right on the homepage. Did you try scrolling? To someone like me, who has done little web development, that documentation isn't very helpful. I have copies of both D Web Development and Learning D (which includes a nice example) and *that* got me going. Overall, there are currently better alternatives to Vibe.d for someone wanting to learn web development. I you have "D Web Development" then that's enough to do almost anything with vibe.d in web development.
Re: Why I am switching to Go
On Wednesday, 21 September 2016 at 17:05:41 UTC, Chris wrote: found out that it's not vibe.d's lack of documentation, but how servers work that is the biggest obstacle. Once you know how certain things work, it's no longer so hard find out how to do it with vibe.d, e.g. when and how to set headers "Access-Control-Allow-Origin", "Accept-Ranges". But the reason you have to set these headers has nothing to do with vibe.d, but with HTTP, Javascript and browsers. I agree, but it is easier to learn those things if you're using a different language, due to the assumption with vibe.d that you've got that background.
Re: Why I am switching to Go
On Wednesday, 21 September 2016 at 16:13:13 UTC, bachmeier wrote: To someone like me, who has done little web development, that documentation isn't very helpful. I have copies of both D Web Development and Learning D (which includes a nice example) and *that* got me going. Overall, there are currently better alternatives to Vibe.d for someone wanting to learn web development. Well, it depends on what you want / need: server development or D + server development. If it's server development, there are loads of options and you don't need to go the lengths of learning D. In my case, I had loads of stuff written in D and wanted to use it as a web service. Thus, vibe.d was the obvious choice. I knew almost nothing about server development when I started and found out that it's not vibe.d's lack of documentation, but how servers work that is the biggest obstacle. Once you know how certain things work, it's no longer so hard find out how to do it with vibe.d, e.g. when and how to set headers "Access-Control-Allow-Origin", "Accept-Ranges". But the reason you have to set these headers has nothing to do with vibe.d, but with HTTP, Javascript and browsers.
Re: Why I am switching to Go
On Wednesday, 21 September 2016 at 13:56:01 UTC, Nick Sabalausky wrote: On 09/20/2016 03:14 PM, Intersteller wrote: Vibe.d looks great on the surface but lack of documentation, http://vibed.org/docs http://vibed.org/api There's also two examples right on the homepage. Did you try scrolling? To someone like me, who has done little web development, that documentation isn't very helpful. I have copies of both D Web Development and Learning D (which includes a nice example) and *that* got me going. Overall, there are currently better alternatives to Vibe.d for someone wanting to learn web development.
Re: Why I am switching to Go
On Wednesday, 21 September 2016 at 13:56:01 UTC, Nick Sabalausky wrote: On 09/20/2016 03:14 PM, Intersteller wrote: Vibe.d looks great on the surface but lack of documentation, http://vibed.org/docs http://vibed.org/api There's also two examples right on the homepage. Did you try scrolling? I'll grant that the stupid "modern" sales-pitch-first, content-hidden-in-small-print-below web design style that's so popular and now used on vibe's homepage makes those harder to find than they should be, but still, these ARE right there on the homepage, and it's very complete. I agree. When I fist saw the new layout, it took me a few minutes to find my way around. "Documentation", one of the most important points, is not very prominent and leads you to "First steps" instead of the "API Reference" (which again is not very prominent). Maybe it would help to separate "API" and "First steps" and make points like "Authentication" (and other common features) more prominent. commonly used functionality, Not really. Cite examples of such missing functionality? and that it looks like it is dying suggests that You're just making that up, aren't you? Here: https://github.com/rejectedsoftware/vibe.d/commits/master Not to be a dick, but you really didn't look *at all*, did you? Given that vibe.d's last release was on "Mon, 04 Jul 2016" (~2 1/2 months ago) I don't know where the OP got that impression form either. If you look at Go's release policy you'll see that it has had a 6 months release cycle since 1.5[1], with longer breaks before that: go1.7 (released 2016/08/15) Minor revisions go1.6 (released 2016/02/17) Minor revisions go1.5 (released 2015/08/19) Minor revisions [1] https://golang.org/doc/devel/release.html Wrong claims or assumptions like "vibe.d is dying" have to be addressed on this forum, since they might (wrongly) turn off potential users.
Re: Why I am switching to Go
14 months ago i tried to write my first webapp. initially i chose vibe.d to be my framework. i got a simple app running quickly, but due to my lack of knowledge about webapps in general i got stuck at rather fundamental things. like doing authentication over oauth, or even have a rough guideline how to structure my app. as a beginner using d and vibe.d is quite hard. nobody takes you by the hand and it is that read the fucking manual situation :D .. most of us are quite lazy with reading the docs, and want to see some working stuff! :) (at least if you are programming on fun projects and not for your job) so as a result for my own project i switched to nodejs. nodejs fresh, its new and its in use everywhere .. every problem has been tackled with it and stackoverflow solved 90% of my problems. i still produced the worst spaghetti code with it because i didn't know how to structure a webapp correctly. to my conclusion .. if you don't know what you are doing switch to something popular and you will be much happier. npm install icecreammachinewithsprinkles! but if you are good at what you are doing and see the benefits that d can give you it is worth staying.
Re: Why I am switching to Go
On Wed, 21 Sep 2016 09:56:01 -0400, Nick Sabalausky wrote: > Not to be a dick, but you really didn't look *at all*, did you? You *are* being a dick. Please stop it. When someone takes the time to post something like this, they are reporting the pain they experienced. They might not articulate the precise problem that exists, but that general area has a significant pain point. Berating them is an inappropriate response. Vibe has some documentation. Either Intersteller didn't find it after what they thought a reasonable amount of searching, or they found it and found it lacking. Features whose documentation you can't find are equivalent to missing features. Vibe is under active development. This apparently isn't advertised well enough for Intersteller to be confident in it. The home page has release announcements for February and July, which seems appropriate for a small project occasionally worked on. In this case, it's a moderately large project steadily worked on, with blog posts about as frequent as the golang.org blog.
Re: Why I am switching to Go
...I could care less why you are switching to Go...
Re: Why I am switching to Go
On 09/20/2016 03:14 PM, Intersteller wrote: Vibe.d looks great on the surface but lack of documentation, http://vibed.org/docs http://vibed.org/api There's also two examples right on the homepage. Did you try scrolling? I'll grant that the stupid "modern" sales-pitch-first, content-hidden-in-small-print-below web design style that's so popular and now used on vibe's homepage makes those harder to find than they should be, but still, these ARE right there on the homepage, and it's very complete. commonly used functionality, Not really. Cite examples of such missing functionality? and that it looks like it is dying suggests that You're just making that up, aren't you? Here: https://github.com/rejectedsoftware/vibe.d/commits/master Not to be a dick, but you really didn't look *at all*, did you?
Re: Why I am switching to Go
On Wednesday, 21 September 2016 at 01:15:22 UTC, deadalnix wrote: On Tuesday, 20 September 2016 at 20:59:18 UTC, wobbles wrote: I would say otherwise. I've built multiple sites in vibe-d, so I probably wouldn't need them, but having a vibe-d specific beginner tutorial from start to end of a project would be great. Tutorial != doc. I agree and if you know web development and have done any significant development vibe should not be hard to learn off the docs. If the OP was to say anything about ecosystem then yes Go maybe a better option for the OP. I don't think vibe is bad but ecosystem is more lacking for the developer who just wants stuff to work and not put in the leg work on fixing bugs/features in various pieces of the development of web applications.
Re: Why I am switching to Go
On Tuesday, 20 September 2016 at 20:59:18 UTC, wobbles wrote: I would say otherwise. I've built multiple sites in vibe-d, so I probably wouldn't need them, but having a vibe-d specific beginner tutorial from start to end of a project would be great. Tutorial != doc.
Re: Why I am switching to Go
On Tuesday, 20 September 2016 at 22:17:26 UTC, WhatMeWorry wrote: On Tuesday, 20 September 2016 at 20:35:49 UTC, Daniel Koz wrote: Dne 20.9.2016 v 22:01 Karabuta via Digitalmars-d napsal(a): [...] Nothing of this is specific for vibe.d, so I do not see any reason to have doc about this in vibe.d Could he be asking for little examples of the above bullets? Maybe small working examples online? It would help a lot just to pull out the unit tests and add a few comments and put them up on web under sample usage... I suggested to Sonke before, but there's always a lot to do.
Re: Why I am switching to Go
On Tuesday, 20 September 2016 at 21:19:49 UTC, Daniel Kozak wrote: My fault. I was speaking about doc (API), I do not say anything about tutorial and so on. Yes I belive having more tutorials and howtos it is a good thing. I don't think anyone would disagree wrt tutorials and how tos. I don't think anyone has mentioned D Web Development, which the OP might find a good source.
Re: Why I am switching to Go
On Tuesday, 20 September 2016 at 20:35:49 UTC, Daniel Kozak wrote: Dne 20.9.2016 v 22:01 Karabuta via Digitalmars-d napsal(a): [...] Nothing of this is specific for vibe.d, so I do not see any reason to have doc about this in vibe.d Could he be asking for little examples of the above bullets? Maybe small working examples online?
Re: Why I am switching to Go
Dne 20.9.2016 v 22:59 wobbles via Digitalmars-d napsal(a): On Tuesday, 20 September 2016 at 20:35:49 UTC, Daniel Kozak wrote: 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 I would say otherwise. I've built multiple sites in vibe-d, so I probably wouldn't need them, but having a vibe-d specific beginner tutorial from start to end of a project would be great. Sonke wrote a good blog post a while back with a chat system, and there's a new blogger using vibe too. But we could do with more. I guess I should take that up maybe. Not sure if I have the time though, and I don't have a whole pile of interest in blogging... My fault. I was speaking about doc (API), I do not say anything about tutorial and so on. Yes I belive having more tutorials and howtos it is a good thing.
Re: Why I am switching to Go
On Tuesday, 20 September 2016 at 20:35:49 UTC, Daniel Kozak wrote: 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 I would say otherwise. I've built multiple sites in vibe-d, so I probably wouldn't need them, but having a vibe-d specific beginner tutorial from start to end of a project would be great. Sonke wrote a good blog post a while back with a chat system, and there's a new blogger using vibe too. But we could do with more. I guess I should take that up maybe. Not sure if I have the time though, and I don't have a whole pile of interest in blogging...
Re: Why I am switching to Go
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
Re: Why I am switching to Go
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
Re: Why I am switching to Go
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) :)
Re: Why I am switching to Go
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 :)
Re: Why I am switching to Go
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
Re: Why I am switching to Go
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.
Re: Why I am switching to Go
On Tuesday, 20 September 2016 at 19:16:04 UTC, cym13 wrote: What exactly makes you think vibe is dying? it lacks the documentation?
Re: Why I am switching to Go
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)
Re: Why I am switching to Go
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?
Why I am switching to Go
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.
