Main changes over 0.7.29:

  - Compiles on the latest DMD version (2.068.x-2.072.0)
  - Added a new authorization framework for the web/REST interface
    generators
  - Extended the serialization framework with more hooks and traits,
    enabling the use of custom UDAs - vibe-sdlang [1] is an SDLang
    serialization module that became possible this way
  - opDispatch has been removed from Bson/Json
  - Optional support for using diet-ng [2] has been added and is
    enabled by default for new projects - for existing projects, add
    diet-ng as a dependency or add it to dub.selections.json
  - The HTTP client can now be used on Unix socket destinations
  - Added table support for the Markdown compiler

All changes:
https://vibed.org/blog/posts/vibe-release-0.7.30

DUB package:
https://code.dlang.org/packages/vibe-d/0.7.30

[1]: https://code.dlang.org/packages/vibe-sdlang
[2]: https://code.dlang.org/packages/diet-ng

On Monday, 31 October 2016 at 20:30:22 UTC, Sönke Ludwig wrote:
> Main changes over 0.7.29:
>
>   - Compiles on the latest DMD version (2.068.x-2.072.0)
>   - Added a new authorization framework for the web/REST interface
>     generators
>   - Extended the serialization framework with more hooks and traits,
>     enabling the use of custom UDAs - vibe-sdlang [1] is an SDLang
>     serialization module that became possible this way
>   - opDispatch has been removed from Bson/Json
>   - Optional support for using diet-ng [2] has been added and is
>     enabled by default for new projects - for existing projects, add
>     diet-ng as a dependency or add it to dub.selections.json
>   - The HTTP client can now be used on Unix socket destinations
>   - Added table support for the Markdown compiler
>
> [...]

I'm going to try this out today! :)

On Tuesday, 1 November 2016 at 09:09:05 UTC, Saurabh Das wrote:
> On Monday, 31 October 2016 at 20:30:22 UTC, Sönke Ludwig wrote:
>> [...]
>
> I'm going to try this out today! :)

How can I find out more information about the 'runApplication' change? What does "slowly fading out" mean?

On 2016-11-01 12:20, Saurabh Das wrote:

> How can I find out more information about the 'runApplication' change?
> What does "slowly fading out" mean?

I think it should say something like: "slowly fading out the default main". Instead of having vibe.d define the main function and having a shared module constructor with all the setup, you can define your own main function with all the setup and then call runApplication, which basically contains the same logic as the main function defined by vibe.d.

-- 
/Jacob Carlborg

On 2016-11-01 13:47, Jacob Carlborg wrote:
> On 2016-11-01 12:20, Saurabh Das wrote:
>
>> How can I find out more information about the 'runApplication' change?
>> What does "slowly fading out" mean?
>
> I think it should say something like: "slowly fading out the default
> main". Instead of having vibe.d define the main function and having a
> shared module constructor with all the setup, you can define your own
> main function with all the setup and then call runApplication, which
> basically contains the same logic as the main function defined by vibe.d.

For reference, here's the commit that introduced the change: https://github.com/rejectedsoftware/vibe.d/commit/f7ba59a6c80dc85882654138087bad579480cadf

-- 
/Jacob Carlborg

On Tuesday, 1 November 2016 at 12:47:13 UTC, Jacob Carlborg wrote:
> On 2016-11-01 12:20, Saurabh Das wrote:
>
>> How can I find out more information about the 'runApplication' change?
>> What does "slowly fading out" mean?
>
> I think it should say something like: "slowly fading out the default main". Instead of having vibe.d define the main function and having a shared module constructor with all the setup, you can define your own main function with all the setup and then call runApplication, which basically contains the same logic as the main function defined by vibe.d.

Is "phasing" the word that's being looked for here? I.e. "slowly phasing out the default main".

Am 01.11.2016 um 12:20 schrieb Saurabh Das:
> On Tuesday, 1 November 2016 at 09:09:05 UTC, Saurabh Das wrote:
>> On Monday, 31 October 2016 at 20:30:22 UTC, Sönke Ludwig wrote:
>>> [...]
>>
>> I'm going to try this out today! :)
>
> How can I find out more information about the 'runApplication' change?
> What does "slowly fading out" mean?

A summary would be:

runApplication does the same as runEventLoop, plus performing command line finalization and privilege lowering. This is the same that VibeDefaultMain otherwise does, with the only difference that it is invoked with an explicit function call.

Am 01.11.2016 um 14:29 schrieb John Colvin:
> On Tuesday, 1 November 2016 at 12:47:13 UTC, Jacob Carlborg wrote:
>> On 2016-11-01 12:20, Saurabh Das wrote:
>>
>>> How can I find out more information about the 'runApplication' change?
>>> What does "slowly fading out" mean?
>>
>> I think it should say something like: "slowly fading out the default
>> main". Instead of having vibe.d define the main function and having a
>> shared module constructor with all the setup, you can define your own
>> main function with all the setup and then call runApplication, which
>> basically contains the same logic as the main function defined by vibe.d.
>
> Is "phasing" the word that's being looked for here? I.e. "slowly phasing
> out the default main".

Yes that sounds better. I'll change it and complete that partial sentence.