On 2012-11-02 09:45, Lubos Pintes wrote:
> It could be something like .NET assembly, i.e. everything needed is in

I'm not sure I understand. Would you build a dynamic library with all the functionality and a thin wrapper just to make it an executable?

-- 
/Jacob Carlborg

On 2012-11-02 12:27, Sönke Ludwig wrote:

> I haven't used shared libs in conjunction with vibe.d, but in a LLVM
> based compiler project that was compiled as a DLL (where PIC is not
> required). For OS X I dodged the PIC problems by compiling it as a
> static library.

On Mac OS X PIC is the default, no problems :)

-- 
/Jacob Carlborg

On Fri, 02 Nov 2012 18:28:55 +0100
Faux Amis <faux@amis.com> wrote:

> On 02/11/2012 00:14, Nick Sabalausky wrote:
> >
> > If you're not scared off of node.js yet, read this: https://semitwist.com/mirror/node-js-is-cancer.html  (The original link is dead, so I have it mirrored there, minus the CSS so it looks ugly, sorry.)
> 
> I actually read that website when I tried out node.js. I thought vibe.d would suffer the same locking behaviour.
> 

It can if you're not careful, Ted is right about that. However, IMO it's less of an issue with Vibe.d because using its I/O will automatically yield to other requests running in their own fibers. Plus D code just simply executes much faster than JS, even if it is V8 JS.

Also, the "event loop with built in HTTP server" approach *can* also make it easier to write fast servers because unlike CGI-style it's a lot easier to cache stuff in memory.

On Friday, 2 November 2012 at 22:21:42 UTC, Nick Sabalausky wrote:
> Also, the "event loop with built in HTTP server" approach *can* also make it easier to write fast servers because unlike CGI-style it's a lot easier to cache stuff in memory.

Of course, that's a double edged sword too because it isn't hard to accidentally inject bizarre cross-request bugs.

This is one of the reasons I still use classic CGI on most my live apps, despite being able to use a long lived process with just a recompile with my lib: it is just easier to ensure stability with the process separation.

On 2012-10-31 12:30, Jordi Sayol wrote:

> 
> Congratulations for this new release!
> 
> New deb packages for vibe v0.7.9 available at https://code.google.com/p/d-apt/
> 

When I make an apt-get update I get.


W: Failed to fetch http://d-apt.googlecode.com/files/Release  Unable to find expected entry 'Sources' in Release file (Wrong sources.list entry or malformed file)

I anyone else getting this ?

Al 07/11/12 11:24, En/na Knud Soerensen ha escrit:
> On 2012-10-31 12:30, Jordi Sayol wrote:
> 
>>
>> Congratulations for this new release!
>>
>> New deb packages for vibe v0.7.9 available at https://code.google.com/p/d-apt/
>>
> 
> When I make an apt-get update I get.
> 
> 
> W: Failed to fetch http://d-apt.googlecode.com/files/Release  Unable to find expected entry 'Sources' in Release file (Wrong sources.list entry or malformed file)
> 
> I anyone else getting this ?
> 

d-apt do not have debianized source packages.

Try to comment or delete the line "deb-src http://d-apt.googlecode.com/files /" in "/etc/apt/sources.list" file, or in any file inside "/etc/apt/sources.list.d/" directory.

Regards,
-- 
Jordi Sayol

On 2012-11-07 11:59, Jordi Sayol wrote:
> Al 07/11/12 11:24, En/na Knud Soerensen ha escrit:
>> On 2012-10-31 12:30, Jordi Sayol wrote:
>>
>>>
>>> Congratulations for this new release!
>>>
>>> New deb packages for vibe v0.7.9 available at https://code.google.com/p/d-apt/
>>>
>>
>> When I make an apt-get update I get.
>>
>>
>> W: Failed to fetch http://d-apt.googlecode.com/files/Release  Unable to find expected entry 'Sources' in Release file (Wrong sources.list entry or malformed file)
>>
>> I anyone else getting this ?
>>
> 
> d-apt do not have debianized source packages.
> 
> Try to comment or delete the line "deb-src http://d-apt.googlecode.com/files /" in "/etc/apt/sources.list" file, or in any file inside "/etc/apt/sources.list.d/" directory.
> 
> Regards,
> 

Thanks, that worked.

-- 
Join me on
Skype	   knudhs
Facebook   http://www.facebook.com/profile.php?id=1198821880
Linkedin   http://www.linkedin.com/pub/0/117/a54
Twitter    http://twitter.com/knudsoerensen
bitcoin donations: 13ofyUKqFL43uRJHZtNozyMVP4qxKPsAR2