Vic:
- Confusing forum. First listed forum on 'D' is not for D users, but it's called D! It is in fact for D commiters. This causes frustration for both users and commiters. (yes there is 'learn D' but it's 4th down. Commiters forum should be slightly hidden and user questions should not be answered in commuters but politely asked to post in the proper forum.).
This looks sufficiently easy to fix. It just means restyling and reshuffling this page: http://forum.dlang.org/
Are you able to sketch what kind of look you like for this page and show an image?
- I was *very* disappointed that using base library locks you into GC vs ref. counting. Separate, I like how Objective C has NSObject for GC purpose(I'd love a framework that is just ref counting), but there should be dual libs and base should not be GC.
Allocators will probably come, but still there are no plans for language hooks, so there's still some way to go. I think this can be partially solved.
- D is/has become complex. metaprograming, generics, macros, etc. This is a culture issue, very hard to fix cultural issues
At this point I don't think this will be fixed. Removing complexity is hard.
- Very little 'user' outreach. Meetups such as 'learn D' (set up editor w/ DUB, and write some vibe.d DNS client/server in 4 lessons). Or how to use a c .so lib.
This could be improved, but beside the need for D community to grow, I think it's also a cultural problem.
So hth. FYI I plan to hire 3+ 'D lang' programmers (users, not commuters) to rewrite the Java project in Dallas and/or San Jose (CA) over the next few months (Feel free to ping me @puppetMaster3, ideal candidate is 'prolific' and career programmer)
What's the purpose of the rewrite? What do you hope to improve over the Java code?
Bye, bearophile
