On Wednesday, 8 June 2016 at 17:34:25 UTC, Ola Fosheim Grøstad
wrote:
On Wednesday, 8 June 2016 at 17:17:37 UTC, Adam D. Ruppe wrote:
bother with a proper setup. There's a reason ALL the other
major languages and frameworks use Apache/nginx/IIS on their
websites. It's the recommended way to do it.
Sure, you can have vibe.d behind nginx, if you want to, but it
would be more impressive if you didn't have to. Scripting
languages do of course have to.
The main point is that it isn't visible at all that vibe.d is
involved or how it is being used. So you loose out on a
showcase opportunity.
What other adopted solutions do is not really relevant as they
already _have_ massive amounts of showcases around the web _or_
they are not trying to position themselves in as a web backend
langauge. D is not a scripting language, if it wants to compete
with Go in the web arena it has to showcase itself where it can.
AFAIK golang.org uses their own stuff, Go on AppEngine.
There's a difference between an application server and a
frontend web server.
Well, you should be able to write a proxy in a system level
language. If you can showcase that it is easy to get comparable
performance then all the better.
vibes website doesn't use a proxy. But if D wants to compete in
web then there are alot of better areas to improve on like ORMs
(I know not everyone likes them but they have their use cases and
users), DB support, etc. That will attract more ppl more than
some proxy would.. At least as far as people and companies that
build applications.. I mean D could also be used to build a
database but why when there are already used alternatives..
