On Saturday, 29 February 2020 at 08:56:36 UTC, Ron Tarrant wrote:
> On Friday, 28 February 2020 at 22:50:05 UTC, Walter Bright wrote:
>> https://fasterthanli.me/blog/2020/i-want-off-mr-golangs-wild-ride/
>>
>> This is a very worthwhile read. There's a lot for us to learn here.
>
> I tried Go a while back, but when I found that it enforces K&R style to the point of issuing errors if I used Allman-style curly braces, I just lost interest.
>
> Yeah, it doesn't take much. :)

In these kind of languages, you forget about formatting at all. You just set "go fmt" to run on each save in your IDE and then you can put braces however you want and the formatter will set them up in an expected way.

For D I also run dfmt on save and don't really argue with it. I used to be in the "let people code how they want" camp, but nowadays I'm more for consistent formatting, because it's one less barrier when reviewing code from others.

On Saturday, 29 February 2020 at 15:58:28 UTC, JN wrote:
> On Saturday, 29 February 2020 at 08:56:36 UTC, Ron Tarrant wrote:
>> On Friday, 28 February 2020 at 22:50:05 UTC, Walter Bright wrote:
>>> [...]
>>
>> I tried Go a while back, but when I found that it enforces K&R style to the point of issuing errors if I used Allman-style curly braces, I just lost interest.
>>
>> Yeah, it doesn't take much. :)
>
> In these kind of languages, you forget about formatting at all. You just set "go fmt" to run on each save in your IDE and then you can put braces however you want and the formatter will set them up in an expected way.
>
> For D I also run dfmt on save and don't really argue with it. I used to be in the "let people code how they want" camp, but nowadays I'm more for consistent formatting, because it's one less barrier when reviewing code from others.

assuming you only push... what if you need to pull after a PR... formatting does not work.
If you collaborate on FOSS you have to follow the style on a per repo basis.

On Saturday, 29 February 2020 at 10:42:57 UTC, Tove wrote:
> On Saturday, 29 February 2020 at 08:56:36 UTC, Ron Tarrant wrote:
>> On Friday, 28 February 2020 at 22:50:05 UTC, Walter Bright wrote:
>>> https://fasterthanli.me/blog/2020/i-want-off-mr-golangs-wild-ride/
>>>
>>> This is a very worthwhile read. There's a lot for us to learn here.
>>
>> I tried Go a while back, but when I found that it enforces K&R style to the point of issuing errors if I used Allman-style curly braces, I just lost interest.
>>
>> Yeah, it doesn't take much. :)
>
> Funny, I read the spec, when I realized that I wasn't able to use Allman, I instantly ditched GO, didn't even try Hello World to this day.
>
> I thought I was alone.

It's very interesting that syntax is this important to you when D has one of the most complex syntaxes of any language I've written in :)

It's not difficult to break rust path design. It's another go fanboy moved to the next hot thing. Strange why it's not node.js, maybe because he started with node.js.

On Friday, 28 February 2020 at 22:50:05 UTC, Walter Bright wrote:
> https://fasterthanli.me/blog/2020/i-want-off-mr-golangs-wild-ride/
>
> This is a very worthwhile read. There's a lot for us to learn here.

For those wanting to compare D's extensions parsing

          - /
          - /.
          - /.foo
          - /foo
     .txt - /foo.txt
          - /foo.txt/bar
          - C:\
        . - C:\.
     .txt - C:\foo.txt
 .txt\bar - C:\foo.txt\bar

On Saturday, 29 February 2020 at 21:42:09 UTC, Jesse Phillips wrote:
> For those wanting to compare D's extensions parsing
>
>           - /
>           - /.
>           - /.foo
>           - /foo
>      .txt - /foo.txt
>           - /foo.txt/bar
>           - C:\
>         . - C:\.
>      .txt - C:\foo.txt
>  .txt\bar - C:\foo.txt\bar
This makes me sad.

On Saturday, 29 February 2020 at 23:01:57 UTC, asdfasdfasdf wrote:
> On Saturday, 29 February 2020 at 21:42:09 UTC, Jesse Phillips wrote:
>> For those wanting to compare D's extensions parsing
>>
>>           - /
>>           - /.
>>           - /.foo
>>           - /foo
>>      .txt - /foo.txt
>>           - /foo.txt/bar
>>           - C:\
>>         . - C:\.
>>      .txt - C:\foo.txt
>>  .txt\bar - C:\foo.txt\bar
> This makes me sad.

Why? If I was reading his tables correctly it matches close to Rust behavior (we don't provide Some() or None). I didn't run this on Windows to see if behavior changed.

On 2/29/20 7:15 AM, H. S. Teoh wrote:> On Sat, Feb 29, 2020 at 08:56:36AM +0000, Ron Tarrant via Digitalmars-d wrote:

> For me, the fact the Go didn't (and still doesn't) have generics is a
> showstopper for me.

I coded in Go for one year for a microservice security company. After cursing for about two weeks I settled down and went along with whatever idioms Go wanted me to write in. I don't mean lack of features was not important; what I mean is, we humans can adapt any situation.

The fact that Go does not have generics (or templates) is an indication to me of the engineering skills of Go's creators. It's almost advocating "don't use the computer, write it again and again." Well, if they haven't understood the utility of templates, they first need to open their minds and then eat multiple bakery-fulls of bread. (Bad translation of a Turkish saying.)

Ali

On Sunday, 1 March 2020 at 01:43:26 UTC, Ali Çehreli wrote:
> On 2/29/20 7:15 AM, H. S. Teoh wrote:> On Sat, Feb 29, 2020 at 08:56:36AM +0000, Ron Tarrant via Digitalmars-d wrote:
>
> > [...]
> generics is a
> > [...]
>
> [...]

The company you work for, is Go a customer requirement or what blocks the usage of D?

Kind regards
Andre

On Saturday, 29 February 2020 at 20:56:35 UTC, Kagamin wrote:
> It's not difficult to break rust path design. It's another go fanboy moved to the next hot thing. Strange why it's not node.js, maybe because he started with node.js.

Could you elaborate?