Goodbye Vivaldi
-
had high hopes for this browser but it's crashing more than ever. 3 times tonight in 5 minutes. sorry, I'm out. the search continues.
-
Sorry to see you go so fast – I'd give it a go when we reach first Beta. Hang around a bit longer, you won't regret it
-
Has there ever been a tech preview of ANY software that DIDN'T crash all the time?..lol Be patient, good thing come to those that wait.
-
I'm using windows beta 10 ( technical preview) plus vivaldi…...Yes vivaldi crashes. I wonder if it is all the cool extensions and add ons i have hooked into it. (probably). I can live with it. knock em dead vivaldi. Windows reboots whenever it feels like it. No user input required. Be strong with the translation software. Also , i think, be a browser that can render any page. Remember the bad old days when you could'nt access certain documents because of the (computer) language barrier? My fear is that . ....
Websites are now telling me my browser is incompatible with their website...Not cool.... Be a browser that speaks all the languages.
So making the others add ons and such work with your browser is a good idea. Tips and tricks and how to's .Best e-gards
-
I'm using windows beta 10 ( technical preview) plus vivaldi…...Yes vivaldi crashes. I wonder if it is all the cool extensions and add ons i have hooked into it. (probably). I can live with it. knock em dead vivaldi. Windows reboots whenever it feels like it.
Frankly I'm using vivaldi since the day one and I haven seen a single crash, just a couple of rendering crases ona single tab (black page+ dead bird).
Same with win 10, seen a lot of problems, as expected, but no crashes, freezes, reboots, blue sceeens, whatever.
Maybe you have a bad memory module or something that has nothing to do with the SW, no matter if beta or not.
-
No need to call people names. Not everybody is technically inclined and gets what an alpha version is…
-
When you release all new "Technical Preview" - elect a previous version that was a "good" with few complaints, just things that did not work and let those that download decide.
"Previous vintage release (1.0.162.9 ): - Download here" - and this will save you a lot of frustrated users and silly bug reports.
Later you can have three levels: The released version that has been properly tested, the latest good vintage, and the test and try at your own risk version.
You will be inundated with silly bugs without strict discipline now - and one way to remove those that will never ever file a consistent bug report is to never expose them. They can wish, but then be told "Thanks, but we are working on it" - "Thanks, jolly good idea!" - "Thanks, not this century". -
-