Paulo Pinto wrote:

> Am 03.02.2013 19:58, schrieb bearophile:
>> Dejan Lekic:
>>
>>> In real projects people do the job as best as they
>>> can at the moment,
>>
>> But often there's also some need for:
>>
>> http://en.wikipedia.org/wiki/Code_review
>>
>> Bye,
>> bearophile
> 
> 
> If only most companies I worked for cared about it, or for that matter unit tests. :(

I understand the girl is a researcher. They, especially if they are PhD students, have very strict deadlines, and have milestones to do. Finally, they in most cases work ALONE. With all due respect, but I find it disrespectful to criticise immediately the implementation, especially if it is something pretty serious. Finally, such critic, pull request, suggestion, whatever, should be directed *to the author herself*, or on project's mailing list, bugtrack, etc instead of posting here. Don't you agree?

-- 
Dejan Lekic
dejan.lekic (a) gmail.com
http://dejan.lekic.org

Nick Sabalausky wrote:

> On Sun, 03 Feb 2013 22:15:09 +0100
> "Michael" <pr@m1xa.com> wrote:
> 
>> Best code, it's which works and the client is satisfied.
> 
> And the end users are satisfied. AND doesn't cause problems when it inevitably needs maintenance. And isn't prone to crapping out or breaches of security.

AND you expect that from ONE, single person who is implementing something like Higgs? :) Come on, be realistic...

-- 
Dejan Lekic
dejan.lekic (a) gmail.com
http://dejan.lekic.org

On Monday, 4 February 2013 at 19:19:06 UTC, Dejan Lekic wrote:
> Nick Sabalausky wrote:
>
>> On Sun, 03 Feb 2013 22:15:09 +0100
>> "Michael" <pr@m1xa.com> wrote:
>> 
>>> Best code, it's which works and the client is satisfied.
>> 
>> And the end users are satisfied. AND doesn't cause problems when it
>> inevitably needs maintenance. And isn't prone to crapping out or
>> breaches of security.
>
> AND you expect that from ONE, single person who is implementing something like
> Higgs? :) Come on, be realistic...

Yes, you are right. But it's all is just nuances )))

P.S.: For completeness ;)

