I wonder what kind of programming people plan or _hope_ to use D for in 2016?

Do you have plans to:

1. migrate legacy C++ code bases to D when C++ bindings are final?

2. integrate with numerical solutions like TensorFlow?

3. create web services with vibe.d?

4. run D apps in the cloud?

5. run D apps on mobile?

6. create runtime less programs (games, embedded)?

7. work on the D language/phobos ?

8. or something else?


What other languages do you think you will use or toy with in 2016 and for what purpose?

What would it take for you to use D instead, or what changes would be needed for you to move from language X to D?

In the next couple of days I'll be doing a feedback thread on my windowing and image library.
After that I hope to see it to completion.

Maybe some web development and assembly related stuff!

On Tuesday, 5 January 2016 at 12:33:54 UTC, Rikki Cattermole wrote:
> In the next couple of days I'll be doing a feedback thread on my windowing and image library.
> After that I hope to see it to completion.

Cool! Are you going to use the libraries for an application?

> Maybe some web development and assembly related stuff!

What kind of assembly related things are you interested in? Would WebAssembly/asm.js be interesting? If someone is interested in creating a compiler for a small subset of D to WebAssembly/asm.js then I'd like to participate. Something small enough to be completed quickly (meaning "sunday programming").

Here are my (hopeful, given enough spare time) plans for D:

1. Code up a new experimental unicode-syntax for a subset of D now that the C++ to D transition is "complete", with a fair selection of unicode operators and symbols (e.g. "π", "∑", "≤", "≠" etc).

2. Toying with WebAssembly.

3. Finish some basic libraries for memory-slicing, queues, hashes and so.

I probably can't use D for any work related in 2016 :-/. For work I probably will continue to use C/C++/Objective-C++ (iOS/asm.js), Python (web), Go(web), TypeScript(web) and maybe adopt Angular2, Swift(iOS).

On the web side I am locked down to these language because of tooling and infrastructure support. On the iOS side tooling prevents adoption of non-Apple tech.

The only work-related area where I can use D (or Rust) in 2016 is runtime less asm.js for high performance web client engines. But neither D (or Rust) has asm.js support yet, so... I might dabble with that.

On Tuesday, 5 January 2016 at 12:27:12 UTC, Ola Fosheim Grøstad wrote:
> I wonder what kind of programming people plan or _hope_ to use D for in 2016?
>
> Do you have plans to:
>
> 1. migrate legacy C++ code bases to D when C++ bindings are final?
>
> 2. integrate with numerical solutions like TensorFlow?
>
> 3. create web services with vibe.d?
>
> 4. run D apps in the cloud?
>
> 5. run D apps on mobile?
>
> 6. create runtime less programs (games, embedded)?
>
> 7. work on the D language/phobos ?
>
> 8. or something else?
>
>
> What other languages do you think you will use or toy with in 2016 and for what purpose?
>
> What would it take for you to use D instead, or what changes would be needed for you to move from language X to D?

I plan on using the new Android support to build a mobile app entirely in D, with some components running on the server, ie "cloud," at least initially.  I'll probably bind to some existing C libraries, but no C++.  Hopefully I'm done working on the language/phobos, as most of the Android support is in, and I don't have anything else to add.

I don't anticipate nor want to use any other language, but I suspect I'll be forced to call some minimal Java through JNI, for a few native Android APIs that are Java-only and that I might need.

On 06/01/16 2:21 AM, Ola Fosheim Grøstad wrote:
> On Tuesday, 5 January 2016 at 12:33:54 UTC, Rikki Cattermole wrote:
>> In the next couple of days I'll be doing a feedback thread on my
>> windowing and image library.
>> After that I hope to see it to completion.
>
> Cool! Are you going to use the libraries for an application?

Not currently, we just need infrastructure first.

>> Maybe some web development and assembly related stuff!
>
> What kind of assembly related things are you interested in? Would
> WebAssembly/asm.js be interesting? If someone is interested in creating
> a compiler for a small subset of D to WebAssembly/asm.js then I'd like
> to participate. Something small enough to be completed quickly (meaning
> "sunday programming").

