Changes:

 - Refactored the MongoDB client to better match the actual database
   structure + range interface for query results (by Dicebot)

 - A number of important fixes in the HttpClient and ConnectionPool

 - Correct memory alignment is now enforced in the custom memory allocators
   (Caused exceptions on 32-bit Linux)

 - Added task management methods (interrupt(), join() and running)

 - Lots of smaller fixes and enhancements

Full change log: http://vibed.org/blog/posts/vibe-release-0.7.12 Download: http://vibed.org/download?file=vibed-0.7.12.zip GitHub: https://github.com/rejectedsoftware/vibe.d

Al 11/02/13 12:53, En/na Sönke Ludwig ha escrit:
> Changes:
> 
>  - Refactored the MongoDB client to better match the actual database
>    structure + range interface for query results (by Dicebot)
> 
>  - A number of important fixes in the HttpClient and ConnectionPool
> 
>  - Correct memory alignment is now enforced in the custom memory allocators
>    (Caused exceptions on 32-bit Linux)
> 
>  - Added task management methods (interrupt(), join() and running)
> 
>  - Lots of smaller fixes and enhancements
> 
> Full change log: http://vibed.org/blog/posts/vibe-release-0.7.12 Download: http://vibed.org/download?file=vibed-0.7.12.zip GitHub: https://github.com/rejectedsoftware/vibe.d
> 

Congratulations for this new release Sönke! Great work!

-- 
Jordi Sayol

On 02/11/2013 03:53 AM, Sönke Ludwig wrote:

> Full change log: http://vibed.org/blog/posts/vibe-release-0.7.12
> Download: http://vibed.org/download?file=vibed-0.7.12.zip
> GitHub: https://github.com/rejectedsoftware/vibe.d

Great work! :)

I use vibe.d as an example of how useful a tool D is. Recently, somebody has shown me a web server code written in Python: It was in 14 lines, could you belive it? Well, I've responded back with a vibe.d example. It was basically the same code as Python, translated to D. Of course, the solution that use vibe.d does not have Python's infamous GIL; instead, it comes with parallelism and concurrency out of the box. And you are aware of typos in your code even before running your program. ;)

Ali

Great project -- a flagship example of D's real world application!

On 2013-02-11 19:11, Ali Çehreli wrote:
> same code as Python, translated to D. Of course, the solution that use vibe.d
> does not have Python's infamous GIL; instead, it comes with parallelism and
> concurrency out of the box. And you are aware of typos in your code even before
> running your program. ;)

Running worker processes can make the GIL problem a little less of a PITA, but having the typos pointed out before running the app... is just priceless. :)

I'm struggling with the temptation to move a Python website to vibe.d.
What keeps me from doing that are Django templates. Not even because vibe's templates have to be recompiled each time some small markup change is introduced -- I got used to that with LaTeX ;) -- but because of Jade. It's way too far off course from HTML for my tastes. I see no reason for inventing a completely new format when all you need is templating.

So let me use this opportunity to ask you: is somebody working on other template systems for vibe.d already or shall I get involved myself? I'm thinking about something similar to this, syntax-wise: http://jinja.pocoo.org/

On Monday, 11 February 2013 at 19:08:16 UTC, FG wrote:
> Great project -- a flagship example of D's real world application!
>
> On 2013-02-11 19:11, Ali Çehreli wrote:
>> same code as Python, translated to D. Of course, the solution that use vibe.d
>> does not have Python's infamous GIL; instead, it comes with parallelism and
>> concurrency out of the box. And you are aware of typos in your code even before
>> running your program. ;)
>
> Running worker processes can make the GIL problem a little less of a PITA, but having the typos pointed out before running the app... is just priceless. :)
>
> I'm struggling with the temptation to move a Python website to vibe.d.
> What keeps me from doing that are Django templates. Not even because vibe's templates have to be recompiled each time some small markup change is introduced -- I got used to that with LaTeX ;) -- but because of Jade. It's way too far off course from HTML for my tastes. I see no reason for inventing a completely new format when all you need is templating.
>
> So let me use this opportunity to ask you: is somebody working on other template systems for vibe.d already or shall I get involved myself? I'm thinking about something similar to this, syntax-wise: http://jinja.pocoo.org/

I'm working on porting Twig (http://twig.sensiolabs.org/) to D (so I can use it with vibe.d) but I'm still far even from a preview release.. I'm hoping to have more spare time in upcoming months to implement at least small usable subset of Twig features.

I will post in this forum/NG once I have something to show..

On 2013-02-11 20:40, Aleksandar Ruzicic wrote:
> I'm working on porting Twig (http://twig.sensiolabs.org/) to D (so I can use it
> with vibe.d) but I'm still far even from a preview release.. I'm hoping to have
> more spare time in upcoming months to implement at least small usable subset of
> Twig features.

Splendid. Tell me if you need help with that.

