On Saturday, 20 September 2014 at 04:28:58 UTC, deadalnix wrote:
On Friday, 19 September 2014 at 23:47:06 UTC, Max Klyga wrote:
Jonathan Blow just recorded a talk about the needs and ideas
for a programming language for game developer.
https://www.youtube.com/watch?v=TH9VCN6UkyQ
This talk mentions D quite a lot of times.
D is mentioned as the most probable to be adopted if it were
possible for frictionless interaction with existing codebase.
An interesting talk if you want to look at language design
from game developer perspective.
I haven't finished the talk yet, but already this is kind of
upsetting. The claim that he want to create a programming
language, but is unable to give concrete examples of any case
he makes so far, grossly misrepresent what exists in other
languages or flat out declare that he doesn't know.
I got similar feeling. If he joined D, there would be more value
than starting all from the ground.
I think D fits well his requirements. He admits it between the
lines when defines D as better C++, but not worth switching
because of not enough gain.
IMHO, D has the best cumulative score across all languages in
main 3 categories (despite tooling):
1. Kernel type (mostly no memory allocations) - the winner here
2. Game type (mostly manual memory management) - the winner here
3. Applications/Scripts (mostly automatic memory management))-
the winner in large scale apps. In terms of small ones, for most
people D places somewhere in 2nd place group because of static
typing (but honestly I prefer writing scripts in statically typed
languages)
After years of codding I think the following topics (pointed in
video) will never be solved entirely in any language
1. Resource handling
2. Error handing
As for the biggest D rival - Rust, despite all syntax choices I
don't accept, here is at least one thing that prevents Rust to be
ready for ver 1.0 in the end of year:
http://doc.rust-lang.org/guide-pointers.html#gc
Gc<T>
"In the future, Rust may have a real garbage collected type, and
so it has not yet been removed for that reason."
In my opinion, as a usual coder, memory model in Rust is not well
defined for now.
Piotrek