Mostly sljit/glulx.
Basically I want to study more assembly in general.
With the hope of killing off dmd-be *evil grin*.

The only other adaptation is using sljit to create a jit'd version of a tree graph for web application server (routing).

> Here are my (hopeful, given enough spare time) plans for D:
>
> 1. Code up a new experimental unicode-syntax for a subset of D now that
> the C++ to D transition is "complete", with a fair selection of unicode
> operators and symbols (e.g. "π", "∑", "≤", "≠" etc).
>
> 2. Toying with WebAssembly.
>
> 3. Finish some basic libraries for memory-slicing, queues, hashes and so.
>
> I probably can't use D for any work related in 2016 :-/. For work I
> probably will continue to use C/C++/Objective-C++ (iOS/asm.js), Python
> (web), Go(web), TypeScript(web) and maybe adopt Angular2, Swift(iOS).
>
> On the web side I am locked down to these language because of tooling
> and infrastructure support. On the iOS side tooling prevents adoption of
> non-Apple tech.
>
> The only work-related area where I can use D (or Rust) in 2016 is
> runtime less asm.js for high performance web client engines. But neither
> D (or Rust) has asm.js support yet, so... I might dabble with that.
>

On Tuesday, 5 January 2016 at 13:24:58 UTC, Joakim wrote:
> I plan on using the new Android support to build a mobile app entirely in D, with some components running on the server, ie "cloud," at least initially.
[...]
> I don't anticipate nor want to use any other language, but I suspect I'll be forced to call some minimal Java through JNI, for a few native Android APIs that are Java-only and that I might need.

Neat! Does this mean that you might be able to do commercial stuff with D on Android this year?

Keep working on Linux GTK applications using GtkD including:

* Finish my tiling terminal emulator, terminix (https://github.com/gnunn1/terminix)

* Take a shot at doing a Linux chat/IM application following the gnome-chat design

On Tuesday, 5 January 2016 at 13:42:26 UTC, Ola Fosheim Grøstad wrote:
> On Tuesday, 5 January 2016 at 13:24:58 UTC, Joakim wrote:
>> I plan on using the new Android support to build a mobile app entirely in D, with some components running on the server, ie "cloud," at least initially.
> [...]
>> I don't anticipate nor want to use any other language, but I suspect I'll be forced to call some minimal Java through JNI, for a few native Android APIs that are Java-only and that I might need.
>
> Neat! Does this mean that you might be able to do commercial stuff with D on Android this year?

Only in the sense that it will have a paid component, but it's just something I'll be doing on my own.

On Tuesday, 5 January 2016 at 13:43:32 UTC, Gerald wrote:
> Keep working on Linux GTK applications using GtkD including:
>
> * Finish my tiling terminal emulator, terminix (https://github.com/gnunn1/terminix)

Nice, you should put that on dub.

I know I'll be doing a few web programs in D (already have the contracts so it is increasing in priority even now). I'll probably be expanding my css tools for my other job too.

For non-work stuff, it all depends on how much time I have, but the basic list is:

1) the doc thing I've been talking about endlessly

2) improve D error messages. dmd "no template matches" and druntime "RangeError" are both sucky because they don't tell the user important facts the computer knows.

3) write a cocoa implementation for simpledisplay

4) get minigui up to 1.0

5) finish at least one of my games

> What other languages do you think you will use or toy with in 2016 and for what purpose?

I'll still be using Ruby, Python, Java, and of course, Javascript for other work things too.

> What would it take for you to use D instead, or what changes would be needed for you to move from language X to D?

My D program for work has a major component in Java which I just wrote last month because I wanted to use a major Java library and it was easier to just write it right there than mess with JNI or whatever.

If D had the same Java interface out of the box, or the same cutting-edge library I might have use it there too, but meh, idk. It is just a simple server that spits out XML - something Java is very good at.

On Tuesday, 5 January 2016 at 13:43:32 UTC, Gerald wrote:
> * Finish my tiling terminal emulator, terminix (https://github.com/gnunn1/terminix)

ooh, I wrote a terminal emulator too a while ago:

https://github.com/adamdruppe/terminal-emulator

If any of my code would be useful to you, always feel free to copy it.