Crazy, sad but ... would you use D for your own facebook or pinterest?

[Chris Wright via Digitalmars-d]

On Mon, 02 Jan 2017 21:49:03 +0000, aberba wrote:

> I'm not building Facebook/pinterest but I'm trying to work on a platform
> like "pinterest-like" but on a small scale. I want it to be easy to
> write, fast, ... you know. D is obviously that (IMO).
> 
> About scalability, would you recommend D(vibe.d initially) for long run
> (techically, generally, currently)? Why? (Brutal honesty).

I'd consider what languages future employees are likely to know and how 
much time it would take them to become proficient with D. I'd consider 
what dependencies I will likely have and whether there are existing D 
libraries for them. Then I'd put together a demo and see how it works. 
Use ab(1) (the Apache benchmark tool) to estimate scaling naively, and 
then implement a more application-specific benchmarking tool to see in 
more depth.

I'd do that iteratively, so I'm not spending weeks on a demo that can't 
handle two simultaneous database connections or falls over if you look at 
it funny.

I'm likely to want investors, so a functional demo is useful, even if I 
scrap it after seed funding or Series A.

I'd do the same with any toolkit or language at that stage. For instance, 
I'm at an early-stage startup right now, and I spent a bit of effort 
comparing several different frameworks we could use for services and RPCs.

This isn't so much an answer, but then, I don't know your usecase well 
enough, and I don't know what technologies you plan to use. For instance, 
you might want to use Hadoop for file storage. Or MongoDB + GridFS. Or 
MySQL with a limit on file sizes. Or a scale-out filesystem like Qumulo. 
These are quite different options with different levels of support in D.