4 ms·
To comment on the dynamic DOM - we're displaying up to three answer types (text, code, links) for each question. We're loading them independently to get informa
by wayy 4y ago
To comment on the dynamic DOM - we're displaying up to three answer types (text, code, links) for each question. We're loading them independently to get information to the user as fast as possible. The alternative (in this state) is to have all of them wait until the slowest component finishes. We're still in the early stages of development, so either way it's not going to be perfect. I can see how this can be a poor experience for some - we're working on it.
- visarga 4y agoMaybe not everyone understands that the Q&A responses have to go through a large language model before they are displayed. This takes time, showing something while the LM is churning away is a good idea.
- wayy 4y agoYep, the current loading bar attempts to do that (replaced by the slowest generated answer when available). Definitely looking into new ways to improve speed + loading experience if necessary.
- unsafecast 4y agoA placeholder empty box that gets populated when the content arrives would be an improvement.
- joshstrange 4y agoSide-by-side is the best way to handle this. Show results on the left and load in the ML stuff on the right after it loads. This prevents content-jump and makes the results less wide (you want to aim for <700px to be more readable).