One night I dreamed I was walking along the beach with Discourse.
Many scenes from my life flashed across the sky.
In each scene I noticed footprints in the sand.
Sometimes there were two sets of footprints,
other times there were one set of footprints.

This bothered me because I noticed
that during the low periods of my life,
when I was suffering from
anguish, sorrow or defeat,
I could see only one set of footprints.

So I said to the Discourse,
"You promised me Discourse,
that if I used you,
you would always walk beside me.
But I have noticed that during
the most trying periods of my life
there have only been one
set of footprints in the sand.
Why, when I needed you most,
you have not been there for me?"

The Discourse replied,
"The times when you have
seen only one set of footprints,
is when I carried you."

% outages at TDWTF : 65.blahblahblah% (or roughly 2 out of every three outages)

When the Dead do walk seek water's run, for this the Dead will always shun.swift river's best or broadest lake, to ward the Dead and haven make.if water fails thee, fire's thy friend, if neither guards it will be thy end.

It's a small price to pay. Once the page is loaded, you can see Infinite Posts!™ No need to click next page every time.

Of course it still takes a couple of seconds to load the next chunk. And it happens much more often than you had to click next page in the previous forum, meaning you still lose more time. But you save one click every 50 posts!

So, why do we have square the amounts of outages than the next big competitor (try.discourse)? And don't you guys need to restart try.discourse.org every once in a while for all the updates you post on that?

Also, we had (/ still have sometimes?) the white-post problem. As a forum that should count towards outage.
Also that Downtime number seems fake? What with being a perfect 4 hours?

I think it might be related to some sort of gross misconfiguration of the logging coupled to the way some people use bots. At least some of the times that DC has been down, it's been because we've filled up the disk (presumably with logging info) and have needed emergency Staff attention.

I am not sure how Pingdom calculates response times but I think they average from the whole world and all their ping sites, of which they have a lot. I remember the ping response times being pretty bad for Stack Overflow back in the day as well and that is a very, very fast site. Thanks compiled .net code!

One of the biggest WTFs around here is how you're aware of a programming environment that doesn't suck ass and can be used to create decent websites, and somehow built this in a giant open source shitpile instead.

Meh, I think it was the right tool for the job in this case. For projects like this you want to be able to iterate quickly (although, you should test a bit more thoroughly before releasing) and there is a huge community around RoR. Ruby support is also pretty ubiquitous these days, the hosting is cheap and with the advent of Docker, anyone can have it up and running in a short period of time. The same cannot be said of .Net code, the price of entry would be a lot more expensive and it would be a lot harder for a novice to get up and running, not to mention the hosting would be a lot more expensive.

The only thing more ubiquitous these days for the purposes that they wanted to address would be PHP. So which would you rather have?

the hosting is cheap and with the advent of Docker, anyone can have it up and running in a short period of time. The same cannot be said of .Net code, the price of entry would be a lot more expensive and it would be a lot harder for a novice to get up and running, not to mention the hosting would be a lot more expensive.

Any hosting that allows Docker allows Mono. In fact I'm pretty sure you can just run Mono inside your Docker VM or whatever they call it.

RoR makes it a lot faster to deploy new features, etc. At least for me and those I know. If you take two projects and develop one in RoR and another in .Net, RoR will usually win for speed of development. To each their own though.

I would certainly agree with that and I feel like most issues that crop up should have tests written for them to verify that they are fixed. Then, if you ever have a regression, it should be caught by automated testing. TDD only works if you follow the procedures.

Agreed. And far too many of those are regressions which should have been caught by testing. To be fair though, I believe we are not on the stable branch. Also, I speculate that we are likely on the bleeding edge so that we can catch those bugs as some sort of arrangement between Jeff and Alex. That is a WAG though.

RoR makes it a lot faster to deploy new features, etc. At least for me and those I know.

You'd have to cite a hell of a study between, say, Rails and MVC. A hell of a study. Because that's utter gibberish. Plus .net environments have those nice things like "working debuggers" that make writing code so much easier.

