DIP75 - Release Process

[Rikki Cattermole via Digitalmars-d]

On 11/03/2015 11:04 p.m., Paolo Invernizzi wrote:
> On Wednesday, 11 March 2015 at 08:57:14 UTC, Rikki Cattermole wrote:
>> On 11/03/2015 9:00 p.m., Vladimir Panteleev wrote:
>>> On Wednesday, 11 March 2015 at 07:32:48 UTC, Andrei Alexandrescu wrote:
>>>> It doesn't seem so to me. You find easy weaknesses in my vision and
>>>> pump on them instead of working on making it stronger. That's the easy
>>>> "but that business won't work, and here are the reasons why" approach.
>>>> The harder part is finding ways to make it work by overcoming its
>>>> weaknesses.
>>>
>>> Here is a counter-proposal:
>>>
>>> 1. Add Dub to D.
>>>
>>> 2. Add a "web development" link in the sidebar, which simply links to
>>> vibed.org.
>>>
>>> 3. Add an example on the front page on how to create a simple web
>>> server. It needs to list only main.d and package.json, and the dub
>>> command line to build it. A package.json will be needed for non-trivial
>>> things anyway, so might as well get that out of the way anyway.
>>>
>>> 4. Unite the Vibe.d forum with forum.dlang.org. I should be able to do
>>> this by making forum.dlang.org connect to it via NNTP.
>>>
>>> I think this will achieve much of your goal without the drawbacks.
>>
>> I would like to add putting focus on getting libasync[0] phobos ready
>> instead of the vibe.d direction.
>>
>> It might be a lot younger, but it is also have a lot smaller scope.
>>
>> Perhaps even a rewrite of std.socket to use it?
>>
>> It is a lot of work, but its probably a more manageable unit of work
>> in the short term.
>>
>> [0] https://github.com/etcimon/libasync
>
>
> +100000!!!
>
> and yes, we are using vibe.d in production, but libasync also.
> ---
> Paolo

IMO it makes more sense then vibe.d itself does. Yes vibe.d is what end 
developers will use. But libasync is doing a lot of the lower level work 
needed to make vibe.d useful.

If we can get the low level parts decent, vibe.d will benefit greatly 
from it.