Jump to page: 1 24  
Page
Thread overview
Is the D community lacking development tools?
May 22, 2012
Roman D. Boiko
May 22, 2012
Dejan Lekic
May 22, 2012
Roman D. Boiko
May 22, 2012
Roman D. Boiko
May 22, 2012
H. S. Teoh
May 22, 2012
deadalnix
May 22, 2012
Jacob Carlborg
May 25, 2012
Dejan Lekic
May 25, 2012
Dmitry Olshansky
May 28, 2012
Marco Leise
May 29, 2012
Roman D. Boiko
May 26, 2012
Jacob Carlborg
May 22, 2012
Sean Kelly
May 22, 2012
Michael
May 24, 2012
Sean Kelly
May 25, 2012
Jacob Carlborg
May 25, 2012
simendsjo
May 25, 2012
Jonathan M Davis
May 25, 2012
simendsjo
May 25, 2012
Artur Skawina
May 25, 2012
Paulo Pinto
May 25, 2012
Sean Kelly
May 22, 2012
Jacob Carlborg
May 22, 2012
Roman D. Boiko
May 22, 2012
Jacob Carlborg
May 22, 2012
s
May 22, 2012
Kevin Cox
May 22, 2012
Roman D. Boiko
May 22, 2012
Jacob Carlborg
May 22, 2012
Christian Manning
May 22, 2012
David Nadlinger
May 22, 2012
shd
May 22, 2012
Jacob Carlborg
May 24, 2012
Mikael Lindsten
May 24, 2012
Roman D. Boiko
May 22, 2012
http://d-coding.com/2012/05/22/is-the-d-community-lacking-development-tools.html
May 22, 2012
On Tuesday, 22 May 2012 at 10:03:36 UTC, Roman D. Boiko wrote:
> http://d-coding.com/2012/05/22/is-the-d-community-lacking-development-tools.html

My opinion - no.

We already have:
1) Mono-D, a MonoDevelop plugin - my personal favourite.
2) Code::Blocks - I used it for years, still provides excellent D support.
3) Visual D - for VisualStudio users.
4) DDT - for Eclipse users
5) NetbeansD - for NetBeans users
6) Geany and Kate - for those who want to write a quick D proggy.
7) VIM and Emacs

Sure, all of them can be better, provide more fancy features, etc...

May 22, 2012
On Tuesday, 22 May 2012 at 10:18:48 UTC, Dejan Lekic wrote:
> On Tuesday, 22 May 2012 at 10:03:36 UTC, Roman D. Boiko wrote:
>> http://d-coding.com/2012/05/22/is-the-d-community-lacking-development-tools.html
>
> My opinion - no.
> We already have:
> ...
> 5) NetbeansD - for NetBeans users
Didn't know about that one.


May 22, 2012
On Tuesday, 22 May 2012 at 10:18:48 UTC, Dejan Lekic wrote:
> On Tuesday, 22 May 2012 at 10:03:36 UTC, Roman D. Boiko wrote:
>> http://d-coding.com/2012/05/22/is-the-d-community-lacking-development-tools.html
>
> My opinion - no.
> We already have:
> ...
> 5) NetbeansD - for NetBeans users
Didn't know about that one.


May 22, 2012
On 2012-05-22 12:03, Roman D. Boiko wrote:
> http://d-coding.com/2012/05/22/is-the-d-community-lacking-development-tools.html

I agree with basically everything in that article.

-- 
/Jacob Carlborg
May 22, 2012
On Tuesday, 22 May 2012 at 10:59:04 UTC, Jacob Carlborg wrote:
> On 2012-05-22 12:03, Roman D. Boiko wrote:
>> http://d-coding.com/2012/05/22/is-the-d-community-lacking-development-tools.html
>
> I agree with basically everything in that article.

I would also appreciate any specific feedback
May 22, 2012
On 2012-05-22 13:21, Roman D. Boiko wrote:
> On Tuesday, 22 May 2012 at 10:59:04 UTC, Jacob Carlborg wrote:
>> On 2012-05-22 12:03, Roman D. Boiko wrote:
>>> http://d-coding.com/2012/05/22/is-the-d-community-lacking-development-tools.html
>>>
>>
>> I agree with basically everything in that article.
>
> I would also appreciate any specific feedback

* do you think such project is worth the effort?

Yes

* do you feel that D ecosystem lacks tool support?

Yes

* Does this prevent many from using D?

Probably, not me though

* which tools are needed most? Which may be needed, but are not a high priority for you?

This is quite hard, that is, how to prioritize. This is my list, in no particular order:

* IDE
* Compiler (usable as a library)
* Build tool
* Testing framework
* GUI library
* Tool for automatically create bindings for C/C++/Objective-C
* ABI compatible with Objective-C, i.e. extern(Objective-C)
* Package manager
* Support for iOS

The hard thing is to prioritize. I'm thinking like this:

You need a compiler and an IDE/editor to write any tools. I would like and IDE that is just as good as Eclipse JDT. For that to happen we need a compiler usable as a library. I'm assuming we want to write as much as possible in D so a compiler written in D is necessary. A GUI library would be needed as well.

