RejectedSoftware Forums

Sign up

Public awareness of Vibe.D

I stumbled across Vibe.D a few months ago while looking at the D
programming language. But when I do a regular web search, it's
not commonly listed. Would it make sense to get references to it
posted at dlang.org or the D projects pages at
prowiki.org/wiki4d, and maybe on wikipedia and the wikipedia list
of web frameworks?

Thanks,
-Mike

Re: Public awareness of Vibe.D

Am 06.09.2012 20:17, schrieb Michael_S:

I stumbled across Vibe.D a few months ago while looking at the D
programming language. But when I do a regular web search, it's not
commonly listed. Would it make sense to get references to it posted at
dlang.org or the D projects pages at prowiki.org/wiki4d, and maybe on
wikipedia and the wikipedia list of web frameworks?

Thanks,
-Mike

I wanted to make a bigger announcement and put some effort into
improving visiblity as soon as v0.8.0 will be out, which is supposed to
be stable, performance optimized, and feature-complete (regarding the
advertised features). But I guess at least for D-specific sites it would
definitely make sense to have references there, even if the current
state is not yet "stable".

In the case of wikipedia I suspect it doesn't yet qualify for its own
article (but maybe only the german version is that strict). The web
framework list sounds like it could work, although it has to be said
that vibe.d is not a pure web framework, even though it contains a web
server and an HTML template system...

Re: Public awareness of Vibe.D

I think you are being a tad bit pessimistic.

You have a 'production' server(that looks kickass. Seriously.) running
already, do you not?

Right now my major complaints are simply polish. (if they even qualify as
complaints.)
And it's still ahead of a lot of other projects that I have seen.

Development is still proceeding at a relatively rapid pace.

I would start 'pushing it out there.'
Make it clear that you want feedback on any issues, Make it clear it's
'beta', I really
do not think that there is currently much at all holding it back. It's in
a good enough state to
be usable. Go! I want to see this thing on the D announce list again!

Ha! I knew I saw Vibe.d on Wikipedia!
http://en.wikipedia.org/wiki/MongoDB#Language_support
I wonder where exactly the "D" link points to... ;-D

Oh, and I honestly find a lot more awesome D stuff by stalking the crap
out of anyone who has A D project
in their repos on github. I kinda got burned by the old site when I first
started with D.

On Thu, 06 Sep 2012 15:00:43 -0500, Sönke Ludwig
sludwig@rejectedsoftware.com wrote:

Am 06.09.2012 20:17, schrieb Michael_S:

I stumbled across Vibe.D a few months ago while looking at the D
programming language. But when I do a regular web search, it's not
commonly listed. Would it make sense to get references to it posted at
dlang.org or the D projects pages at prowiki.org/wiki4d, and maybe on
wikipedia and the wikipedia list of web frameworks?

Thanks,
-Mike

I wanted to make a bigger announcement and put some effort into
improving visiblity as soon as v0.8.0 will be out, which is supposed to
be stable, performance optimized, and feature-complete (regarding the
advertised features). But I guess at least for D-specific sites it would
definitely make sense to have references there, even if the current
state is not yet "stable".

In the case of wikipedia I suspect it doesn't yet qualify for its own
article (but maybe only the german version is that strict). The web
framework list sounds like it could work, although it has to be said
that vibe.d is not a pure web framework, even though it contains a web
server and an HTML template system...

Re: Public awareness of Vibe.D

Am 08.09.2012 13:19, schrieb 1100110:

I think you are being a tad bit pessimistic.

You have a 'production' server(that looks kickass. Seriously.) running
already, do you not?

Right now my major complaints are simply polish. (if they even qualify
as complaints.)
And it's still ahead of a lot of other projects that I have seen.

Development is still proceeding at a relatively rapid pace.

I would start 'pushing it out there.'
Make it clear that you want feedback on any issues, Make it clear it's
'beta', I really
do not think that there is currently much at all holding it back. It's
in a good enough state to
be usable. Go! I want to see this thing on the D announce list again!

My only concern is that attracting non-D people (who need to switch
languages) on one hand requires some instantly interesting feature(s)
and on the other hand many of them will probably easily get discouraged
if something doesn't work right away.

So everything that is more or less inside the D community is definitely
fine, but I guess that advertising a polished version to the 'general
public' has the best chances to also reach some future D-developers.

All in all I would say there are three blockers that would be good to
have out of the way:

  • vibedist has to work at least on localhost as a vhost manager and
    watchdog process
  • the recently discovered memory leak needs to be fixed
  • get the multithreaded HTTP server version thread-safe and tune the
    libevent back end so that we get some impressive benchmark numbers as
    this always seems to be a selling point to many (although these
    benchmarks most of the time have nothing to do with reality when it
    comes to real apps)

Re: Public awareness of Vibe.D

My only concern is that attracting non-D people (who need to
switch
languages) on one hand requires some instantly interesting
feature(s)
and on the other hand many of them will probably easily get
discouraged
if something doesn't work right away.

So everything that is more or less inside the D community is
definitely
fine, but I guess that advertising a polished version to the
'general
public' has the best chances to also reach some future
D-developers.

All in all I would say there are three blockers that would be
good to have out of the way:

  • vibedist has to work at least on localhost as a vhost

manager and
watchdog process

  • the recently discovered memory leak needs to be fixed
  • get the multithreaded HTTP server version thread-safe and

tune the
libevent back end so that we get some impressive benchmark
numbers as
this always seems to be a selling point to many (although these
benchmarks most of the time have nothing to do with reality
when it
comes to real apps

Eh, when I did a little server work, the main selling point was
"use as little resources as possible, so that we can give this
server almost
no resources."

It's all marketing and management who have no idea what's going
on and still insist that they make the final decision.

Politics, man. They suck.