On Sunday, 24 December 2017 at 15:00:09 UTC, Dylan Graham wrote:
On Saturday, 23 December 2017 at 08:15:04 UTC, Dan Partelly
wrote:
On Saturday, 23 December 2017 at 01:12:53 UTC, Dylan Graham
wrote:
language it should be, not the language some C++ programmer
wants but is never going to use anyway.
Ironically, D is so close to beeing the language a C++
programmer would really use that you can smell it. It doesnt
have to bend, since it got so close with a lot of good
decisions. D is the first language Im aware of which has the
potential to satisfy the needs of a very large portion of the
market,
How much further does D have to go to start snatching C++'s
userbase?
In my honest opinion, D doesn't offer as much of an advantage
over C++ as it does C# and Java. Currently D has much better
template syntax, modules (although that idea is being floated
in the C++ community), but what else? The C++ juggernaut keeps
piling on new features every 3 years. It's hard for D to stay
in the lead (that is if it is).
That's the biggest problem with C++, they pile on relentlessly
half baked feature after half baked feature in a big dump that no
one with a life can ever grasp.
I've been writing a voxel engine in C#. Writing anything high
performance in C# becomes non-idiomatic, you're locked into OOP
and performance sucks.
D offers far more features C# and Java. As a result, I think D
would have a greater appeal on those audiences.
The big issues with Java and C# are the required infrastructure
for deployment. They could be the best languages since sliced
bread, they would still be annoying to deploy as the runtime is
an emulator.
I ported 1 app from Java to D. It was so unspectacular (or better
said it was spectacularly easy) that you're probably right.
Reaching to Java devs is a good idea. The advantage of Java
though, is not the language but the huge, huge, huge existing
libraries and packages and know how. This will be difficult to
overcome for any language.
