Closed Poll: Do you have Discourse Syndrome
-
due to some unfortunate bugs in the platform.
To be clear, bugs in whose platform, Discourse or Android?
I find it interesting because I've got an app rendering a fully interactive North America map in SVG with tap-to-zoom and smooth zoom transitions... and it works better on my 7" Galaxy Tab in Dolphin with Android 4.4 than this forum.I can't scroll down in a text forum because of the ajax loading jamming the screen for several seconds even time I swipe, but I can have smooth zoom transitions on an SVG rendering?
-
We're basically building for the next 10 years, not the previous 10 years. We are 1 year into that plan.
Ok, that is a statement. A bold statement, but an honest statement.And as it is your company, you are entitled to make that decision.
Good luck.
-
Same browser ...
Not necessarily. The Samsung Galaxy Tab I have came with a stock Internet browser - just called "Internet" - but I use Chrome on it. There are also many other browsers to choose from.
... same OS ...
Do you even know how Android is put out there? Every Android manufacturer starts with the base Android OS, but they make their own adjustments for their devices. That's part of why when there's a new release of Android, the manufacturers don't push it out to the devices right away. They have to make their mods all over again, and then do a bunch of QA.
-
Not at all. Just trying to explain that you're going to see very poor performance specific to Android (1-4 seconds on tap) due to some unfortunate bugs in the platform.
Stop. Just stop. You've been told by myself and @DrakeSmith that it works fine on our Android devices. Stop attacking the OS, and look at other potential causes.
-
Stop. Just stop. You've been told by myself and @DrakeSmith that it works fine on our Android devices. Stop attacking the OS, and look at other potential causes.
This reminds me of the time @blakeyrat got all pissed of trying to debug some javascript on iOS.
Filed Under: Good times
-
Stop. Just stop. You've been told by myself and @DrakeSmith that it works fine on our Android devices. Stop attacking the OS, and look at other potential causes.
And in my case, in direct comparison to the latest iOS device (to test after seeing that exact meta discourse topic a week or so ago)
-
-
You can debug JavaScript? I thought you just kept randomly changing shit until it worked... that has always been my experience of 'debugging' JS.
-
debug some javascript
Maybe that's what they need to do for discourse on Android ...
-
You can debug JavaScript? I thought you just kept randomly changing shit until it worked... that has always been my experience of 'debugging' JS.
alert(object.property)
-
Sure you can! Just write "debugger;" in the source code and you'll create a breakpoint. Don't forget to check in code littered with them; the next developer to debug will be oh so glad you did half the work for them :)
-
Ah, so you do it the way you did it thirty years ago in BASIC: fucking print statements carefully embedded strategically into the code. Or something that smells suspiciously like an invalid function to create a breakpoint?
Awesome.
-
Or, you could use a debugger. Unless you need to debug something on an iOS device. Then you're screwed. Or at least you used to be.
-
I should have remembered to use sarcasm tags in my post. I am aware of how to debug JavaScript. These new fangled browsers even let you set your own breakpoints in the debugging panel anyway.
As for debugging on iOS, there are options for that, too.
-
I seem to remember Android adding it not too long ago, but thankfully I don't have to do much with mobile web programming
-
You can debug JavaScript? I thought you just kept randomly changing shit until it worked... that has always been my experience of 'debugging' JS.
Try Firebug on Firefox. The debugger is great, you have all the usual actions like step-in, step-out, etc.Erm... ok, it only works with Firefox, but a lot of issues you can fix on the desktop as well.
-
Sure you can! Just write "debugger;" in the source code and you'll create a breakpoint. Don't forget to check in code littered with them; the next developer to debug will be oh so glad you did half the work for them :)
And neither will be the user :-)
-
I should have remembered to use sarcasm tags in my post.
I noticed that after I started typing, and figured I'd just go with it.
As for debugging on iOS, there are options for that, too.
I stay away from the things. Have they changed since this?
-
These new fangled browsers
You just reminded me of my professor at college... in 1997 he said something like "I have heard that they brought out a version of Pascal with which you can code for Windows by now".
-
A bit. You can do all kinds of obscene things like bridging Xcode to iThingy Safari and get debug information back, but that requires having a Mac and using Xcode, neither of which are especially pleasant.
-
that requires having a Mac and using Xcode, neither of which are especially pleasant.
After doing some minor ios app work, I think I would almost rather do c++ Windows COM code.
almost
-
Appcelerator Titanium and Unity are less painful than Xcode directly. Fortunately I don't do that much stuff in iOS at present...
-
-
And what tool, pray tell, were you planning on using to compile your Swift with? Would that not be Xcode 6 as mentioned on Apple's developer page for Swift?
-
Grab an iOS device (or even a Windows phone) and test it with Discourse along an Android device - Android across the board almost takes twice as long to render a topic page. This is a problem with the plain old vanilla Android.
-
I'd suggest it's a problem with Discourse just as much as it is with Android.
Fuck me, I never thought I'd defend Android in any way.
-
Not based on the tests that @DrakeSmith has done. Also, I don't have access to an iOS device, and I don't currently have the inclination to spend the money on it.
-
Also, I don't have access to an iOS device, and I don't currently have the inclination to spend the money on it.
Note @faoileag: try Discourse on the company's iPad come Monday.Edit: during lunch break, of course.
-
Not based on the tests that @DrakeSmith has done. Also, I don't have access to an iOS device, and I don't currently have the inclination to spend the money on it.
Well to be fair, I am obviously rooted, with i/o scheduler tweaks, cpu governor tweaks, and may have been running ART instead of Dalvik at the time (but I don't remember if I was then)
-
I hear what you're saying, but I've tested it on the Moto X, Nexus 5, and Nexus 7. That's as vanilla as you get out of the box with Android. If it does work better on a different Android device, as far as I know that would be the fringe case here.
So it functions on Android, there's just an unknown causing an overall speed issue which seems to cause a few other issues. As previously mentioned... there's a fix in mind that will eventually come, but it's not trivial nor definite.
Also, considering the issue doesn't occur on any other platform - it does seem like an Android issue. No one is avoiding a fix because of this, it's just not an issue with an obvious fix within Discourse at the moment.
-
So it functions on Android
Trying out the site in my moto x to see what you all are whining about. loaf times stuck balls. Site otherwise functional. Was able to quote. Keyboard to large on landscape.
-
After doing some minor ios app work, I think I would almost rather do c++ Windows COM code.
almost
OMG! LOL!
-
-
-
Trying out the site in my Moto X to see what you all are whining about. Load times suck balls. Site otherwise functional. Was able to quote. Keyboard too large in landscape mode.
I hate typing on phones. FTFM.
-
I hate
typing on phonesposting on Discourse via mobile. FTFM.
There FTFY.Edit: did it yesterday, know how you feel.
-
To be fair, typing on a phone seems to suck regardless of the phone.
Then you realise I'm using a Nokia PureView 808, which I gather was the last Nokia smart phone (as opposed to feature phone) running Symbian on a single core and their browser which is based on Opera is slow as sin before you start. I can only imagine how painful it would be trying to use Discourse when simpler sites give it trouble.
-
-
would it be
load time sucks balls
?
-
Swype is mostly OK as an input method. Mostly. Except when the screen decides to think I lifted my finger off it for a couple of milliseconds in there, chopping a longer word up into several idiotic pieces.
No examples to hand; I use a laptop for Discoursing…
-
would it be
>load time sucks balls
?
No. Nice try. [spoiler]correct horse battery staple[/spoiler]
-
loaf times stuck balls
Is there a desktop browser addon that will autoincorrect all my words like that?
-
-
That's because Xcode is full of shit.
-
The only reason to get Xcode is to get the developer tools that come with it so you can use a real programming system.
-
It's funny you say that because things go fairly quick on my android phone. The only real lag is when I have cleared cache and dumped history...then things have to think for about 5 second a will everything tag teams my browser.
-
I don't have any issues on my android tablet or phone either, and, based on earlier comments, neither does @DrakeSmith. The only people who have issues are @awesomerobot and @codinghorror, and it appears that between the two of them, their test pool includes Nexus devices and the Moto X. I'm not sure what @DrakeSmith is running, but I've got a Galaxy Tab 4 (brand new) and an HTC Sensation 4G (2 years old). I wonder if they're just using the stock browser and not trying something better, like chrome or dolphin. Because, let's be honest, the stock android browser sucks balls.
-
Nexus devices ... the stock browser ... like chrome
On the mentioned Nexus devices Chrome is the standard browser.
-
Perceived perf is a very subjective thing.
For some a second delay is a minor inconvenience, for other's a train wreck.
-
It is also like analog modems vs. cable modems. Once you have seen it go faster, you can never go back. But if all you know is modems, you'll be happy.
Regardless, I expect Android perf will be fixed one way or the other eventually. But know that the perf regressions (Android/Chrome system level stuff we can't even touch) there are currently in the range of 3x to 4x the perf you will see on any iOS device at this time, at least for Discourse. It is really bad as a multiplier, it is not 20% slower, you will pray for page loads that are merely twice as slow.