Hyphenated words now count as one word? plus some bugs that this has introduced

[ZayaFTW]

@leviarruda

please fix this ASAP.

@TomErikSmith

@zoran Can we get some kind of concrete update on this? It has now been a full month.

@leviarruda

Wow, more than one month and no solution from the team. This paid service is looking like public government stuff.

I get why people are upset, but I think we should be careful about assuming this is an easy problem to fix. Unless we’re software developers familiar with LingQ’s codebase, none of us really knows the scope of what’s going on behind the scenes.

Hiring additional developers isn’t necessarily a silver bullet either. Complex legacy systems, integrations, and version upgrades can be costly and time-consuming to untangle. LingQ has faced similar technical hurdles before. I share the frustration, but realistically this may be one of those situations where we have to wait for the team to work through it.

[TomErikSmith]

April 13th:

@zoran

Thanks, we will look into this.

April 16th:

@zoran

The issue should now be fixed on all platforms.

April 20th:

@zoran

Hi everyone, just an update here. We will soon release a fix for the mentioned issue. It will be reverted back. Thanks for your patience.

April 24th:

@zoran

@TomErikSmith I hope we will push a fix for this on Monday. Appreciate your patience.

May 23rd:

@zoran

The mentioned issue is fixed and we will push a fix to production soon.

June 2nd:

@zoran

We will keep hyphenated words split. This change will be reverted back in the coming days. I am sorry it’s taking a bit long, but we will push an update soon.

June 8th:

@zoran

@JulianiTOgo Everything should be back to normal soon.

It is now June 14th.

For 2 months straight we have been told that the fix is “soon” or that it is already “fixed” and the “fix” will be released “soon”…

This is the bulk of the frustration. If we were told that, “hey this is a crazy problem it will take a few months to fix”, it would be really annoying, but it is what it is. However, insted we have been repeatedly lead to believe the fix was a couple of days away for a full 2 months.

Not only this but we have never been told what happened in the first place, and why it is a problem to fix. It seems that this was a change made intentionally to merge hyphenated words, it caused unintended issues and complaints, and they decided to “revert” this change… This doesn’t seem to be a huge 2 month+ project to do… If it is, then this is a much bigger problem for the future of LingQ. That a single update can potentially just disable the platform for months on end.

PS - I don’t think @zoran is to blame here either. I think he has been mislead on this as well, and is just the unwitting messenger in this case.

[roosterburton]

LingQs word system works on an x/y coordinate basis. X word in the sentence / Y sentence. But with additional complications such as X sentence in Y paragraph. Their CWT relies on this system and small changes can create large ripples. Even thinking about making changes to their caching/word/phrase placement systems and legacy lessons would require large amounts of testing and planning. Seems like a strange change to make in the first place, with testing and compatibility an afterthought. I’m guessing some languages may benefit from the hyphenated approach. Maybe the devs will explain their reasoning when it blows over.