Moar downtime? who was playing with bots again?
-
It's interesting that the definition they use results as San Francisco-Oakland and San Jose being listed separately. I think most locals would consider them all to be part of a single urban area.
That's like lumping SD and LA together.
-
I highly doubt that is true.
Well it's true, but only on the technicality that I don't know French.
Doubt all you like, but you're wrong. A Frenchman doesn't need France to be big in order to think it's better than the rest of the world. An Englishman doesn't need England to be big in order to know it's better than the rest of the world. An American - the rest of the what?
@blakeyrat said:Whatever. Point is, fuck everybody who says German when their great, great, great grandfathers were bombing the Kaiser. And I'm sure their great, great, great grandfather would say the same. Except with more charming Victorian lingo.
Multiple history fail, although I agree with the sentiment.
@boomzilla said:Yeah, my German ancestors all came over in the 19th century, though my wife's great grandfather was in the Kaiser's army and apparently jumped ship in NY in the early 20th. She also has Scottish ancestors who came over in the 17th century to survey NJ.
...and there you have it. What you'll find back in the"old country", is that only nationalist twats care about where their ancestors come from enough to bring it out in public. And, amusingly enough, they're often wrong about that.
-
...and there you have it. What you'll find back in the"old country", is that only nationalist twats care about where their ancestors come from enough to bring it out in public.
Yes, because their stories are probably pretty boring and predictable.
-
Yes, because their stories are probably pretty boring and predictable.
Oooh, that reminds me of when I was listening to a lot of American Armed Forces radio (Gulf, mid-90s), 'coz they were playing the best music. They had this regular segment during the day, called Our National Heritage (or similar).
Something with a title like that on an Army station could easily be mistaken for tedious propaganda broadcasts, but it was actually very interesting. I got to learn all sorts of things about the customs, culture and history of people around the world (ok, mostly Europe).
Filed under: not much about Americans, though...
-
Actually, here's some nationalist twats being shown to be wrong. It is teh funneh.
https://www.youtube.com/watch?v=pj3F-O_62gE
For those not "in the know", Garry Bushell (the journalist who comes out with "if yer was a racist, this'd just kill yer, wuddnit?") has been known to come out with the "occasional1" racist, sexist or homophobic comment.
1 The rest of the time, he's not speaking.
-
Garry Bushell could make anything sound racist, sexist and/or homophobic. I'm still trying to work out whether Garry Bushell or Piers Morgan is the more offensive of the two.
-
That's like lumping SD and LA together.
I don't think so. SF and SJ significantly closer to each other than SD and LA. Driving along 101, there isn't any real dividing line between them; there is nowhere that isn't urban. That's mostly true along 880 between SJ and OAK, too.
-
Driving along 101, there isn't any real dividing line between them; there is nowhere that isn't urban.
QFT. My like is of your statement, not of 101 (which is firmly on my list of “roads to avoid”…)
-
Shrug. I see them as much different cities. Then again, you do have the Santa Clara 49ers.
-
Shrug. I see them as much different cities. Then again, you do have the Santa Clara 49ers.
But we're talking about metropolitan areas. There's a lot of diversity in probably every major one in that list. Those three in the Bay area seem like they're part of the same sprawl in a way that LA and SD definitely aren't.
-
you do have the Santa Clara 49ers.
I don't. I moved away before they moved to Santa Clara.
-
I don't. I moved away before they moved to Santa Clara.
You do have them as an example of your point.
-
but i know masters level lit majors that get it wrong.
They were lit majors for a reason. they're stupid.
Their inability to grasp the simplest of concepts in their own major echoes that of a CS major that can't figure out the difference between while(){} and do{}while().
-
@Intercourse said:
Is it normal for so many JSON POST methods to just hang for 15s at a time? Every one of them is 15.08s and 241B.
Extremely normal, that's the client polling for notifications....
-
Extremely normal, that's the client polling for notifications....
I know WTF it is, I just do not get why it takes 15 fucking seconds every time.
-
Because that's exactly how long the server is configured to wait before spitting out what is essentially "no changes"?
-
@Intercourse said:
I know WTF it is, I just do not get why it takes 15 fucking seconds every time.
You should google "long polling".
-
I guess it would be stupid to ask why, with all these whiz-back super futuristic atomic-age gizmos, you ain't using websockets for this?
-
I guess it would be stupid to ask why, with all these whiz-back super futuristic atomic-age gizmos, you ain't using websockets for this?
I'll pretend like that was a serious question (and I remember reading this a while ago):
https://meta.discourse.org/t/why-does-discourse-not-use-web-sockets/18302?u=boomzilla
-
Mm, I was not aware there were ISPs that actually disabled WebSockets, that actually is an ok answer. Shockingly.
His other reasons are shit though. Especially the last one.
-
For the message bus in one of our web applications, we use a custom Atom feed as the message bus. The messages are mostly “hey, go and look at this webpage (which is JSON)” passed back and forth so that we can cope with very large real messages (one of our users decided to send gigabyte-sized images via it!) but it seems to work quite well and goes through most firewalls OK as the baseline protocol is just HTTP/HTTPS (a trivial deployment option).
-
Mm, I was not aware there were ISPs that actually disabled WebSockets, that actually is an ok answer. Shockingly.
His other reasons are shit though. Especially the last one.
That's one of the great things about SignalR for .NET. It checks to see if the client can use web sockets. If the client can use web sockets, everything moves ahead. If not, then it seamlessly falls back to long polling. I'd have to double check, but IIRC, it only loads the client script that it needs for whichever solution is being used.