On Wednesday, 6 January 2016 at 11:16:20 UTC, Chris wrote:
> Don't think I'll have time for that and once you use D, you lose interest in other languages :-)

Amen to that.
Had to write some Java recently and kept trying to go call functions UFCS style.

And if I have to match up angle brackets for a generic list of a generic list of a generic type one more time I'll poke my eyes out!

On Wednesday, 6 January 2016 at 11:16:20 UTC, Chris wrote:
> Don't think I'll have time for that and once you use D, you lose interest in other languages :-)

I legitimately cannot use C++ anymore after using D, especially anything related to template/compile-time metaprogramming.

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:
>
> 6. create runtime less programs (games, embedded)?
Am currently knee deep in my first game in D. Using DTiled and DSFML, has been very fun so far.
A rogue-like nomadic city-builder. (That's a thing?!)

> 7. work on the D language/phobos ?
I don't have the knowledge or skills sadly. I will attempt to help out on the  documentation at some stage.

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

Been using Groovy more and more in work.
Will also sadly have to write Java code for some in-house Jenkins plugins.

Personally, I've been using D a lot more in work recently, and quick and dirty tools I need I always go to D first.
One example, we use sysstat to monitor all our servers resource usage, and had no centralised way to view those stats. I wrote a vibe.d service to do just that, plotting the data via plotly.js.
I might clean it up and put it up on Github actually... could be useful to someone.

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:
>
>
> 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've been lurking here for a long time, but this year I need to actually do some projects in D and learn it in the process.

Things on my wish list:

1. Write some data processing code in D for work. Currently I'm using Python/C++, and D would be a very good replacement. If things turn out good, I may become a happy D-at-work coder :)

2. Make a working prototype of my toy language, Venus, in D. (https://github.com/zhaopuming/Venus)

3. Learn about SDC and hopefully make some contributions. Venus is implemented based on SDC design/code.

4. Dive into dlangui/dlangide, and make a simple repl/editor for my language with them.

On 2016-01-05 13:27, Ola Fosheim Grøstad wrote:

> 3. create web services with vibe.d?

I would like to try for work.

> 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 ?

* I'm currently working on native TLS for OS X. Hopefully it will be ready soon, if I can manage to solve the remaining bug(s)

* At some point I need to get std.serialization ready
* Get more of the Objective-C support into upstream

> 8. or something else?

In no particular order:

* JPort, a tool to convert Java to D, for DWT - Not written in D though
* Fixing bugs in the D TextMate grammar, used by GitHub as well
* Enhancing the D TextMate bundle, i.e. adding support for DCD
* Maintaining existing projects, DVM, DStep, DWT

Probably some other stuff I can't recall right now.

> 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?

For work that would mean libraries for connecting to PostgreSQL and RabbitMQ. Ideally compatible with vibe.d.

-- 
/Jacob Carlborg

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?
>
> 8. or something else?

The toy language bug has bitten me, too. I'm going for maximum modularity in the compiler to make it easy to hook in fancy tools.

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

Probably a lot of C++ for my computer science classes.

> 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?

Some very forward-thinking professors. ;)

On Tuesday, 5 January 2016 at 12:27:12 UTC, Ola Fosheim Grøstad wrote:
> 2. integrate with numerical solutions like TensorFlow?

I'm currently working on something along the same lines as TensorFlow -- I started work on this before TensorFlow was announced. I haven't thought too much about writing a distributed backend, but currently there are some reasonably inefficient proof-of-concept CPU and CUDA backends.

It's still fairly early on in development, and I'm more of an academic than an engineer. That said, I've managed to train some modestly sized convolutional networks without trouble.

I'll open source it at some point, but I haven't got a time-frame for that.

On Wednesday, 6 January 2016 at 11:54:01 UTC, wobbles wrote:
> Personally, I've been using D a lot more in work recently, and quick and dirty tools I need I always go to D first.
> One example, we use sysstat to monitor all our servers resource usage, and had no centralised way to view those stats. I wrote a vibe.d service to do just that, plotting the data via plotly.js.
> I might clean it up and put it up on Github actually... could be useful to someone.

Great to hear it's working for you there.  I would love to see that if you choose to make it public - similar problem here, and I feel silly reinventing the wheel (and too much complexity for now to learn and keep up with the standard tools that do it all for you).

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?

1. Finishing my secret redesign of the docs and write the necessary bits to get type information into a database (e.g. sqlite)

2. Getting more involved with D again. Maybe trying a github streak or so.

On Thursday, 7 January 2016 at 00:34:45 UTC, Henry Gouk wrote:
> On Tuesday, 5 January 2016 at 12:27:12 UTC, Ola Fosheim Grøstad wrote:
>> 2. integrate with numerical solutions like TensorFlow?
>
> I'm currently working on something along the same lines as TensorFlow -- I started work on this before TensorFlow was announced. I haven't thought too much about writing a distributed backend, but currently there are some reasonably inefficient proof-of-concept CPU and CUDA backends.
>
> It's still fairly early on in development, and I'm more of an academic than an engineer. That said, I've managed to train some modestly sized convolutional networks without trouble.
>
> I'll open source it at some point, but I haven't got a time-frame for that.

Interesting project.