I started using LingQ again a few weeks ago and there are a lot of bugs, almost to the point of the reader being unusable.
Using the right arrow key to move between words stops working after one or two pages. Reloading the page fixes it, then it breaks again after a page or two.
“Paging moves to known” breaks every couple of pages meaning I go to the next page but there are still blue words on the previous page. Then I go back reload the page and move forward again. This usually fixes it temporarily.
Sometimes when reloading the page to fix one of the other problems a new blue word will pop up that wasn’t blue before.
Sometimes when you click on a blue word it will stay blue and the unhighlighted word before it will turn yellow instead. Reloading the page fixes this.
There is a big problem with hyphenated words as other threads have already mentioned.
There are probably a couple more bugs I’m not thinking of right now.
When I’m trying to read and listen at the same time, having to pause the audio and reload the site every other page really disrupts the flow.
I don’t understand how all of these bugs can even make it to the website. Is there no testing or anything before you push an update. These bugs are all so common it only takes using the reader for 5 to 10 minutes to find them.
I haven’t used the website version in ages but I saw a YouTube video showing someone else using the website version to basically jump through a lesson targetting unknown words (IE using the arrow keys). I came on the forums before jumping in, saw your post, and thought I hope this doesn’t happen to me. Sure enough, it happened to me.
Yeah the service has always been buggy but I’ve always used the iOS app and that has been much more stable over the past few years. It doesn’t have the arrow keys move to the next unknown function (I don’t think) though.
-edit-
I tried switching from Chrome to Firefox but the same thing happened. It worked for a few pages and then the arrow keys stopped working. Or rather I could go backwards but I couldn’t go forward. I mean I could page forward but the right arrow key did nothing.
LingQ can, but they won’t. It’s easy to roll back code to a working version with current source code management tools.
It takes extra time and effort to fix bugs offline, make sure the changes worked, i.e. QA, then integrate into the live version. Since LingQ already uses its paying customers for QA, why bother?
It’s beyond a joke at the moment. I paid for the lifetime membership, so I can’t exactly cancel, not to mention all the time I’ve spent creating all my lessons so I wouldn’t want to lose those, but how do people who are paying every month for this feel?
Two and a half months ago when i first reported the hyphen issue and all the bugs it brought, and they said they were going to revert it back, this is what I thought was going to happen, just roll it back to the previous state. How this is not something they are able to do Is crazy.
I mean, how does Steve Kaufmann feel? He supposedly uses the platform a lot, right? Is this acceptable to him?