Topic seems like a shchtoopid question, but I am serious on this one.
Case in point. I had set my sights on a F800gs ever since the announcement. Seemed (on paper) to be what I was looking for. Right size. Right mass. etc. Seemed similar to my KLE but with a whole heap more power, and that was my only real gripe with the KLE.
So I take one for a spin. I find the throttle totally uncontrollable, the front twitchy and rattley, and the whole ride experience unpleasant, and I rapidly turn off the bike.
But I am thinking that maybe it is a mistake to test ride a bike. Sound strange? Let me justify.
One wise guy (think it was Ama Ride Ride) here said that you have to adjust to a different bike, and that adjustment takes time. Good point. Conclusions reached after 10 mins are likely to be wrong. Maybe what you should really consider is the feedback from owners who have climbed the learning curve into the bike and ignore your own impression.
Seems I fell into a trap I keep warning my students about. - Dont judge quickly.
I have heard plenty criticism of KLEs here on the forum, but I have yet to meet an owner unhappy with the bike. We ride, we adapt and we enjoy.
If you were conteplating a KLE would you listen to SuperJuice who thinks they are for chicks and moffies, and who has probably never thrown a leg over one (or maybe even a chick ;D) or AdventureMX who has one that he regularly does three fences on, and who I watched climb the Jericho rock as if it was a speed-bump.
A sidetrack story from my line.
A few years ago I need to edit a file on a new UNIX computer. I ask if there is an editor in UNIX and someone says VI. I sukkel for hours with VI thinking I am on Candid Camera and come to the conclusion it is the most useless editor ever written and find a UNIX notepad type editor, do the edits and decide never to use VI again.
Few months later we need the code of a print spooler changed and get in an expert. I watch in awe as Andre edits code and files like a magician. Code morphs at the touch of a key.
"What editor you using?" I ask.
"VI," he says.
"Sheet!" I say. "I struggled to get the damn thing to work."
"Best and quickest editor ever written. Takes a while to get used to it - cryptic. Not for newbies. Persevere." he advises.
Now if uou need an editor for serious work you going to take my word or Andre's? Kark question. Take Andre's.
So if you thinking about a F800 you going to take my word or someone who has ridden one for a few months? Another kark question.
So why do a test ride? It may only muddy the water.
Case in point. I had set my sights on a F800gs ever since the announcement. Seemed (on paper) to be what I was looking for. Right size. Right mass. etc. Seemed similar to my KLE but with a whole heap more power, and that was my only real gripe with the KLE.
So I take one for a spin. I find the throttle totally uncontrollable, the front twitchy and rattley, and the whole ride experience unpleasant, and I rapidly turn off the bike.
But I am thinking that maybe it is a mistake to test ride a bike. Sound strange? Let me justify.
One wise guy (think it was Ama Ride Ride) here said that you have to adjust to a different bike, and that adjustment takes time. Good point. Conclusions reached after 10 mins are likely to be wrong. Maybe what you should really consider is the feedback from owners who have climbed the learning curve into the bike and ignore your own impression.
Seems I fell into a trap I keep warning my students about. - Dont judge quickly.
I have heard plenty criticism of KLEs here on the forum, but I have yet to meet an owner unhappy with the bike. We ride, we adapt and we enjoy.
If you were conteplating a KLE would you listen to SuperJuice who thinks they are for chicks and moffies, and who has probably never thrown a leg over one (or maybe even a chick ;D) or AdventureMX who has one that he regularly does three fences on, and who I watched climb the Jericho rock as if it was a speed-bump.
A sidetrack story from my line.
A few years ago I need to edit a file on a new UNIX computer. I ask if there is an editor in UNIX and someone says VI. I sukkel for hours with VI thinking I am on Candid Camera and come to the conclusion it is the most useless editor ever written and find a UNIX notepad type editor, do the edits and decide never to use VI again.
Few months later we need the code of a print spooler changed and get in an expert. I watch in awe as Andre edits code and files like a magician. Code morphs at the touch of a key.
"What editor you using?" I ask.
"VI," he says.
"Sheet!" I say. "I struggled to get the damn thing to work."
"Best and quickest editor ever written. Takes a while to get used to it - cryptic. Not for newbies. Persevere." he advises.
Now if uou need an editor for serious work you going to take my word or Andre's? Kark question. Take Andre's.
So if you thinking about a F800 you going to take my word or someone who has ridden one for a few months? Another kark question.
So why do a test ride? It may only muddy the water.
