• Jesse Phillips (24/24) Jun 22 2018 So I have a tool chain developed utilizing D. It is kind of like
• Bastiaan Veelo (9/33) Jun 24 2018 My $00.02: ideally, your D code should be so easy to read and
• aliak (9/33) Jun 24 2018 Biggest resistance I usually get is around tooling and library
• Vijay Nayar (12/18) Jun 25 2018 One strong argument to make is based on performance. Give them

Jesse Phillips <Jesse.K.Phillips+D gmail.com> writes:

So I have a tool chain developed utilizing D. It is kind of like 
a Linter for what my company does. I started its development back 
in 2009 as a POC for why the company should pursue such a 
concept. That didn't work and I've been utilizing and had a few 
people pick it up and gain value from it.

Recently there is a vitalized effort to look at how we can test 
better, so once again I'm advocating for this Lint like concept 
and of course utilizing my experience with this tool I have used 
over the years.

But it is written in D and we don't have any D developers, we 


that linting is beneficial, which I actually don't think would be 


My argument is going to mainly center around utilizing what 
exists. Once we have more use and a greater need to make 

start there.

Should I be looking more at the benefits of having D as a tool? 
It was a good choice for me since I know D so well (and other 

space. I'm thinking, like should I go into how learning D 
wouldn't be too hard for new hire since it has similar syntax to 

Bastiaan Veelo <Bastiaan Veelo.net> writes:

On Friday, 22 June 2018 at 14:45:46 UTC, Jesse Phillips wrote:
 So I have a tool chain developed utilizing D. It is kind of 
 like a Linter for what my company does. I started its 
 development back in 2009 as a POC for why the company should 
 pursue such a concept. That didn't work and I've been utilizing 
 and had a few people pick it up and gain value from it.

 Recently there is a vitalized effort to look at how we can test 
 better, so once again I'm advocating for this Lint like concept 
 and of course utilizing my experience with this tool I have 
 used over the years.

 But it is written in D and we don't have any D developers, we 


 convince them that linting is beneficial, which I actually 


 My argument is going to mainly center around utilizing what 
 exists. Once we have more use and a greater need to make 

 start there.

 Should I be looking more at the benefits of having D as a tool? 
 It was a good choice for me since I know D so well (and other 

 space. I'm thinking, like should I go into how learning D 
 wouldn't be too hard for new hire since it has similar syntax 


My $00.02: ideally, your D code should be so easy to read and 

going on and learn D from it, by example. If you need to convince 
decision makers, you may want to polish up a subset as a 
showcase. Make the tools so good that the benefits of using them 
are obvious.

Good luck!

Bastiaan.

aliak <something something.com> writes:

On Friday, 22 June 2018 at 14:45:46 UTC, Jesse Phillips wrote:
 So I have a tool chain developed utilizing D. It is kind of 
 like a Linter for what my company does. I started its 
 development back in 2009 as a POC for why the company should 
 pursue such a concept. That didn't work and I've been utilizing 
 and had a few people pick it up and gain value from it.

 Recently there is a vitalized effort to look at how we can test 
 better, so once again I'm advocating for this Lint like concept 
 and of course utilizing my experience with this tool I have 
 used over the years.

 But it is written in D and we don't have any D developers, we 


 convince them that linting is beneficial, which I actually 


 My argument is going to mainly center around utilizing what 
 exists. Once we have more use and a greater need to make 

 start there.

 Should I be looking more at the benefits of having D as a tool? 
 It was a good choice for me since I know D so well (and other 

 space. I'm thinking, like should I go into how learning D 
 wouldn't be too hard for new hire since it has similar syntax 


Biggest resistance I usually get is around tooling and library 
availability - which is not something I can argue for in the face 
of other languages. So if that comes up, I'd be interested to 
know how that went.

Also, "may D force be with you" (has no one made a t-shirt from 
that yet, it's so bad it's good!) :p

Cheers,
- Ali

Vijay Nayar <madric gmail.com> writes:

On Friday, 22 June 2018 at 14:45:46 UTC, Jesse Phillips wrote:
 Should I be looking more at the benefits of having D as a tool? 
 It was a good choice for me since I know D so well (and other 

 space. I'm thinking, like should I go into how learning D 
 wouldn't be too hard for new hire since it has similar syntax 


One strong argument to make is based on performance. Give them 
numbers about how fast your tool runs and make it efficient. The 
idea is that because the linting tool will be run for every 
incremental build a developer makes, slower running times are a 
barrier to productivity.

But once performance targets are defined, and if the company 

their call. Ultimately it is their company and their assets.

In such a case, I would generalize your tool for use outside of 
the specific context of your company, and make it the basis of an 
open source project.