How slow is Discourse on your mobile?

Filed under: English -> French -> Arabic -> Danish -> Dutch -> Spanish -> Latvian -> Haitian Creole -> Lithuanian -> Portuguese -> Romanian -> English

loopback0

I'd change that if I could be bothered to figure out where the restriction on notification type is.
But I can't, so it stays.

ben_lubar

Inod Zithismörul, Ranger cancels Mill Plants: Needs millable unrotten plants.

translator

After 10 translations Bing says: The Ranger Annuler plants, plants, plants not rotten, millable Zithism.

Filed under: English -> Vietnamese -> Danish -> Haitian Creole -> Chinese Simplified -> Finnish -> Hungarian -> Japanese -> Portuguese -> Polish -> Romanian -> English

hungrier

That made more sense than the original.

translator

After 10 translations Bing says: People have more sense than the original.

Filed under: English -> Latvian -> Russian -> Dutch -> Slovenian -> Japanese -> Romanian -> Greek -> Slovak -> Italian -> Catalan -> English

accalia

https://github.com/AccaliaDeElementia/SockBot/blob/master/sock_modules/sumon.js#L59

and the various strings that can be in that type parameter:

https://github.com/AccaliaDeElementia/SockBot/blob/master/messageBus.js#L18

Kuro

Careful guys and girls,

this is bot-talk in a meta-topic blakeyrat participates in

Filed Under: Oh no you didn't

Polygeekery

@Kuro said:

this is bot-talk in a meta-topic blakeyrat participates in

He has not lost his shit for a while. He is overdue. He is like a volcano. You either have a small blowup every once in a while, or after a long enough period you get Vesuvius and the aftermath.

FrostCat

Of course, now that you've said that, we'll get to see if he can resist the goading.

Polygeekery

@FrostCat said:

we'll get to see if he can resist the goading.

I can neither confirm nor deny that was my intentions.

accalia

@Intercourse said:

or after a long enough period you get Vesuvius and the aftermath.

pretty sure it takes a while to reach that level of pent up.... blakeyness. didn't we have a Mount St Hellens at least recently with the bots?

Polygeekery

@accalia said:

didn't we have a Mount St Hellens at least recently with the bots?

Yes, in that Mount St Helens was isolated in damage and only effected a few people. Vesuvius is when he completely flips his shit and then rage quits. We are way overdue.

accalia

hmm... maybe. i've always went for the typhoon metaphor rather than the volcano.... but that's just me.

Polygeekery

Typhoons are gentle in comparison. I think the volcanic explosion is a more apt metaphor. ;-)

blakeyrat

You people all have an unhealthy obsession with Blakeyrat.

FrostCat

@blakeyrat said:

You people all have an unhealthy obsession with Blakeyrat.

Nonsense. I shudder at the taste of undead flesh. It revitalizes me.

FrostCat

I'm curious to see if anyone can guess what that's a quote from.

FrostCat

So the test in the first post, on my brand-new LG G3 with a 2.5GHz quad-core processor or whatever, posts a score of like 4500.

end

The deeper issue is that you guys are updating too often IMO.

This is a community that is highly intolerant of anyone making mistakes, where hating IT things and IT people is glorified.. even celebrated. The more minor the mistake, the more exciting it is to you guys. My favorite is how numbered lists are our fault, somehow, even though the Markdown spec, such as it is, has defined numbered lists that was since 2004. No matter, the presence of spec Markdown lists is Discourse is not just a personal affront to your human decency but an indication that we a) suck at our jobs b) don't care c) personally hate you. None of those things are true.

Which is, well, your choice. It makes you a group of people that are highly unpleasant to interact with. (and from a career standpoint you should be careful with these kinds of toxic attitudes if they are bleeding over into your work life -- it is deeply unhealthy) But more practically, it makes you the worst possible audience for bleeding edge daily build code that is going to have regressions, particularly as we rip out and upgrade core frameworks we use (Ember).

TL; DR I suggest only updating with the marked betas which occur (roughly) every week.

RaceProUK

And obviously the best way to handle us being critical is to blanket-insult the entire community, whether the individuals within deserve it or not.

Also, this place toxic? Believe me, this place is far from toxic. If you want a toxic community, try being a Sonic fan. Compared to the environment on some of those sites, this place is full of kittens and puppies.

Monarch

https://www.youtube.com/watch?v=baVkpul4XoU

end

For example -- the CSS font size bug (related to making global font sizes easier to adjust in 1.2 request) existed for all of 2 days. You would not have even experienced that bug at all had you updated with the numbered semi-weekly beta releases.

I can think of a bunch of other examples recently, as it has been very beta-y with updating Ember, a core framework we rely on.

