<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body><div><div style="font-family: Calibri,sans-serif; font-size: 11pt;">We use D in our work a little. And we dont using it more because we do not need to ;).<br><br>We have a quite big php codebase and bacause od facebook(hhvm) our code is fast enought.</div></div><div dir="ltr"><hr><span style="font-family: Calibri,sans-serif; font-size: 11pt; font-weight: bold;">Od:</span><span style="font-family: Calibri,sans-serif; font-size: 11pt;"><a href="mailto:digitalmars-d@puremagic.com">Manu via Digitalmars-d</a></span><br><span style="font-family: Calibri,sans-serif; font-size: 11pt; font-weight: bold;">Odesláno:</span><span style="font-family: Calibri,sans-serif; font-size: 11pt;">28. 5. 2015 16:40</span><br><span style="font-family: Calibri,sans-serif; font-size: 11pt; font-weight: bold;">Komu:</span><span style="font-family: Calibri,sans-serif; font-size: 11pt;"><a href="mailto:digitalmars-d@puremagic.com">digitalmars.D</a></span><br><span style="font-family: Calibri,sans-serif; font-size: 11pt; font-weight: bold;">Předmět:</span><span style="font-family: Calibri,sans-serif; font-size: 11pt;">Why aren't you using D at work?</span><br><br></div>I've been using D in all my personal projects for years now, but I<br>lament coding C at work every day, and I pine for salvation.<br>I seem to have reasonable influence in my workplaces, and I suspect I<br>could have my workplace adopt D, but when considering the notion with<br>other staff, we always seem to encounter hard blockers to migration<br>that stop us in our tracks.<br><br>I expect I'm not alone. Please share the absolute blockers preventing<br>you from adopting D in your offices. I wonder if there will be common<br>themes emerge?<br><br><br>Every place I work has a slightly different set of blockers. I have<br>potential opportunity to involve D in my workplace in multiple key<br>areas, but blockers exist along every path, as follows:<br><br>Web:<br>* We need NaCl + Emscripten support in LDC. Doesn't need to be<br>comprehensive, just successfully compile code. Emscripten alone may<br>satisfy; probably a much easier target.<br><br>Core engine/applications:<br>* Android+iOS. (plus also the web targets above in the future)<br><br>Desktop utilities:<br>* Workable Qt bindings.<br><br>General friction/resistance from colleagues:<br>* Forceinline. We have SO MUCH CODE that simply must inline. It's<br>non-negotiable, nobody is comfortable to write ranges or properties<br>without forceinline. I can't sell "just trust that the optimiser might<br>maybe hopefully do what you want" to low-level engineers, I've been<br>trying for years.<br>* Debugging experience; it's come a long way, but there's still<br>significant usability inhibitors.<br><br><br>I often wonder if others share the importance of mobile cross-compilers?<br>They seem to be getting lots of love recently, which is very exciting!<br>I'd like to encourage those working on the Android/iOS toolchains to<br>publish regular binary builds of the toolchains so we with little<br>allocated working time can grab the latest toolchains and try our<br>stuff from time to time.<br>Who maintains the CI solutions for the various compilers? How hard is<br>it to add CI for the common cross-compilers and publish them?<br><br><br>The interesting observation I make from that list above, is that<br>barring Qt bindings, everything I list is a problem for LDC. It would<br>seem to that LDC is the most important point of focus for my company<br>at this time.<br>How many contributors does LDC have these days out of curiosity?<br>GDC could give Android, but all the other points depend on LLVM.<br><br><br>The trick is getting something (anything) to shift to D in the office,<br>giving other programmers some exposure, and give us a context to<br>experiment with D in application to our particular workload; that is,<br>realtime processing and rendering of geospatial data, an ideal<br>workload for D in my mind! http://udserver.euclideon.com/demo (demo is<br>NaCl + Emscripten, we'd love to have written it in D!)<br></body></html>