You would also need a build tool and testing framework to write new tools. Since we want to have everything as modularized and reusable as possible a package manager is also really needed.

If you also want to slap on a GUI on the tools you need a GUI library. For Mac OS X it would be a lot easier to be ABI compatible with Objective-C to create a GUI library.

For most of these tools, in particular: the build tool, testing framework and package manager it would be nice to have the compiler usable as a library. This would allow to have build scripts and other scripts written in D.

So to summarize:

A lot of the tools needed to be built depends on each other but I think most of the tools depend on a compiler, written in D, usable as a library.

* was this post useful? What could I change to make future posts in the series better?

Not really for me, nothing I didn't already know.

* should I add commenting on my blog, or dlang forum is better for that?

I prefer commenting here.

-- 
/Jacob Carlborg
May 22, 2012
On Tue, May 22, 2012 at 12:18:47PM +0200, Dejan Lekic wrote:
> On Tuesday, 22 May 2012 at 10:03:36 UTC, Roman D. Boiko wrote:
> >http://d-coding.com/2012/05/22/is-the-d-community-lacking-development-tools.html
> 
> My opinion - no.
[...]

+1. For me, vim + dmd/gdc is Good Enough(tm). Other tools are nice to
have, but not a must.

Having said that, though, having the reference compiler as a D-callable library would be a big plus (for building pretty printers, code analyzers, etc.).


T

-- 
Computerese Irregular Verb Conjugation: I have preferences.  You have biases.  He/She has prejudices. -- Gene Wirchenko
May 22, 2012
+1 for a GUI lib, which is in sync with DMD releases.


On Tuesday, 22 May 2012 at 12:08:37 UTC, Jacob Carlborg wrote:
> On 2012-05-22 13:21, Roman D. Boiko wrote:
>> On Tuesday, 22 May 2012 at 10:59:04 UTC, Jacob Carlborg wrote:
>>> On 2012-05-22 12:03, Roman D. Boiko wrote:
>>>> http://d-coding.com/2012/05/22/is-the-d-community-lacking-development-tools.html
>>>>
>>>
>>> I agree with basically everything in that article.
>>
>> I would also appreciate any specific feedback
>
> * do you think such project is worth the effort?
>
> Yes
>
> * do you feel that D ecosystem lacks tool support?
>
> Yes
>
> * Does this prevent many from using D?
>
> Probably, not me though
>
> * which tools are needed most? Which may be needed, but are not a high priority for you?
>
> This is quite hard, that is, how to prioritize. This is my list, in no particular order:
>
> * IDE
> * Compiler (usable as a library)
> * Build tool
> * Testing framework
> * GUI library
> * Tool for automatically create bindings for C/C++/Objective-C
> * ABI compatible with Objective-C, i.e. extern(Objective-C)
> * Package manager
> * Support for iOS
>
> The hard thing is to prioritize. I'm thinking like this:
>
> You need a compiler and an IDE/editor to write any tools. I would like and IDE that is just as good as Eclipse JDT. For that to happen we need a compiler usable as a library. I'm assuming we want to write as much as possible in D so a compiler written in D is necessary. A GUI library would be needed as well.
>
> You would also need a build tool and testing framework to write new tools. Since we want to have everything as modularized and reusable as possible a package manager is also really needed.
>
> If you also want to slap on a GUI on the tools you need a GUI library. For Mac OS X it would be a lot easier to be ABI compatible with Objective-C to create a GUI library.
>
> For most of these tools, in particular: the build tool, testing framework and package manager it would be nice to have the compiler usable as a library. This would allow to have build scripts and other scripts written in D.
>
> So to summarize:
>
> A lot of the tools needed to be built depends on each other but I think most of the tools depend on a compiler, written in D, usable as a library.
>
> * was this post useful? What could I change to make future posts in the series better?
>
> Not really for me, nothing I didn't already know.
>
> * should I add commenting on my blog, or dlang forum is better for that?
>
> I prefer commenting here.


May 22, 2012
Le 22/05/2012 12:18, Dejan Lekic a écrit :
> On Tuesday, 22 May 2012 at 10:03:36 UTC, Roman D. Boiko wrote:
>> http://d-coding.com/2012/05/22/is-the-d-community-lacking-development-tools.html
>>
>
> My opinion - no.
>
> We already have:
> 1) Mono-D, a MonoDevelop plugin - my personal favourite.
> 2) Code::Blocks - I used it for years, still provides excellent D support.
> 3) Visual D - for VisualStudio users.
> 4) DDT - for Eclipse users
> 5) NetbeansD - for NetBeans users
> 6) Geany and Kate - for those who want to write a quick D proggy.
> 7) VIM and Emacs
>
> Sure, all of them can be better, provide more fancy features, etc...
>

Refactoring tools ? Static code analysis ? Formaters ?

I'd say, just compare to what exists in Java or C# and you'll know that yes, many things are missing.
« First   ‹ Prev
1 2 3 4