Introducing vibe.d!

[F i L]

On Friday, 27 April 2012 at 20:15:05 UTC, Tove wrote:
> On Friday, 27 April 2012 at 19:40:53 UTC, F i L wrote:
>> "vibe.d" as the project name is great, but why have module 
>> vibe.d and not simply vibe? Or, why prefix all the types with
>
> More complicated projects/frameworks ontop of vibe which 
> implements it's own main is free to use vibe.all.
>
> But I think...
>   import vibe.d;
> ... makes perfect sense because it contains main()!

Ah I see, I was thinking the example wasn't the full code. Still, 
I think doing something like:

     import vibe, vibe.html;

where vibe has main() and vibe.html has html is still better 
semantics.