Vivaldi 3.8 RC 2 – Vivaldi Desktop Browser snapshot 2259.32/33
-
@juanvase No. That is not how coding works. Potentially, all code is influenced by all other code. They are not modules that can be plugged in and unplugged. Lines of code are interconnected, and contain decision gates that read conditions affected by completely different areas of the code. This is why patching or modifying a browser is so labor-intensive.
An apt parallel, actually, is the living body. You could as easily transplant the leg of a grown man to the body of a ten-year-old girl of different blood type. Yeah, it's a leg, like all legs are legs, but the transplant would immediately cause a shutdown of the recipient's body.
-
-
@Ruarí said in Vivaldi 3.8 RC 2 – Vivaldi Desktop Browser snapshot 2259.32/33:
@Stardust said in Vivaldi 3.8 RC 2 – Vivaldi Desktop Browser snapshot 2259.32/33:
What are the fastest?
@Stardust For the non-optimised builds we build internally, Linux (x64)
Of course...
-
@Ruarí I feel that speed should be a priority. I’m not convinced it’s time for 3.8 yet.
-
@code3 Speed is always paid attention to in Vivalidi. It will never the the primary focus. That's reserved for features. And speed will never determine whether to update or not. That's a security and web compatibility issue.
-
@Ayespy Yeah, I know, it just seems like it is in a 3.7.1 stage right now.
I think speed should be the main focus. It got much better in the last update, but we need another speed update! Making speed the main focus for one more update does not mean expecting it to be faster than chrome. Maybe not this update, but 3.9 or 4 will hopefully have more speed improvements.
-
@code3 said in Vivaldi 3.8 RC 2 – Vivaldi Desktop Browser snapshot 2259.32/33:
I think speed should be the main focus.
And yet, it's not, and won't be. That would be in contravention to Vivaldi's philosophy. It will always be a consideration. In fact in the last few months, a complete re-write of the way several aspects of the UI are invoked caused a 300% increase in speed for tab creation and window creation. So it's always being looked at. It will never be the main focus.
-
The 8-week cycle beckons later this year. Instead of Vivaldi being two weeks "late" right now, it would be basically right on time. At least that's how I hope it pans out most commonly.
-
In Compose email, create link looks strange with arrows in all buttons, maybe not something for 3.8 though
-
I'm enjoying the experimental "Translate Page" feature. It serves to solve the long-standing problem to me of the simplified Chinese characters of the mainland China. Vivaldi automatically translates them into the traditional counterparts. At last! (It's much much simpler than "translation" between languages. It's just a one-to-one replacement, such as asap -> as soon as possible.)
-
Updated [again]
-
I tried Vivaldi Stable stream (2259.33), but when I opened the page from the speed dial, the access error message appeared for a second (I could not read the message) and then went to the clicked page.
This error was not occured in the previous versions.