Am 04.02.2013 20:16, schrieb Dejan Lekic:
> Paulo Pinto wrote:
>
>> Am 03.02.2013 19:58, schrieb bearophile:
>>> Dejan Lekic:
>>>
>>>> In real projects people do the job as best as they
>>>> can at the moment,
>>>
>>> But often there's also some need for:
>>>
>>> http://en.wikipedia.org/wiki/Code_review
>>>
>>> Bye,
>>> bearophile
>>
>>
>> If only most companies I worked for cared about it, or for
>> that matter unit tests. :(
>
> I understand the girl is a researcher. They, especially if they are PhD
> students, have very strict deadlines, and have milestones to do. Finally, they
> in most cases work ALONE. With all due respect, but I find it disrespectful to
> criticise immediately the implementation, especially if it is something pretty
> serious. Finally, such critic, pull request, suggestion, whatever, should be
> directed *to the author herself*, or on project's mailing list, bugtrack, etc
> instead of posting here. Don't you agree?
>

100%

On Monday, 4 February 2013 at 20:08:32 UTC, Paulo Pinto wrote:
> Am 04.02.2013 20:16, schrieb Dejan Lekic:
>> Paulo Pinto wrote:
>>
>>> Am 03.02.2013 19:58, schrieb bearophile:
>>>> Dejan Lekic:
>>>>
>>>>> In real projects people do the job as best as they
>>>>> can at the moment,
>>>>
>>>> But often there's also some need for:
>>>>
>>>> http://en.wikipedia.org/wiki/Code_review
>>>>
>>>> Bye,
>>>> bearophile
>>>
>>>
>>> If only most companies I worked for cared about it, or for
>>> that matter unit tests. :(
>>
>> I understand the girl is a researcher. They, especially if they are PhD
>> students, have very strict deadlines, and have milestones to do. Finally, they
>> in most cases work ALONE. With all due respect, but I find it disrespectful to
>> criticise immediately the implementation, especially if it is something pretty
>> serious. Finally, such critic, pull request, suggestion, whatever, should be
>> directed *to the author herself*, or on project's mailing list, bugtrack, etc
>> instead of posting here. Don't you agree?
>>
>
> 100%

I agree too.

But one thing that I saw is we should getting happy to see another project using D, but the focus went to her code instead!

Let's take easy, and be glad that she is promoting D.

And by the way, the project looks awesome!

On Sunday, 3 February 2013 at 21:05:57 UTC, Peter Alexander wrote:
> On Sunday, 3 February 2013 at 18:24:05 UTC, Dejan Lekic wrote:
>> Welcome to reality Bearophile!!!
>>
>> In real projects people do the job as best as they can at the moment, and they probably, and with right, do not care what people who only theorise, criticise, and philosophise think! You write perfect code?! I doubt! And if you do, you will probably never finish any serious project in time!
>
> That's besides the point. If people aren't using a feature of the language (e.g. contracts or const) then perhaps it is a sign of problems with those features, whether it be technical, or lack of tutorial, or poor documentation etc. I don't know if it is, but I find it interesting to observe how people use the language in real code.

Good points.

In the case at hand, the researcher is likely not expecting to re-use the code or maintain it past the projects termination point, so it's most likely a quick and dirty job. In fact she mentions that no attempts were made to optimize for performance because it's a proof of concept, which suggests throw away code.

BTW, I've been digging away on D for a few months now, and have written a fair amount of D code, yet I still have not explored all of the languages features and even after I've looked at everything it's very likely I will not use all of the available features because it's very likely not all of it will add enough value, and may even complicate matters in practice more than it promises to simplify in theory.

--rt

It would be nice to know why she choose D.

Possibly the reason is because she wanted to write code quickly, which is one of the advantages that D is supposed to provide over some other languages.

--rt

On Monday, 4 February 2013 at 23:02:04 UTC, MattCoder wrote:
> On Monday, 4 February 2013 at 20:08:32 UTC, Paulo Pinto wrote:
>> Am 04.02.2013 20:16, schrieb Dejan Lekic:
>>> Paulo Pinto wrote:
>>>
>>>> Am 03.02.2013 19:58, schrieb bearophile:
>>>>> Dejan Lekic:
>>>>>
>>>>>> In real projects people do the job as best as they
>>>>>> can at the moment,
>>>>>
>>>>> But often there's also some need for:
>>>>>
>>>>> http://en.wikipedia.org/wiki/Code_review
>>>>>
>>>>> Bye,
>>>>> bearophile
>>>>
>>>>
>>>> If only most companies I worked for cared about it, or for
>>>> that matter unit tests. :(
>>>
>>> I understand the girl is a researcher. They, especially if they are PhD
>>> students, have very strict deadlines, and have milestones to do. Finally, they
>>> in most cases work ALONE. With all due respect, but I find it disrespectful to
>>> criticise immediately the implementation, especially if it is something pretty
>>> serious. Finally, such critic, pull request, suggestion, whatever, should be
>>> directed *to the author herself*, or on project's mailing list, bugtrack, etc
>>> instead of posting here. Don't you agree?
>>>
>>
>> 100%
>
> I agree too.
>
> But one thing that I saw is we should getting happy to see another project using D, but the focus went to her code instead!
>
> Let's take easy, and be glad that she is promoting D.
>
> And by the way, the project looks awesome!

I absolutely agree.

On 02/03/2013 08:56 AM, bearophile wrote:
> text() is shorter than to!string(),

In all fairness, I wasn't aware of text until this comment, so perhaps the author was not either?

For the curious, I found docs here, since I now knew what I was looking for:

http://dlang.org/phobos/std_conv.html#.text


-- 
Matthew Caron, Software Build Engineer
Sixnet, a Red Lion business | www.sixnet.com
+1 (518) 877-5173 x138 office

On 02/03/2013 01:58 PM, bearophile wrote:
> Dejan Lekic:
>
>> In real projects people do the job as best as they
>> can at the moment,
>
> But often there's also some need for:
>
> http://en.wikipedia.org/wiki/Code_review

Which is very difficult when attempting to bootstrap a new language into a company, to say nothing of working on some random project. I have that issue at work now - code is reviewed by C programmers, so they won't be able to compare one D idiom to another because they're not aware of either of them.

-- 
Matthew Caron, Software Build Engineer
Sixnet, a Red Lion business | www.sixnet.com
+1 (518) 877-5173 x138 office