it's like saying "we hate bugs and we hate peope who write buggy software" (by the way, I suggest looking in the mirror every now and again) and then "sign us up for the buggiest release format you have, daily!"

At some level, I am saying "stop hitting yourself".

RaceProUK

Are you aware a lot of us here want to move off latest? Did you know we even had a petition requesting @PJH stop updating so often? Did you know he's also applying no more updates for at least a month?

And again with the attitude. That's what we don't like; as far as I'm concerned, your image here has nothing to do with you as a person, but with how you present yourself to our little corner of the Internet. A little humility goes a long way. So does not deleting valid bug reports and criticism (though I accept you may not do that anymore, or ever for that matter; all I have w.r.t. that is hearsay).

As for
@codinghorror said:

by the way, I suggest looking in the mirror every now and again

the temptation is to say 'go fuck yourself'. But y'know what, I'm not going to say that; that's not who I am. It's who I used to be, and it got me fucking nowhere. What I will say though is this: follow your own advice.

PleegWat

@RaceProUK said:

Compared to the environment on some of those sites, this place is full of kittens and puppies.

Foxes, I think you'll find.

RaceProUK

@PleegWat said:

Foxes, I think you'll find.

Ah yes, how can I forget @accalia

end

I do look in the mirror all the time, that's why I don't willingly hang out in communities that glorify making fun of others for mistakes they make themselves all the time. But you do.

What's Wrong With The Daily WTF

I think this para is also relevant, from this Pulitzer winning article

Humans, Hickling said, have a fundamental need to create and maintain a narrative for their lives in which the universe is not implacable and heartless, that terrible things do not happen at random, and that catastrophe can be avoided if you are vigilant and responsible.

In hyperthermia cases, he believes, the parents are demonized for much the same reasons. “We are vulnerable, but we don’t want to be reminded of that. We want to believe that the world is understandable and controllable and unthreatening, that if we follow the rules, we’ll be okay. So, when this kind of thing happens to other people, we need to put them in a different category from us. We don’t want to resemble them, and the fact that we might is too terrifying to deal with. So, they have to be monsters.”

Where what you are resembling is the average Daily WTF subject.

blakeyrat

@codinghorror said:

The deeper issue is that you guys are updating too often IMO.

Right. It's definitely not, "the Discourse developers continually check-in broken code without even pretending to do any testing of it."

@codinghorror said:

My favorite is how numbered lists are our fault, somehow, even though the Markdown spec, such as it is, has defined numbered lists that was since 2004.

I don't give a shit what Markdown is or does. You gave us a forum where if you type "3." in the edit window, you get "1." in the result. There is no way that's not a bug. An extremely, extremely obvious bug.

To just dismiss it by saying, "oh well Markdown!" misses the point entirely. You picked this shitty formatting language. You are shipping the buggy code. You are responsible for fixing it.

I don't hate "IT things and IT people" (whatever the fuck those are), but I can tell you something I really do hate: people who, instead of taking responsibility for their own mistakes, just continually pass-the-buck.

@codinghorror said:

but an indication that we a) suck at our jobs b) don't care c) personally hate you. None of those things are true.

a) definitely is.

Not sure about the other two.

@codinghorror said:

Which is, well, your choice. It makes you a group of people that are highly unpleasant to interact with.

Good. Why don't you talk to Alex about removing Discourse so we wouldn't have to interact with your unpleasantness. My end goal here is to never have to interact with this bullshit again as long as I live-- you (via Alex being an idiot) forced your way into our community. Nobody here asked for you.

@codinghorror said:

(and from a career standpoint you should be careful with these kinds of toxic attitudes if they are bleeding over into your work life -- it is deeply unhealthy)

People who hire me actually appreciate my attention to detail and resistance to shipping buggy products. They must be mutant freaks or something.

@codinghorror said:

But more practically, it makes you the worst possible audience for bleeding edge daily build code that is going to have regressions, particularly as we rip out and upgrade core frameworks we use (Ember).

How about not putting the buggy versions out there for anybody to download? How about maybe actually testing your shit before you commit it to the repo?

@codinghorror said:

TL; DR I suggest only updating with the marked betas which occur (roughly) every week.

Are they any better?

blakeyrat

@codinghorror said:

For example -- the CSS font size bug (related to making global font sizes easier to adjust in 1.2 request) existed for all of 2 days.

It only existed at all because you had an incompetent developer check-in a change without testing it on one of the most popular desktop browsers in existence. One that runs on every OS. There is literally ZERO excuse for that to happen, EVER.

You're lecturing the wrong party here. Why are you chewing-out the people who found the bug instead of the person who created the bug? (I guess point b) in that previous post was true, also. You simply do not care.)

BTW, you do realize that we have a thread here with like a shitload of upvotes asking to move off your fast shitty buggy releases and change to the slightly-slower shitty buggy releases, right? You're preaching to the choir.

