4 ms·
Too bad Dlang never reached mainstream. It's a perfectly suitable language for backend programming and system programming where golang is growing popular.
by zyngaro 10y ago
Too bad Dlang never reached mainstream. It's a perfectly suitable language for backend programming and system programming where golang is growing popular.
- jordigh 10y agoGolang isn't going mainstream either, and D isn't doomed to never got popular either. Let's not speak in such hyperbole. If you like language $X, use language $X and as long as you can find sufficient resources for it, don't worry about who else is using it (I personally can find sufficient resources for D).
- dpc_pw 10y agoIf D had in-language-integrated Fibers like Go does it would be just better in every aspect. Native-fast code, fast compile, powerful generic and meta-programming. It was trying to be better C/C++ but should have instead push where Go is going: highly productive and fast. I think Rust is much better C replacement - much higher overhead and mental cost, for software that can't compromise on performance, reliability and safety.
- WalterBright 10y agoI'm not sure that language integrated ones would be better. As D's abstraction abilities have improved, we've been moving features from the core language to the library.
- dpc_pw 10y agoThe only thing that I find great about Go is the fact that you can write, normal, imperative, blocking-io-like code dealing with about anything (network, file, any io) and get a service that can handle 10k concurrent connections without thinking much about it. If D could do the same, no matter if through language support, or a library it would be really awesome. Note: it seems to me, currently D's fibers require manual `yield`. The entire point is not to have to do it.
- Doxin 10y agoI suggest you go have a look at vibe.d, which is a networking/IO framework. It allows you to write your code as if it's only ever going to handle a single connection and have it magically work(tm) for multiple connections too.