[Qgis-user] QGIS 3.4.2 still very slow to work in Windows 10

[Patrick Dunford]

I run the latest 3.4.x on Linux which has been very stable and reliable.

It will be a while before 3.x is as mature and dependable as 2.x which 
was at 2.18 a very mature product that had been operating a good number 
of years.

Used to run the development version 2.99 but these days I view "stable" 
as effectively development simply because other users (not me) have 
lodged reports for hundreds of bugs that are progressing only slowly.

I wanted the new features in 3.x and would not go back to 2.18 now.

On 11/12/18 6:49 AM, Bernd Vogelgesang wrote:
> Hi,
>
> I can't contribute to your particular problems, but have some remarks.
>
> You said you "reverted" to 2.18. On Windows, you can easily run 3.x 
> besides 2.x. Do you have the same problems with 2.18?  If so, it's 
> really your personal installation that fails, I think.
>
> The node tool was redesigned in 3.x, and there is quite a discussion 
> going on, cause not so many people like the new behaviour.
>
> In general, I would like to say, that the promotion of the newest 
> release shown in QGIS is quite a bad idea: The inexperienced will not 
> hesitate to update and therefore run in every possible bug, being left 
> clueless, while the more experienced are more cautious and install it 
> only anlongside for testing purposes first.
>
> The developers are in a bad situation: They need lots of testers to 
> find bugs, but in my opinion they reach the wrong users with that 
> advertisement. (no idea how to improve this)
>
> Furthermore, the new version had a bad start, cause (as I understood) 
> last-minute-changes in dependencies caught them unprepared.
>
> Unfortunately, no one gives warnings about the major issues somewhere 
> prominently e.g. on the QGIS.org website, so you have to read the 
> mailing-list(s) and search in the issue queue yourself. In my opinion, 
> in QGIS3 the developers were a little too ambitious, but it seems they 
> also had kind of bad luck as well. Lots of features introduced are 
> somewhat bleeding-edge and need time to ripe.
>
> As I rarely use Windows, I'm not of big help. I just want to recommend 
> you to use the network installer (advanced install!) and install the 
> 2.x LTR and the 3.x LTR in parallel and update them through the 
> installer once in a while, and keep 2.18 for productive work as long 
> as you do not trust the 3.x version.
>
> The open source mantra is "release early, release often", but that 
> doesn't mean that everyone has to update early and often as well!
>