I don't have a crystal ball, so this is of course speculation on my end, but there have been a lot of questions which i think i can attempt to answer with my knowledge of technology and the statements that Lindens made towards us.
Then there's the classic search, which doesn't use an embedded web browser and shows convenient list of results on the left, and a single result on the right. All i have heard about this is "there are no plans to deprecate the underlying protocol", so it looks like it will stay in foreseeable future, but in fact it doesn't work perfectly any longer, some entries are just missing and can't be found even if you nail the query. We expect this to get worse with time, because Linden Lab has no genuine incentive to keep this protocol working well. For now, web search tabs can be used as an alternative, but if it comes to worst, it's no big problem to make search work exactly like in V2, it's just another embedded web browser window. The only thing holding us back is that not everyone would like it.
As Linden Lab has no genuine incentive to keep this feature working, there WILL be temporary breakage. In fact there is now, with friend permissions, SVC-7104. Feel free to make yourself felt on this issue by voting and subscribing to it.
If it comes to worst, it's no major effort to make profiles work like in V2, but that's not something we're going for.
My viewer, Singularity, has had the goal of integrating Mesh content - first display, then upload - for the last 7 months. We have been working hard towards that, and hope to have something to show soon.
Henri has started a rework of Cool VL viewer with a stated goal of supporting Mesh eventually.
Phoenix viewer has no immediate plans for Mesh content support, because essentially the whole team is working on Firestorm, yet they are interested to implement Mesh support in Phoenix too if they can do it without drawing many hands away from Firestorm.
While a clean work path showing one viewer developer implement or port a feature can always be leveraged by other developers to speed up their progress, Singularity's approach has involved reworking more than 120 000 lines of code beforehand to make Mesh integration easier, spread over half a year of work. Now, because of this, we don't feel like our implementation will fit easily within Phoenix, unless they repeat that whole work. But there is still a chance that an independent implementation makes its way into Phoenix, and if we can help them with knowledge we have gained, we certainly will.
One particular i'm mildly worried about is the new inventory delivery protocol. Snowglobe 1.5 based viewers include support for that (disabled for now), but it has its bugs which would need to be ironed out quickly if the old protocol suddenly malfunctions. Also, Viewer 1.23 would not survive that.
Knowledge Base >