On 3/28/2016 3:35 PM, Jin wrote:
> On Monday, 28 March 2016 at 19:29:55 UTC, Walter Bright wrote:
>> On 3/28/2016 6:10 AM, Jin wrote:
>>> My english is too bad to write articles, sorry :-(
>>
>> Baloney, your english is very good. Besides, I'm sure there will be many
>> volunteers here to help you touch it up.
>
> I just wrote the article on russin: https://habrahabr.ru/post/280378/
> Translation to english:
> https://translate.google.com/translate?hl=ru&sl=ru&tl=en&u=https%3A%2F%2Fhabrahabr.ru%2Fpost%2F280378%2F
>

Awesome! Who wants to help with the English?

On 3/28/2016 5:07 PM, Walter Bright wrote:
> On 3/28/2016 3:35 PM, Jin wrote:
>> On Monday, 28 March 2016 at 19:29:55 UTC, Walter Bright wrote:
>>> On 3/28/2016 6:10 AM, Jin wrote:
>>>> My english is too bad to write articles, sorry :-(
>>>
>>> Baloney, your english is very good. Besides, I'm sure there will be many
>>> volunteers here to help you touch it up.
>>
>> I just wrote the article on russin: https://habrahabr.ru/post/280378/
>> Translation to english:
>> https://translate.google.com/translate?hl=ru&sl=ru&tl=en&u=https%3A%2F%2Fhabrahabr.ru%2Fpost%2F280378%2F
>>
>>
>
> Awesome! Who wants to help with the English?

I'll start with the first paragraph (I don't know any Russian):

Google:

Multitasking - this is what is implemented in Go of the good, though not perfect.  Nice syntax with a tart aftertaste, simple and powerful abstraction, bribe its elegance compared to other imperative languages.  And taste the best, so do not want to have to slide to mediocrity.  Therefore, if and switch to another language, it must be even more expressive and with no less sensible multitasking.

English:

Multitasking - Go's multitasking capabilities are good, though not perfect.  It has a nice syntax with a sweet aftertaste, simple and powerful abstraction, elegant compared to other imperative languages.  It exhibits good taste, so one does not wish to compromise into mediocrity.  Therefore, to switch to another language, it must be even more expressive and with no less sensible multitasking.

On 2016-03-29 01:53, Ali Çehreli wrote:

> Seriously, I appreciate any documentation links that you can give to
> complete my "homework" before DConf. :)

I was hoping someone could give _me_ the links, that's why I wrote the post ;)

-- 
/Jacob Carlborg

On Monday, 28 March 2016 at 22:35:12 UTC, Jin wrote:
> On Monday, 28 March 2016 at 19:29:55 UTC, Walter Bright wrote:
>> On 3/28/2016 6:10 AM, Jin wrote:
>>> My english is too bad to write articles, sorry :-(
>>
>> Baloney, your english is very good. Besides, I'm sure there will be many volunteers here to help you touch it up.
>
> I just wrote the article on russin: https://habrahabr.ru/post/280378/
> Translation to english: https://translate.google.com/translate?hl=ru&sl=ru&tl=en&u=https%3A%2F%2Fhabrahabr.ru%2Fpost%2F280378%2F

Create repository on GitHub. So, it will be easier for others to help with translation.

On Monday, 28 March 2016 at 10:49:28 UTC, Jacob Carlborg wrote:
> It would be useful with a wiki page, or similar, that describes and compares different ways of doing concurrency in D, both built-in and third party libraries like this and vibe.d. Also compare against other languages like Go, Erlang, Scala and so on.

+1
Wiki is absolutely the best solution to this, I agree. Plus, we already have a wiki so he should just go there and start writing. The community will incorrect grammar/syntax and typos.

On Tuesday, 29 March 2016 at 12:30:24 UTC, Dejan Lekic wrote:
> +1
> Wiki is absolutely the best solution to this, I agree. Plus, we already have a wiki so he should just go there and start writing. The community will incorrect grammar/syntax and typos.

http://wiki.dlang.org/Go_to_D

On Tuesday, 29 March 2016 at 17:10:02 UTC, Jin wrote:
> On Tuesday, 29 March 2016 at 12:30:24 UTC, Dejan Lekic wrote:
>> +1
>> Wiki is absolutely the best solution to this, I agree. Plus, we already have a wiki so he should just go there and start writing. The community will incorrect grammar/syntax and typos.
>
> http://wiki.dlang.org/Go_to_D

Since I know a bit of Russian, I took a shot at improving this article,
and got partway through the "Channels" section.  But now I need to get
back to work... so hopefully somebody else can work on improving the
English text. :-)


--T

On Sunday, 27 March 2016 at 18:17:55 UTC, Jin wrote:
> DUB module: http://code.dlang.org/packages/jin-go
> GIT repo: https://github.com/nin-jin/go.d
>
> [...]

Have you considered using a Disrupter (http://lmax-exchange.github.io/disruptor/) for the channels?  Not sure how it compares to what you're using from Vibe.d, but it's not a hard data structure to implement and, IIRC, it allows for multiple producers and consumers.

On Wednesday, 30 March 2016 at 14:28:50 UTC, Casey Sybrandy wrote:
> On Sunday, 27 March 2016 at 18:17:55 UTC, Jin wrote:
>> DUB module: http://code.dlang.org/packages/jin-go
>> GIT repo: https://github.com/nin-jin/go.d
>>
>> [...]
>
> Have you considered using a Disrupter (http://lmax-exchange.github.io/disruptor/) for the channels?  Not sure how it compares to what you're using from Vibe.d, but it's not a hard data structure to implement and, IIRC, it allows for multiple producers and consumers.

Oh, and yes, I know that it would have to be rewritten in D unless there's a C version somewhere.  I actually did it once and it wasn't too bad.  I don't think I have a copy anymore, but if I do find it, I can put it up somewhere.

On Wednesday, 30 March 2016 at 15:22:26 UTC, Casey Sybrandy wrote:
>> Have you considered using a Disrupter (http://lmax-exchange.github.io/disruptor/) for the channels?  Not sure how it compares to what you're using from Vibe.d, but it's not a hard data structure to implement and, IIRC, it allows for multiple producers and consumers.
>
> Oh, and yes, I know that it would have to be rewritten in D unless there's a C version somewhere.  I actually did it once and it wasn't too bad.  I don't think I have a copy anymore, but if I do find it, I can put it up somewhere.

This is java bloatware. :-(