On 2014-10-29 18:12, Laeeth Isharc wrote:
Rationale for using Dart in combination with D is that I am not thrilled
about learning or writing in Javascript, yet one has to do processing on
the client in some language, and there seem very few viable alternatives
for that. It would be nice to run D from front to back, but at least
Dart has C-like syntax and is reasonably well thought out.
I actually thought this over in the past and posted my research here:
http://forum.dlang.org/thread/ll38cn$ojv$1...@digitalmars.com
It would be awesome to write front-end tools in D. However, there won't
be much browser support unless you're backed by Google or Microsoft.
What's going to replace javascript? Will it be typescript? asm.js? dart?
PNaCl?
The solution is obviously to compile from D to the target language. But
what's the real advantage? Re-using some back-end MVC libraries? All the
communication is actually done through sockets, there's never any real
interaction between the back-end/front-end.
Also, you realize the front-end stuff is so full of community
contributions that you're actually shooting yourself in the foot if you
divert away from the more popular language and methodologies.
So, I settle with javascript, and I shop for libraries instead of
writing anything at all. There's so much diversity in the front-end
world, a few hundred lines of code at most are going to be necessary for
an original piece of work. Heh.
