4 ms·
Nice work thank you for sharing. Tangentially it’s not clear to me what relevance D should have for any greenfield projects where there is not already heavy in
by WhitneyLand 8y ago
Nice work thank you for sharing.
Tangentially it’s not clear to me what relevance D should have for any greenfield projects where there is not already heavy investment in a code base to consider.
First there’s the whole Rust comparison, and then the incredible impact of the comparative size and momentum of ecosystems for various languages.
This reddit thread has a few interesting comments. It was quite surprising to see D’s architect/designer discount the value of memory management issues in a sub link there. Anecdotally what I’ve read, and experienced, is that it’s one of the most important sources of bugs when quantity and time to debug and fix are considered.
https://www.reddit.com/r/rust/comments/5h0s2n/what_made_rust_more_popular_than_d/ https://www.reddit.com/r/rust/comments/5h0s2n/what_made_rust...
- EvenThisAcronym 8y ago> Tangentially it’s not clear to me what relevance D should have for any greenfield projects where there is not already heavy investment in a code base to consider. Another one of Cybershadow's articles on D that blew my mind is, IMO, one of the greatest arguments for why you should care about D. The beauty, conciseness and flexibility of the implementation here is extremely cool. And this is not a one-off case; there are many programmers in the D community that create awesome stuff like this all the time. Writing in D is like having superpowers, and going back to a less expressive language feels horribly constraining.
- p0nce 8y agoPerhaps are you referring to this article? https://blog.thecybershadow.net/2014/03/21/functional-image-processing-in-d/ https://blog.thecybershadow.net/2014/03/21/functional-image-... Vladimir has one hell of a blog.
- EvenThisAcronym 8y agoYes, thanks. Forgot to actually post the link.