Is Mahalo Answers being crushed under the weight of kludgey ajax?
You can leave an optional "tip" with Mahalo's virtual currency, Mahalo Dollars. If you are asking a difficult question that might require some research, or if you'd like a wide variety of feedback, a higher tip often leads to more answers to your question.
M$2 Answers
It is annoying that it doesn't work perfectly, but it hasn't been running for that long so I'm sure we will see significant improvements in the future. Even Microsoft couldn't anticipate the number of users that wanted to download the Windows 7 beta and had to delay it by a day to get more servers up.
You can leave an optional "tip" with Mahalo's virtual currency, Mahalo Dollars. If you are asking a difficult question that might require some research, or if you'd like a wide variety of feedback, a higher tip often leads to more answers to your question.
M$It is being crushed. But I don't think it is script errors. I have been on Mahalo since day one and I have never had a script error.
Perfornamce has been deteriorating constantly. It has been almost unuseable this week. It is taking me 30 to 90 seconds to load each page but it never crashes and I have never had a script error.
I am using XP and IE.
I also have a MAC Pro. It is very fast. But- it is a disaster with Mahalo or with any site or application written with a lot of Java script. This occurs with either Safari or FireFox. I do not believe the MAC problems are in any way related to the Mahalo code. I have given up on using the MAC to surf the web except for news sites
Personal experience.
You can leave an optional "tip" with Mahalo's virtual currency, Mahalo Dollars. If you are asking a difficult question that might require some research, or if you'd like a wide variety of feedback, a higher tip often leads to more answers to your question.
M$
Please disregard the comment about script errors. I had both script debugging and error notices turned off. Turned on the notices and now I am a believer.
The comment about script based sites and applications on the MAC however stands as stated.
mahalo errors out in ie xp and its bad code, however when using osx, script errors should be attributed to the operating system? i never looked at it like that before, but it makes perfect sense. for 10 years i have been mistakenly taking on the burden of writing code that works in all browsers - i'm such a fool.
that doesn't make sense for all kinds of reasons, most important of all is this - if your code doesn't run well on a targeted browser then your code sucks.
I believe Jason uses a mac himself, so they know. I just can't figure out what it is they are trying to accomplish with all this client side code. If it's a ajax scaling issue then the code is uberkludge. ( i know im most likely misusing kludge a bit, but its an awesome word)