The math is bad on that. 4 hours of downtime during Nov is not 99.45% uptime. Nov has 30 days, which is 720 hours. With 4 hours of downtime, that's 716 hours of uptime. 716 / 720 = 0.99444444 or 99.44%. Looks like pingdom needs some math help.

When the Dead do walk seek water's run, for this the Dead will always shun.swift river's best or broadest lake, to ward the Dead and haven make.if water fails thee, fire's thy friend, if neither guards it will be thy end.

it would be a lot harder for a novice to get up and running, not to mention the hosting would be a lot more expensive.

First off, CDCK offers hosting services for the novices you mention, so that's not a huge issue. As for hosting costs, you can find Windows hosting starting at $10/month, and there's always mono if you want to try hosting in another environment.

hmm... last time my quote was visible (at least to me) does it work this time too?

EDIT: Yes, until i refreshed the page.....

When the Dead do walk seek water's run, for this the Dead will always shun.swift river's best or broadest lake, to ward the Dead and haven make.if water fails thee, fire's thy friend, if neither guards it will be thy end.

When the Dead do walk seek water's run, for this the Dead will always shun.swift river's best or broadest lake, to ward the Dead and haven make.if water fails thee, fire's thy friend, if neither guards it will be thy end.

looks like some of the bots aren't affected byt the white post issue....

why?

When the Dead do walk seek water's run, for this the Dead will always shun.swift river's best or broadest lake, to ward the Dead and haven make.if water fails thee, fire's thy friend, if neither guards it will be thy end.

You'd have to cite a hell of a study between, say, Rails and MVC. A hell of a study. Because that's utter gibberish. Plus .net environments have those nice things like "working debuggers" that make writing code so much easier.

Meh, I can call this one a draw. I can only speak from my own experience and I CBA to look up a real study. You are free to though, and if I am wrong (unlike you) I will admit I am wrong.

Is the same as saying, "I am completely unaware of Mono, thank you for enlightening me." You need to have your shoulder aliens checked out. Those motherfuckers are apparently schizophrenic. You fucking cunt.

You can do that in .NET. I've got a .NET project where we are sometimes updating production 2 or three times a week. With a team of two.

Fair enough, I was speaking from my own experience. Right now we are in the alpha stages of a RoR project that I started. We are still early enough on that dev = production. Right now when an alpha-user requests a feature, we implement it, pull from Git and then it is live. Updating production happens A LOT, per week. If it passes tests, it goes to production to be evaluated. This is very early on though.

For devs? Not true. You can use the appropriate express edition to develop commercial apps for free.

Meh, I was talking about the amount of time it takes to get to profitability. As far as dev tools go, I could really give a shit less. Those are one time costs. In my frame of reference, I am talking about the amount of time (and time=money) that it takes to get to a billable consumer. I get your point though.

First off, CDCK offers hosting services for the novices you mention, so that's not a huge issue. As for hosting costs, you can find Windows hosting starting at $10/month, and there's always mono if you want to try hosting in another environment.

Fair enough, but it depends upon how advanced your application is. Off the top of my head, as a guesstimate, I would think that a .Net (Windows Server) solution would require a VPS, which will cost you more. A Digital Ocean Discourse instance will cost you the same amount of money though. I call it a draw.

@blakeyrat, you should notice the difference in tone. When I talk to @abarker, I am very cordial. When I talk to you, I am a bit of a cock, because you are a cunt when you reply to people. You don't know everything, and you need to have those shoulder aliens checked out. You seem to be wrong a lot lately.

Fair enough, I was speaking from my own experience. Right now we are in the alpha stages of a RoR project that I started. We are still early enough on that dev = production. Right now when an alpha-user requests a feature, we implement it, pull from Git and then it is live. Updating production happens A LOT, per week. If it passes tests, it goes to production to be evaluated. This is very early on though.

Once again... what does this have to do with language? You could set up your favorite source control system to trigger deployments to any environment you want on every commit if you wanted to. I can't think of any language that wouldn't allow this. We have most of our .Net projects set up to do this for our test environments.