@codinghorror said:

it's like saying "we hate bugs and we hate peope who write buggy software" (by the way, I suggest looking in the mirror every now and again) and then "sign us up for the buggiest release format you have, daily!"

It's almost as if the people saying they hate this buggy software aren't the people in charge of the server! Hm!

@codinghorror said:

At some level, I am saying "stop hitting yourself".

How about we make a deal: we stop hitting ourselves, and you get your devs to at least load the product once in every major browser after every code change. I'm not saying "test it", because God knows that's fucking impossible, I'm just saying "load it in a browser, and see if the font is size 1.6."

end

@blakeyrat said:

BTW, you do realize that we have a thread here with like a shitload of upvotes asking to move off your fast shitty buggy releases and change to the slightly-slower shitty buggy releases, right? You're preaching to the choir.

Then we are in agreement, as you guys could have easily skipped that bug entirely rather than raging against the machine.

By the way, I strongly recommend you, and everyone here, read this article. Because anyone who makes a mistake is a moron and that should be punishable by death in the most painful way imaginable.

RaceProUK

@codinghorror said:

I do look in the mirror all the time, that's why I don't willingly hang out in communities that glorify making fun of others for mistakes they make themselves all the time. But you do.

Y'know what, I tried to be nice about it, but now you're getting personal, I will tell you to go fuck yourself.

And if I had any respect for you as a person, that's all just gone down the shitter. Of course, you won't care, and find some way to turn it around on me. And all that will do is confirm I'm right in thinking you're a fucking obnoxious egocentric bastard.

blakeyrat

@codinghorror said:

Because anyone who makes a mistake is a moron and that should be punishable by death in the most painful way imaginable.

How about when you stop actively making the mistake of "committing code with zero testing", then we can have a nice discussion of it? The problem here is you haven't yet stopped making the mistake. We never have a chance to stop calling you a moron, because every day there's ever more untested buggy code.

You moron.

Hey, here's an idea: you want some respect and consideration from the community here? How about you create and deliver a quality product to us.

end

It's ok, this is who you guys are, it is what you do. Like racism, it's not exactly a great choice of hobby... but it's not illegal, so to each his own.

blakeyrat

Well now we know. Criticizing Discourse is exactly like leaving a baby in the back of a car unattended. (And also like racism, apparently.) Exactly like that.

At this point, I think Atwood might be literally insane.

EDIT: oh hey Atwood, if you gave me the "pickup truck" forum I'd asked for in the first place, that baby would be just fine-- lots of healthy, fresh air sitting in the bed of one of those.

cartman82

Err... wow. I'm not on the anti-discourse bandwagon and I don't see the connection. And racism cheap shot? Really?

end

Here's the relevant pull quote

Humans, Hickling said, have a fundamental need to create and maintain a narrative for their lives in which the universe is not implacable and heartless, that terrible things do not happen at random, and that catastrophe can be avoided if you are vigilant and responsible.

In hyperthermia cases, he believes, the parents are demonized for much the same reasons. “We are vulnerable, but we don’t want to be reminded of that. We want to believe that the world is understandable and controllable and unthreatening, that if we follow the rules, we’ll be okay. So, when this kind of thing happens to other people, we need to put them in a different category from us. We don’t want to resemble them, and the fact that we might is too terrifying to deal with. So, they have to be monsters.”

The whole community is predicated on "ha ha, look how stupid everyone else is". Because it's too terrifying to realize we're that person too.

blakeyrat

@codinghorror said:

Because it's too terrifying to realize we're that person too.

No, you don't get it at all. We do realize we are that person. That's why we test our shit before releasing it. That's why we do usability testing. That's why we get buy-in from our customers before adding features. Because we're fallible, and if we didn't do those things, we'd end up with a shitty product.

You're the raging egomaniac who knows every tiny bit of code and design he shits out is immediately production-ready.

RaceProUK

@blakeyrat said:

You're the raging egomaniac who knows every tiny bit of code and design he shits out is immediately production-ready.

We may not agree on much, but on this, we're 100% aligned.

And that probably says far more than it initially appears.

end

@blakeyrat said:

EDIT: oh hey Atwood, if you gave me the "pickup truck" forum I'd asked for in the first place, that baby would be just fine-- lots of healthy, fresh air sitting in the bed of one of those.

Doesn't work out too well for trucks either.

end

@blakeyrat said:

You're the raging egomaniac who knows every tiny bit of code and design he shits out is immediately production-read

Really? I am the one forcing you guys to be on daily builds, when we have stable and beta channels? News to me...

cartman82

Sometimes. But on the whole, you're reading too much into it. Your analogy court case lacks the venting component, interpersonal conflict in case of Discourse, community group dynamics and a hundred other things.