Tab where?
-
The mobile site isn't unusable for me. I mean, it works 80% of the time, which I guess is good enough for a project when I was a sophomore in college.
-
How did you manage that then? Because my screenshot was from a nexus 7. Serious question, I'm not trying to troll. Just genuinely curious what the difference might be between our nexuses
-
Because my screenshot was from a nexus 7. Serious question, I'm not trying to troll. Just genuinely curious what the difference might be between our nexuses
From my Nexus 7:
-
Yeah, like I said it's hit and miss. Possibly.related to selecting text on asingle line? That's not 100%.reproducable though so might not have anything to do with it, I dunno
-
Since I discovered it, I've never had an issue with it on either my Nexus 7 or Galaxy S5.
Latest Chrome on both devices.
-
FWIW i also have a nexus7
trying to load meta.d on it craps its pants, usually to the point that i need to force quit or restart the device to get it usable again.
what.thedailywtf will load, eventually, but it takes about 3 minutes to load /latest
also cannot load it on an ASUS VivoTab Smart which is a full windows 8.1 tablet running IE11
the Surface 3 has no trouble with it but touch events are..... spotty at best.
EDIT: This line was for a different thread:
as for the 503s.... no idea whats causing that. it sure as heck ain't my bots as when the site goes down they terminate (upon receiving even one 5xx response they will terminate.and wait to be manually restarted)
-
A 2012 Nexus 7 or a 2013 Nexus 7? Not that I'm sure what the difference really is.
I don't experience that - it loads latest in a few seconds. It's not speedy, but it's definitely not that slow.
-
2013, running fully updated AOSP.
unlocked bootloader because i did root it at one point but i have since flashed a full stock image on top of that because rooting turned out to not do what i wanted to and i wanted OTA updates more than i wanted to keep root.
i just havent bothered relocking the bootloader.
-
2013, running fully updated AOSP.
Same here. My bootloader is locked, but can't see that making any difference.
-
Those are feature requests, filed as passive aggressive "high priority" bugs.
Clarify for me.
Is the "Dismiss Posts" button in the unread tab leaving behind half-read, half-unread zombie threads almost every time it's used a "bug" or "feature request"? I'm fuzzy on the concept.
Maybe the strategy here is: "we never do any testing whatsoever, therefore we never have any bugs, therefore everything is a feature request, therefore we can deny them for any fucking reason we want."
-
You are going to see severe load time issues on Android, as android devices are literally 2x and 3x slower than iOS in Discourse. It is especially bad here because the default page size was increased from 20 to 50. Really crippling on mobile non iOS devices. I wait 11 seconds for topics to load here on the 2013 nexus 7.
https://meta.discourse.org/t/how-to-speed-up-the-mobile-experience/20140/8
I am praying Android 5.0 / L helps with the move away from godawful Dalvik to native code ala iOS.
And the Nexus 9 looks really great, as it is based on even newer version of the very strong hardware in the Nvidia Shield tablet. I already preordered one.
-
Wait... you're blaming the hardware for this?
It's the hardware's fault that your software runs slowly on it when no other forum, and indeed most of the internet, doesn't have this same problem?
-
Nope, check Mozilla Kraken benchmarks (scroll down a bit in the above link). Android web perf is abysmal.
Direct link https://meta.discourse.org/t/how-to-speed-up-the-mobile-experience/20140/17
I hope Lollipop and native fix this. It is very, very bad.
-
Nope, check Mozilla Kraken benchmarks (scroll down a bit in the above link). Android web perf is abysmal.
I hope Lollipop and native fix this. It is very, very bad.
So what if they're abysmal? They're a majority of the mobile market. And still - no other 'software that wants to be a platform' would be content with performing that badly.
Previously it was 'we're hoping for Ember.js to get faster', now you're waiting for Android to get faster? What next?
-
Yeah, i'd love to upgrade to the new nexus, but i probably wont because the screen is too big for me. I already have a perfectly capable windows tablet with a 10.1 inch screen (which even though it runs Windows on a full atom processor with 4GB of ram has worse performance than the nexus for discourse, and it blows the nexus out of the water in all the benchmarks except battery life),
what i want the nexus for is to be my small form factor tablet for reading on and extremely casual browsing
i expect it to be several years before i can get a new sub 8" tablet that runs AOSP.
I'm not saying that discourse is broken on mobile, I'm saying that it seems to require an absolute top of the line mobile device that very few people have, and it really doesn't seem like it should require that. Given the JSON API you've built for discourse i expect is would not be beyond reasonability to write a native app that could be pointed at any discourse instance in the world and get 1000x the performance.
heck, i expect i shall be attempting to write one once i get Sockbot squared away and once US FIRST robotics build season is over (because i don't expect to finish sockbot before january)
-
Which Atom? Only Bay Trail or later has decent performance on Mozilla Kraken and Google Octane. I have a Bay Trail device here I have used a fair bit and performance is fine, way better than Nexus 5 or Nexus 7.
Anything earlier than Bay trail is gonna be bad.
As for the rest, I dunno: Android is just.. kind of awful, to be honest. I used a Nexus 5 as my primary phone until the iPhone 6 was released, and every day I grew to dislike Android even more. Not just the performance, which was pretty bad, but all the crazy Windows 3.1 esque UI gaffes, like constantly being asked if I wanted to use Gmail or Email apps to send mail, and whether I wanted to use Gallery or Photos -- what the hell is the difference and why do I keep getting asked about this? Awful. After nine months I was desperate to switch back.
Still, I really do hope Lollipop and native code helps. The whole Dalvik system is bad news for web apps, as you can see from the benchmarks I linked.
-
-
I remember tapping "always" and it seemed to keep asking me regardless. I dunno. I have no idea what the difference is between email and Gmail, or photos and gallery. I guess I am not smart enough to understand Android.
-
Good thing you're not using it anymore, now that you have an iPhone.
Do the ones doing most of the work on the mobile version of Discourse at least understand it?
-
I don't think the mobile version issues are anywhere near as important as how the behavior is usually nowhere near expected. Pretty much every attempt to post brings up a new bug.
-
Nope.
I hope in 3-5 years Android will catch up with iOS perf, considering ye olde iPhone 5 is ~2x faster at Discourse (and Mozilla Kraken, Google Octane, etc) than the latest android phones.
We'll see if they are on the right track with Android 5.0 / native code soon.
I truly hope it does because right now I have a Nexus 5 I am ashamed to even give away for free, the performance is so poor.. You'd literally have a better performance story (and app choice) on an old refurbished iPhone 5. And if you can afford a 5s or 6? It is not even close.
-
Nope.
I hope in 3-5 years Android will catch up with iOS perf, considering ye olde iPhone 5 is ~2x faster at Discourse (and Mozilla Kraken, Google Octane, etc) than the latest android phones.
We'll see if they are on the right track with Android 5.0 / native code soon.
I truly hope it does because right now I have a Nexus 5 I am ashamed to even give away for free, the performance is so poor.. You'd literally have a better performance story (and app choice) on an old refurbished iPhone 5. And if you can afford a 5s or 6? It is not even close.
So what you're saying then is that it sucks to be anyone not using a top of the line device, and that it's the manufacturer's fault for giving you a non-top-of-the-line experience.
Couldn't you, say, simplify the amount of work going on client-side to alleviate these problems?
-
this place needs meaningful moderation
we actually have that (thanks @PJH) , there is no need for more
-
Wait... you're blaming the hardware for this?
You're hamster is getting fat! You need a faster one.
-
use Gmail or Email apps to send mail
Don't blame the software for your inability to choose and pick the don't ask me again button.
-
I have no idea what the difference is between email and Gmail, or photos and gallery. I guess I am not smart enough to understand Android.
That's Google's insistance on having their own apps for their own products. Gmail is, well, Gmail and Email is every other email provider.
-
I don't have an IOS device but my Blackberry Q5 loads topics faster than either my Nexus 7 or Galaxy S5 as long as it's on wifi. Knock wifi off and it doesn't make much difference which is probably then more down to carrier than anything else (BB is on
EESomething Somewhere, GS5 is on O2).
-
Couldn't you, say, simplify the amount of work going on client-side to alleviate these problems?
Nope. Because just sending content and ceasing any further activity is soooo 2000s.
-
Yeah, like I said it's hit and miss. Possibly.related to selecting text on asingle line? That's not 100%.reproducable though so might not have anything to do with it, I dunno
I have an LG G3, and I agree that getting the Quote Reply is inconsistent. About 90% of the time, the Quote reply button will appear, but the other 10% of the time, it will not show up when quoting text. In some cases, it will only show up after I have posted my reply.
-
You are going to see severe load time issues on Android, as android devices are literally 2x and 3x slower than iOS in Discourse.
Really? My stock Samsung Galaxy Tab 4 and LG G3 both load topics as quickly as my desktop does. Even my old HTC Sensation 4G was only marginally slower than my desktop. We've had this discussion before. You can't base a claim about Android on your experience with a single device.
-
Really? My stock Samsung Galaxy Tab 4 and LG G3 both load topics as quickly as my desktop does. Even my old HTC Sensation 4G was only marginally slower than my desktop. We've had this discussion before. You can't base a claim about Android on your experience with a single device.
Unfortunately, I'll have to agree with jeff.
I have Samsung Galaxy II. It's slow as hell in Chrome. Seems a bit faster in Dolphin, but it's not 100% compatible. Mobile performance is my current biggest pet peeve with Discourse.
BTW I wonder if they could improve the performance by easing off scroll tracking and other metadata collection mechanisms. It's nice that you can tell me what post I lingered on the longest last month, but I'd rather have smooth scrolling experience instead, please.
-
Really? My stock Samsung Galaxy Tab 4 and LG G3 both load topics as quickly as my desktop does. Even my old HTC Sensation 4G was only marginally slower than my desktop.
My 2013 Nexus 7 and Galaxy S5 are both noticeably slower to load Discourse than my desktop when using Chrome.
As I said before, even my bloody Blackberry loads it faster.
-
Unfortunately, I'll have to agree with jeff.
I have Samsung Galaxy II. It's slow as hell in Chrome. Seems a bit faster in Dolphin, but it's not 100% compatible. Mobile performance is my current biggest pet peeve with Discourse.
My 2013 Nexus 7 and Galaxy S5 are both noticeably slower to load Discourse than my desktop when using Chrome.
I wonder if it has to do with connection. I only use discourse on Android over WiFi. Never on a cell signal.
-
All tested this morning on the same Wifi connection (60Mb) - all swapping to cell does is make the Blackberry load more slowly so it's about the same as the others then.
-
I wonder if it has to do with connection. I only use discourse on Android over WiFi. Never on a cell signal.
Tried it on both. Slow as ass either way.
-
That's Google's insistance on having their own apps for their own products. Gmail is, well, Gmail and Email is every other email provider.
Well, then.
http://www.cnet.com/news/gmail-apps-next-version-will-support-yahoo-outlook/
-
That's a start. Bet Samsung and co still insist on providing their own separate email app though.
-
I'm fine with that, I never use it, though.
-
That's a start. Bet Samsung and co still insist on providing their own separate email app though.
Samsung insists on providing their own apps for everything.
-
Quite. The email app is one of the few that can't be disabled though.
-
disabled smishabled.
root the F**ker and force disable it.
-
disabled smishabled.
root the F**ker and force disable it.
On a Samsung? Goodbye warranty.
-
what warranty?
I've never been able to get them to honour their warranties when i called them. sure i rooted my phone, but i wasn't calling about my phone! why should the fact that the phone i am calling you on is rooted have anything to do with the bricked phone i'm holding in my other hand?
EDIT:
they also refused waranty service on a different phone because they apparently severed connection with my carrier and i should contact my carrier for service.
my carrier sent me to you and still has your phones on the shelves to sell!
-
root the F**ker and force disable it.
I like the warranty, thanks.
what warranty?
It's covered by both Samsung and the carrier, so I'd rather have it there just in case it goes wrong as the GS5 isn't exactly cheap to replace otherwise, and the warranty isn't worth the risk just to delete an app.
-
Yeah, the stock mail app is pretty harmless, since I have everything defaulting to Gmail.
-
this place needs meaningful moderation
We have meaningful moderation in the form of community norms.
...culture shift away from hate and vitriol.
LOL. It's a fun place to yell at each other in a safe way. I feel like going all SJW on you for your yearnings for cultural oppression or something, but it's too close to dinner time.
-
I appreciate the effort @kuro but this place needs meaningful moderation and culture shift away from hate and vitriol.
So you want to change TDWTF to something which no longer fulfills the psychological needs which we currently come here for? Where would we go to vent our professional frustrations to others who understand?
-
So you want to change TDWTF to something which no longer fulfills the psychological needs which we currently come here for? Where would we go to vent our professional frustrations to others who understand?
He wants TDWTF to be his idea of a forum. Which is unlikely any actual forum with actual people.
-
Relevant: Google's Product Strategy: Make Two of Everything at Ars Technica
-
Not exactly... I blame Android for having awful webapp performance for no discernable reason. Every time I test on Android it is just excruciatingly, painfully slow, and as I mentioned, I spent 9 months on Nexus 5 as my primary phone to see if the grass is greener on the other side.
It wasn't.
But the good news is that Android has sooo much room for improvement with native code in 5/L. And you should look at the Nvidia Shield Tablet and the Nexus 9, which perform unusually well, that kind of hardware improvement is what Android needs.
Look at those Kraken and Octane numbers! And Nexus 9 is a significantly improved version of that.
On the software side there is HTMLbars, and metal views, but unfortunately Ember 1.8 is performance regression town USA at the moment.
It is disappointing that Android is so slow to improve webapp perf (compared to iOS where going from iphone4s to 5 to 5s to 6 had massive increases in webapp perf in each release), but I am optimistic for the time being that 5/L can hopefully turn things around.
Asus' Transformer Book T100 convertible notebook reviewed
The NVIDIA SHIELD Tablet Review
