Atwood continues to cry that Dicsource is too big to fail.
-
+ :fa_information_disclosure:
-
Grrrr....I just updated that, too. It wasn't obvious how to save it (why only put it at the bottom of a giant page o' settings‽).
That literally JUST happened to me. And the nice "You have unsaved changes dialog" had the options backwards from what I expected so it didn't save.
-
"This shouldn't happen, right?"
-
I was surprised to find a post that was flagged by the community there.
Here is the part that probably offended them :Seems easier than complaining that the hardware doesn't run your bloatware seamlessly.
-
I was surprised to find a post that was flagged by the community there.
Here is the part that probably offended them :Seems easier than complaining that the hardware doesn't run your bloatware seamlessly.
Discourse is literally Hitler.
-
we know Jeff is a bit of a dick personally, but is he actually a shitty developer too? Is all the shouting and screaming masking the fact that he doesn't know how to address the issues in the product?
If you look at Discourse's commit history, it's mostly Sam and co. doing bugfixes and perf stuff, and Jeff's commits are almost all "move reply button a bit more to the right".
So, maybe.
Representative case:
-
he doesn't know how
You are not exactly the first to realize the possibility (probability) of this.
-
Most of which can be solved by using the versions of those frameworks served by CDNs; that way, you take advantage of all those lovely lovely caches
That may solve the bandwidth issue, but actually parsing the gigatons of JS still takes a long time. I can literally watch my CPU usage spike on my system when I load a JS-heavy page.
-
Then maybe you should upgrade from that 486 :P
-
Competence!
-
That may solve the bandwidth issue, but actually parsing the gigatons of JS still takes a long time.
Not the parsing so much as the compiling to bytecode.
Use a smart AMD loader that won't actually evaluate the factory functions that define your modules until they are first required as a dependency and you can get away with loading the lot of them and leaving them inert until necessary.
-
Couple that with the fact JITters are getting better all the time, and the startup isn't anywhere near as bad as it could be
-
gmail mobile version is a simplified interface that sucks. and it bugs you to install a phone app that is ahainst google's own mobile friendly guidelines.
but the worse slowest and unusable mobile web app champion of all is linkedin, I gave up trying to use that one
-
Unless zooming is super important to you, why not just use the official GMail and LinkedIn apps?
-
I use official gmail, but it cant be used as an example of good web app
because of this. I also would like to be able to use it with an android
fork without infecting me phone with google apps.LinkedIn, fuck them, Im not installing that on my phone.
Em 01/10/2015 20:41, "Nicholas 'LB' Braden" <
use-the-contact-form@thedailywtf.com> escreveu:
-
Certainly would explain a lot
I hate to be captain obvious but no one needs JavaScript to do what Discourse does. You can just drop an irc link at the bottom of your article and push the viewer onto Freenode if they have an irc client. If they don't, you can simply use something like kiwiirc.com to get the job done. Seems easier than complaining that the hardware doesn't run your bloatware seamlessly.
That has to be one of us. Also am I the only one who thinks that Discocourse is dog slow on everything. If I need to see disco timers every time I enter or move around in a thread you've done it wrong.
Was that in https://meta.discourse.org/t/the-state-of-javascript-on-android-in-2015-is-poor90
Went through the whole thread but didn't see that post. Maybe I just missed it...
-
It was there, it got flagged to oblivion pretty fast. I suspect the post and user got MegaJeffed as soon as a staff member was available.
-
I was pretty sure that's what had happened.
I think Jeff's idea of constructive criticism is a bit like the interview question: What would you say is your biggest weakness?
-
Come now, give Jeff a break; that was totally unpredictable. There's no way anybody could have foreseen that there might be some sort of information disclosure problem with the whispers feature!
-
Were I not a lazy person, I'd link to every post predicting that precise thing just to provide context. But lazy, so nope...
-
we know Jeff is a bit of a dick personally, but is he actually a shitty developer too? Is all the shouting and screaming masking the fact that he doesn't know how to address the issues in the product?
Once you've been promoted to "visionary", being a developer is infra dig.
-
It was marked by the community for deletion. You had to slick to expand it. Also that link doesn't appear to be working.
-
@Greg_Bulmash said:
I just ran your suggested test on Chrome on an i7 4700MQ / 16GB twice (shutting down some windows before the second run), battery settings on "power saver" and got an average of 350ms mean performance. Switching to "Balanced" and "High Performance" modes got me in the 70-80 range.
This means that you're saying someone with their 2014 high-end laptop on power saving mode is exhibiting 2012 iPhone performance... and that's a problem for you. If your app is so complex, the performance of a Haswell i7 in power-saving mode isn't going to cut it, then is it really the state of JavaScript performance in Android or is it the performance of Ember?
Maybe the iPhone 6S cores are as fast per core as a Haswell i7 without power-saving switched on (if so, Bravo for them). Or maybe the 6S's chip/browser has been tuned for this benchmark. But if I'm on the road and my laptop in power saving mode is going to bog down on Discourse, I'm not going to blame Chrome, I'm not going to blame Intel, I'm going to blame your app.
QFT
from the thread - i would have linked, but disco chrashed chrome twice. i'm not bothering now.[here's the link -bz]:
-
And the next reply to that (at least until Jeffing):
My Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz (Desktop Work PC) just lost to an iPhone :sadpanda:
Yeah, this is definitely some serious egg on Android's face.
-
Thanks. It's amazing my ipad can't have disco open in two tabs without crashing...
-
Given the age of @Greg_Bulmash's account, I would lay odds on him getting the WTDWTF treatment.
Discourse Ten Commandments:
- Thou shalt not question His Holiness
- See 1
- See 1...
-
Given the age of @Greg_Bulmash's account, I would lay odds on him getting the WTDWTF treatment.
Could be, but @falco is TL3 over there, and he's the guy who replied to Greg. Seems to be a disco
devcontributor according to his title.
-
I wonder if TDWTF still shows in their admin panel for top traffic sources:
And WTF is 62.210.181.15?
-
And WTF is 62.210.181.15?
This guy has dedicated a blog to finding out who or what is behind that IP. He seems quite concerned about it, almost paranoid and/or crazy.
Edit: After reading their main blog, it looks like it's probably a woman. Tune in next time for more exciting updates to the "random blogger is concerned by strange IP" chronicles.
-
Filed under: NSAKEY
-
@boomzilla said:
And WTF is 62.210.181.15?
This guy has dedicated a blog to finding out who or what is behind that IP. He seems quite concerned about it, almost paranoid and/or crazy.
Edit: After reading their main blog, it looks like it's probably a woman. Tune in next time for more exciting updates to the "random blogger is concerned by strange IP" chronicles.
A little googling lead me to these guys, who appear to be a datacenter:
But I think it may be a tor node or whatever they call it.
-
Whoa, hang on, wait. Is that meta.derp echoing out a publicly accessible referrer log?
I'm shocked their top 10 referrers aren't buyv1aGGra.ru
Wait... there's no keyboard shortcut for underline?
WAIT... there's no GUI button for underline?
Fuck.
-
That's from our admin panel. Which seemed pretty vanilla to me. Sorry, should have been clearer.
-
[u]Does Markdown even support underline?[/u]
-
It is always interesting to see the approach people take when they have "performance" problems. It seems to me like most just find the first thing that looks odd and point their . No one wants to take the time understand what is actually happening. Just, "Herr drr, your application is slowing my database down."
< /rant>
-
[u]Does Markdown even support underline?[/u]
I don't think it does; most dialects use _ for italics
-
I just ran your suggested test on Chrome
The user still exists, so... is that some new sort of Jeffing? (and yes, that like takes you to a 404).
EDIT: actually scratch that, none of the likes work on meta.d for me. Can anyone confirm?
-
-
Oh wow. How does that even make it into a deployed version?
Also it's nice how manually entering
/users/username
breaks your back button by doing a redirect to/users/username/activity
and leaving the previous entry in history.
-
-
Oh I hope you're fucking kidding me.
-
Underscore or its light weight clone is worth the extra include if you want less garbage js code. Functors ftw.
-
Please no...the way they implement things, that would pop up for no reason at all 20% of the time, and may God have mercy on your soul if you're on mobile.
-
This post is deleted!
-
Oh I hope you're fucking kidding me.
I am, but I wouldn't be surprised if they did.
God have mercy on your soul if you're on mobile
Mobile? That is different. ;)EDIT: I have angered the disco-gods
-
You can tell it's a fake because it doesn't say "OK" and it's a real alert not a browser-crashing javascript thing...
Filed Under: 500 Leave OK
-
No because underlines aren't semantic — think about it: you can emphasize a point, or you can make a strong point, but you can't underline a point. What would that even mean? Underline is just a styling thing; it has no semantic meaning. And besides, people would confuse underlined text for hyperlinks.
Filed under: web pedants are the worst pedants
-
Oh wow. How does that even make it into a deployed version?
How does that even make it past UAT?
What UAT?
OK, how does that even make it past QA?
What QA?
OK, how does that even make it past developer sanity check?
What developer sanity check?
OK, how does that even make it past regression testing?
What regression testing?
OK, how does that even make it past unit testing?
What unit testing?
OK, how does this get overlooked in the design document?
What design document?
Well I'm sorry, but I'm going to have to shoot you.
Right-O, sir.
Filed under: I was going to do a straight up spoof of The Cheese Shop Routine, but with all the different kinds of testing.
-
Also it's nice how manually entering /users/username breaks your back button by doing a redirect to /users/username/activity and leaving the previous entry in history.
Wait...
rifles through history API docs
-
Sam comes out with a nice summary of Discourse's perf problems.