On Mon, 2013-02-11 at 10:11 -0800, Ali Çehreli wrote: […]
> I use vibe.d as an example of how useful a tool D is. Recently, somebody has shown me a web server code written in Python: It was in 14 lines, could you belive it? Well, I've responded back with a vibe.d example. It was basically the same code as Python, translated to D. Of course, the solution that use vibe.d does not have Python's infamous GIL; instead, it comes with parallelism and concurrency out of the box. And you are aware of typos in your code even before running your program. ;)

Python is not being compared to D here, vibe.d is being compared to <what?> Flask, Bottle,…

I would suggest that vibe.d can be a real competitor in the Flask, Sinatra, Ratpack, etc. in the microframework space. But it needs the word spreading, which means serious applications mentioned in Python, Ruby, Groovy, and Go mailing lists. Issues about Python GIL are irrelevant (even if true) as people just use process pools via multiprocessing or concurrent.futures. It is important to not obviously compare apples with wing nuts ;-)

Connections to SQL, MongoDB, Cassandra, Redis, Neo4J, etc. and templating engines are the real kicker here not the even loop.  If it's all in place get the marketing material in place and let the presses roll.

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

On 2013-02-11 20:08, FG wrote:
> Great project -- a flagship example of D's real world application!
>
> On 2013-02-11 19:11, Ali Çehreli wrote:
>> same code as Python, translated to D. Of course, the solution that use
>> vibe.d
>> does not have Python's infamous GIL; instead, it comes with
>> parallelism and
>> concurrency out of the box. And you are aware of typos in your code
>> even before
>> running your program. ;)
>
> Running worker processes can make the GIL problem a little less of a
> PITA, but having the typos pointed out before running the app... is just
> priceless. :)
>
> I'm struggling with the temptation to move a Python website to vibe.d.
> What keeps me from doing that are Django templates. Not even because
> vibe's templates have to be recompiled each time some small markup
> change is introduced -- I got used to that with LaTeX ;) -- but because
> of Jade. It's way too far off course from HTML for my tastes. I see no
> reason for inventing a completely new format when all you need is
> templating.
>
> So let me use this opportunity to ask you: is somebody working on other
> template systems for vibe.d already or shall I get involved myself? I'm
> thinking about something similar to this, syntax-wise:
> http://jinja.pocoo.org/

I like Haml, it's similar to Jade but without the pipes for the plain text.

What about plain HTML, like Ruby (Erb) or PHP uses.

-- 
/Jacob Carlborg

On Mon, 11 Feb 2013 20:11:13 +0000
Russel Winder <russel@winder.org.uk> wrote:

> On Mon, 2013-02-11 at 10:11 -0800, Ali Çehreli wrote: […]
> > I use vibe.d as an example of how useful a tool D is. Recently, somebody has shown me a web server code written in Python: It was in 14 lines, could you belive it? Well, I've responded back with a vibe.d example. It was basically the same code as Python, translated to D. Of course, the solution that use vibe.d does not have Python's infamous GIL; instead, it comes with parallelism and concurrency out of the box. And you are aware of typos in your code even before running your program. ;)
> 
> Python is not being compared to D here, vibe.d is being compared to <what?> Flask, Bottle,…
> 

The "aware of typos in your code even before running your program" is definitely a direct Python vs D thing. And it's a huge deal, IMO (And yea, I'm saying that after having [tried to] use Python/Bottle).

> I would suggest that vibe.d can be a real competitor in the Flask, Sinatra, Ratpack, etc. in the microframework space. But it needs the word spreading, which means serious applications mentioned in Python, Ruby, Groovy, and Go mailing lists. Issues about Python GIL are irrelevant (even if true) as people just use process pools via multiprocessing or concurrent.futures. It is important to not obviously compare apples with wing nuts ;-)
> 

While I agree that Vibe.d vs Flask/DJango/etc is the bigger comparison
here, I think GIL is still relevant: With the Python-based
stuff (as far as I'm aware), it's something that has to be actively
worked around. When I tried to use Python/Bottle, I didn't even *know*
how to do that ('Course, I'm not super-experienced with Python - and
hope to never be - but still.) With D/Vibe.d, OTOH, GIL is simply
a non-issue period.

On 2013-02-11 21:11, Russel Winder wrote:
> Python is not being compared to D here, vibe.d is being compared to
> <what?> Flask, Bottle,…

Who knows, maybe Python was being compared. You can have a nice HTTP server in Python in 0 lines of code, by running: python -m SimpleHTTPServer   :)

> Issues about Python GIL are irrelevant (even if true) as people just use
> process pools via multiprocessing or concurrent.futures.

Exactly, for example spawn a few processes with uWSGI and the Python script doesn't have to deal with multithreading or even use greenlets. So in most of the cases there is no GIL issue... unless you really need multithreading for a fast web service keeping internal states and locks, entering a no-python land.

> Connections to SQL, MongoDB, Cassandra, Redis, Neo4J, etc. and
> templating engines are the real kicker here not the even loop.  If it's
> all in place get the marketing material in place and let the presses
> roll.

Yeah, a sane templating engine is a must. Once you have those things covered, you can win people over by playing to the performance tune. They love that.
Of course having a big traffic site using it would help a lot.