summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorluxagraf <sng@luxagraf.net>2019-11-20 10:24:54 -0500
committerluxagraf <sng@luxagraf.net>2019-11-20 10:24:54 -0500
commit42a6679fbbe3adb5a27b4d37e8d46de14d832c3a (patch)
tree3334ec43ce3a66736910f36a44b995200b1c721c
parent918ab6e28fc377747e6ccd7883a9a6c74ac00306 (diff)
added vivaldi mobile review and ubuntu review
-rw-r--r--ubuntu1910-review.html47
-rw-r--r--ubuntu1910review.txt75
-rw-r--r--vivaldi-mobile-review.html55
-rw-r--r--vivaldi-mobile-review.txt78
4 files changed, 237 insertions, 18 deletions
diff --git a/ubuntu1910-review.html b/ubuntu1910-review.html
new file mode 100644
index 0000000..f159cc1
--- /dev/null
+++ b/ubuntu1910-review.html
@@ -0,0 +1,47 @@
+<p>Leaves are turning, temperatures dipping, sure signs – if you live in the northern hemisphere – that Canonical’s Autumn release is upon us. Ubuntu 19.10 is nicknamed Eoan Ermine – I don’t know how you pronounce it either – and it’s the best non-LTS Ubuntu release Canonical has ever put out.</p>
+<p>I should qualify that statement somewhat, because really, as the newest version, it had damn well better be the best Ubuntu ever. But it’s more than that this time around. I’ve been reviewing Ubuntu for ten years now, using and interacting with it in some form or another for another three or four years before that, and Ubuntu 19.10 is quite simply the best Ubuntu Canonical has ever released.</p>
+<p>The reason I am like 19.10 so much is that it feels insanely fast. Everyday tasks like opening applications, dragging windows, activating the search interface, and even just moving the cursor around are all noticeably faster than in 19.04.</p>
+<p>I happened to be testing a top of the line MacBook around the time I first installed the 19.10 beta on my aging Lenovo x240, and it instantly made the Mac feel like a sloth. Ubuntu 19.10 ran circles around the Mac even on much, much less powerful hardware. Nothing says success in my testing like software that makes old hardware feel newer and even if that were all you got out of Ubuntu 19.10, I’d call it a win.</p>
+<p>The speed boost is immediately noticeable from the minute you pop in the live CD, and it’s even faster when you have it installed, but that’s not all that’s new. As is typical of Ubuntu’s October release there’s a number of new features that are not quite ready for prime time, but show considerable promise including support for the ZFS file system. While still clearly labelled “experimental” (in all caps even), I have had not problems running 19.10 on a root partition formatted with ZFS. That’s not to say that you should go try it, it is EXPERIMENTAL, but it appears that what’s really lacking are tools for managing and working with ZFS. Using ZFS enables some powerful backup and replication possibilities, but the tools for working with ZFS in Ubuntu are still somewhat limited. More on that in minute.</p>
+<p>But first, let’s dig into the speed improvements and what’s new under the hood in Ubuntu 19.10.</p>
+<h3 id="like-gnome-but-fast">Like GNOME, But Fast</h3>
+
+[image="ubuntu1910-desktop.jpg" caption='The default GNOME desktop in Ubuntu 19.10']
+
+<p>Most of improvements in 19.10 can be attributed to the latest release of GNOME 3.34, the default desktop for Ubuntu. However, GNOME 3.34 is faster largely because of work Canonical engineers put in. As an aside, I think the current state of GNOME and the work Canonical has done to make it better are the best argument around for why Canonical made the right call when it shut down Unity.</p>
+<p>If you’d like to understand the finer details of what Canonical did to improve GNOME and how they did it, there’s a post over on the Ubuntu Discourse board that <a href="https://discourse.ubuntu.com/t/boosting-the-real-time-performance-of-gnome-shell-3-34-in-ubuntu-19-10/13095">goes into considerable detail</a>. The biggest takeaway is that Canonical’s engineers looked not for the typical “hot spots,” places RAM or CPU usage spiked, but what it calls “cold spots.” That is, places where GNOME was “was idle instead of updating the screen smoothly.”</p>
+<p>Canonical developers found a bunch of places where this was happening. Three that jumped out at me are improvements to how Mutter refreshes, changes that transferred some work from the GPU <em>back</em> to the CPU, and a fix to frame lagging in Xorg. The latter is interesting because one of the things that I noticed in this release is that GNOME under Wayland did not feel dramatically faster than under Xorg the way it did for me in 19.04. I lost my Wayland envy with the speed improvements in this release.</p>
+<p>Canonical’s write up of the work done to improve GNOME is also interesting for the long list of what didn’t work, and how wrong some of the developers’ initial assumptions were – especially regarding GNOME’s use of JavaScript, which turns out to have next to no effect on performance. Sorry JavaScript haters, but it turns out “assuming that JavaScript is slower than everything else written in C,” is a bad assumption.</p>
+<p>Canonical is not done improving GNOME. The project’s goal for the next release is better performance on faster, modern hardware. Then in 20.10 it wants to improve performance on older, slower machines. As Canonical’s Daniel Van Vugt puts it, “the future of Gnome Shell is bright and worth getting excited about.”</p>
+<p>Even the present is pretty bright. As primarily an i3 user, I still find GNOME Shell overkill, but in 19.10 it’s fast enough that I no longer rush to uninstall it.</p>
+<p>This release sees some tweaks to Ubuntu’s default “Yaru” themes. Yaru is a mix of light and dark elements, though as of 19.10 it’s leaning more toward the light end of the theme spectrum. Personally I rather like the new default look. Ubuntu’s mix of light and dark elements is well thought out and updates in this release include making notifications, menus, and dialogs all share the same light skin, while the top GNOME Shell panel remains dark.</p>
+
+[image="ubuntu1910-light-panels.jpg" caption="The new lighter look for Ubuntu's Yaro theme in 19.10 (composit screenshot)"]
+
+<p>If the changes aren’t to your liking both a full light theme, and full dark theme are included as well. However, to change themes you’ll need to install GNOME Tweak.</p>
+<p>As detailed above, the big news in GNOME 3.34 is the speed boost, but it also has a handful of new features worth noting. Two of the best new features are in the main search view, and in the application overview section. Here you can now group applications into folders, making it easier to organize and find frequently used apps. Creating a folder works just like it does on mobile OSes – drag one app icon onto another and a folder will be automatically created.</p>
+
+[image="ubuntu1910-gnome-folders.jpg" caption="Creating folders in GNOME 3.34."]
+
+<p>In a related feature, you can now order the types of results shown in GNOME’s global search feature. To do so head to the Search panel in settings and you can now, in addition to turning items on and off, drag and drop to reorder them. For example if you want files to always be the first results show, just drag the files option to the top of the settings list.</p>
+<h3 id="zfs-and-the-kernel">ZFS and the Kernel</h3>
+<p>The Ubuntu 19.10 installer includes an option to format the root drive using the Z file system, better known as ZFS. This support is label experimental (in all caps even), and it bears heeding this warning. Do not format your root disk to ZFS on production hardware. I went ahead and formatted a root drive with ZFS on a machine I have to return anyway, and I have had no problems (which, frankly, is amazing), but if Canonical changes some implementation detail between now and when ZFS support is declared stable, that data could be lost. Again, don’t use it now, but having kernel-level support for ZFS is a huge deal, not the least because Canonical thinks the license allows for it.</p>
+<p>Ubuntu has been working on ZFS support for quite a few years now. It started with file-based ZFS in 15.10, which drew on the work of the ZFS On Linux project. Later that support was extended to ZFS for containers in Ubuntu 16.10. Having used ZFS for my LXC containers for nearly a year now with no problems, I can say that Canonical’s handling of the ZFS implementation details makes using ZFS with LXC/LXD no different than using any other file system.</p>
+<p>Fedora and other distros also have good support for ZFS, but most distros have thus far not included kernel level support. One reason is may be that ZFS is licensed under the Common Development and Distribution License, which <a href="https://sfconservancy.org/blog/2016/feb/25/zfs-and-linux/">some claim</a> is incompatible with the GNU General Public License. Canonical and others disagree, but Canonical is one of the first to actual ship with ZFS in the kernel.</p>
+<p>Ubuntu 19.10 adds support for ZFS as the root file system and has tools to create and partition a ZFS file system layout directly from the installer.</p>
+<p>If you’re not familiar with ZFS you may be wondering why you should care. Indeed it’s possible you shouldn’t. There’s nothing wrong with ext4, the default file system used by Ubuntu (and nearly every other distro). ZFS, however, enables some powerful tools that you wouldn’t have access to otherwise, including pooled storage, disk snapshots, data integrity verification and good bit more. A full background on ZFS is beyond the scope of this article, but for those of us using Ubuntu as a workstation, the two biggest wins ZFS offers are probably pooled storage and disk snapshots.</p>
+<p>Because ZFS acts as both a file system and volume manager, it can create a file system that spans multiple hard drives (this is a “pool” in ZFS parlance). How many disks can you pool? Fun fact, Oracle <a href="https://blogs.oracle.com/bonwick/128-bit-storage:-are-you-high">has done the math</a> and fully populating a 128-bit ZFS storage pool would require more energy than boiling the oceans. Which is to say, ZFS has large datasets covered.</p>
+<p>The disk snapshots feature though is more useful on your root partition. Imagine for a moment you have root formatted to ZFS and snapshots are enabled. You install an update that breaks some piece of software you rely on. No problem, you can just roll back the file system to a prior state, effectively wiping the update. This is where Ubuntu is headed, but it’s not there yet. Getting ZFS on the root file system is easy (if EXPERIMENTAL), but there aren’t really any tools yet to manage and take advantage of ZFS’s features. If, however, Canonical can bundle a nice GUI for interacting with and managing ZFS it’s going to have an edge over the competition, especially in the enterprise market.</p>
+<p>The kernel in 19.10 is based on Linux kernel 5.3, which is notable for adding support for the new Radeon RX 5700 series graphics card, as well as the beginnings of support for Intel Speed Select which adds some easier power tuning options.</p>
+<p>Also noteworthy under the hood in the release is the inclusion of proprietary Nvidia drivers on the Ubuntu installation disk. That means you can now install the Nvidia drivers right from the start without any glitchy post-installation hassles.</p>
+<h3 id="snaps-and-bugs">Snaps and Bugs</h3>
+<p>Ubuntu 19.10 ships with quite a few more default apps as Snap packages, notably the Chromium web browser. This change is coming for all version of Ubuntu once the kinks have been worked out. This will save considerable engineering effort on Canonical’s side since it eliminates the need to build every new version of Chromium for all supported Ubuntu releases.</p>
+<p>I had no problems using the Snap version of Chromium, and indeed the only real indicator that it’s a Snap is that it takes just a bit longer to open than usual. That said, there are quite a few reports of bugs over on the <a href="https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-to-snap-transition/11179/11">relevant Ubuntu Discourse thread</a>. The main complaints seem to center around the Snap version not adopting the look when using other GNOME themes, and, for some users, problems with Chromium save dialogs. There are also edge case issues using some advanced features of the Chromium developer tools.</p>
+<p>While I can see how moving Chromium in particular to a Snap would be a huge time and effort savings for Canonical, judging by user feedback it’s not quite there yet. So far anyway, it hasn’t been pushed out to users of older Ubuntu releases.</p>
+<p>Ubuntu 19.10 ships with new ‘Media Sharing’ toggle in the Settings app, under the Sharing panel. It shares files that any DLNA or UPnP compatible device can access, which means it should have out of the box support for sharing files with smart TVs, some consoles (Playstation 4, for example), and other devices on your network. There’s a couple things to note here though. First off this feature shares three folders by default – Pictures, Videos and Music – and it shares them to every device on your LAN. If you want more fine-grained control you’re out of luck.</p>
+<p>The other more serious note is that initial release of Ubuntu 19.10 shipped with a bug that enabled this sharing by default. That’s been fixed, but if you installed 19.10 right away, definitely make sure to update your system and double-check to make sure the sharing feature is off. I tested this feature using VLC on Android to play videos. Everything works fine, but it lacks the polish and speed of Plex. Given how easy it is to install and run Plex (or my personal favorite of the DLNA players, Jellyfin), I’d suggest using a third-party media sharing app.</p>
+<p>One final note for those of you waiting on support for the Raspberry Pi 4, Ubuntu has published a <a href="https://ubuntu.com/blog/roadmap-for-official-support-for-the-raspberry-pi-4">roadmap</a>. The short story is that Ubuntu 19.10 support for the Raspberry Pi 4 model B is currently limited to the 1GB and 2GB versions. Canonical’s Galem Kayo writes on the Ubuntu blog that, “due to a kernel bug, USB ports are not supported out of the box in the official arm64 image on the 4GB RAM version.”</p>
+<p>Canonical’s engineers have identified the necessary kernel fixes and are currently testing them, but so far there’s no official support for the 4 GB model. There is, however, a workaround. I have successfully installed 19.10 on my 4 GB Raspberry Pi 4 using a boot param to tell the kernel it only has 3 GB of RAM. It’s hardly ideal, but if you want to play around with it today it is technically possible to do so.</p>
+<h3 id="conclusion">Conclusion</h3>
+<p>Ubuntu 19.10 is unusual for an October Ubuntu release in that I’d call it a must-have upgrade. While it retains some of the experimental elements Ubuntu’s Fall releases have always been noted for, the speed boosts to GNOME alone make it will worth your time. If you prefer to stick with more stable releases, most of what’s new in 19.10 will eventually be backported to 19.04 and possibly even the last LTS release, 18.04.</p>
+<p>Still, unless you’re committed to the stability of LTS releases, I see no reason not to upgrade. As I said at the beginning of this review, Ubuntu 19.10 is quite possibly the best release of Ubuntu Canonical has ever delivered and it’s well worth upgrading if you’re already an Ubuntu user and well worth trying if you’re not.</p>
diff --git a/ubuntu1910review.txt b/ubuntu1910review.txt
new file mode 100644
index 0000000..0715a54
--- /dev/null
+++ b/ubuntu1910review.txt
@@ -0,0 +1,75 @@
+Leaves are turning, temperatures dipping, sure signs -- if you live in the northern hemisphere -- that Canonical's Autumn release is upon us. Ubuntu 19.10 is nicknamed Eoan Ermine -- I don't know how you pronounce it either -- and it's the best non-LTS Ubuntu release Canonical has ever put out.
+
+I should qualify that statement somewhat, because really, as the newest version, it had damn well better be the best Ubuntu ever. But it's more than that this time around. I've been reviewing Ubuntu for ten years now, using and interacting with it in some form or another for another three or four years before that, and Ubuntu 19.10 is quite simply the best Ubuntu Canonical has ever released.
+
+The reason I am like 19.10 so much is that it feels insanely fast. Everyday tasks like opening applications, dragging windows, activating the search interface, and even just moving the cursor around are all noticeably faster than in 19.04.
+
+I happened to be testing a top of the line MacBook around the time I first installed the 19.10 beta on my aging Lenovo x240, and it instantly made the Mac feel like a sloth. Ubuntu 19.10 ran circles around the Mac even on much, much less powerful hardware. Nothing says success in my testing like software that makes old hardware feel newer and even if that were all you got out of Ubuntu 19.10, I'd call it a win.
+
+The speed boost is immediately noticeable from the minute you pop in the live CD, and it's even faster when you have it installed, but that's not all that's new. As is typical of Ubuntu's October release there's a number of new features that are not quite ready for prime time, but show considerable promise including support for the ZFS file system. While still clearly labelled "experimental" (in all caps even), I have had not problems running 19.10 on a root partition formatted with ZFS. That's not to say that you should go try it, it is EXPERIMENTAL, but it appears that what's really lacking are tools for managing and working with ZFS. Using ZFS enables some powerful backup and replication possibilities, but the tools for working with ZFS in Ubuntu are still somewhat limited. More on that in minute.
+
+But first, let's dig into the speed improvements and what's new under the hood in Ubuntu 19.10.
+
+### Like GNOME, But Fast
+
+Most of improvements in 19.10 can be attributed to the latest release of GNOME 3.34, the default desktop for Ubuntu. However, GNOME 3.34 is faster largely because of work Canonical engineers put in. As an aside, I think the current state of GNOME and the work Canonical has done to make it better are the best argument around for why Canonical made the right call when it shut down Unity.
+
+If you'd like to understand the finer details of what Canonical did to improve GNOME and how they did it, there's a post over on the Ubuntu Discourse board that [goes into considerable detail](https://discourse.ubuntu.com/t/boosting-the-real-time-performance-of-gnome-shell-3-34-in-ubuntu-19-10/13095). The biggest takeaway is that Canonical's engineers looked not for the typical "hot spots," places RAM or CPU usage spiked, but what it calls "cold spots." That is, places where GNOME was "was idle instead of updating the screen smoothly."
+
+Canonical developers found a bunch of places where this was happening. Three that jumped out at me are improvements to how Mutter refreshes, changes that transferred some work from the GPU *back* to the CPU, and a fix to frame lagging in Xorg. The latter is interesting because one of the things that I noticed in this release is that GNOME under Wayland did not feel dramatically faster than under Xorg the way it did for me in 19.04. I lost my Wayland envy with the speed improvements in this release.
+
+Canonical's write up of the work done to improve GNOME is also interesting for the long list of what didn't work, and how wrong some of the developers' initial assumptions were -- especially regarding GNOME's use of JavaScript, which turns out to have next to no effect on performance. Sorry JavaScript haters, but it turns out "assuming that JavaScript is slower than everything else written in C," is a bad assumption.
+
+Canonical is not done improving GNOME. The project's goal for the next release is better performance on faster, modern hardware. Then in 20.10 it wants to improve performance on older, slower machines. As Canonical's Daniel Van Vugt puts it, "the future of Gnome Shell is bright and worth getting excited about."
+
+Even the present is pretty bright. As primarily an i3 user, I still find GNOME Shell overkill, but in 19.10 it's fast enough that I no longer rush to uninstall it.
+
+This release sees some tweaks to Ubuntu's default "Yaru" themes. Yaru is a mix of light and dark elements, though as of 19.10 it's leaning more toward the light end of the theme spectrum. Personally I rather like the new default look. Ubuntu's mix of light and dark elements is well thought out and updates in this release include making notifications, menus, and dialogs all share the same light skin, while the top GNOME Shell panel remains dark.
+
+If the changes aren't to your liking both a full light theme, and full dark theme are included as well. However, to change themes you'll need to install GNOME Tweak.
+
+As detailed above, the big news in GNOME 3.34 is the speed boost, but it also has a handful of new features worth noting. Two of the best new features are in the main search view, and in the application overview section. Here you can now group applications into folders, making it easier to organize and find frequently used apps. Creating a folder works just like it does on mobile OSes -- drag one app icon onto another and a folder will be automatically created.
+
+In a related feature, you can now order the types of results shown in GNOME's global search feature. To do so head to the Search panel in settings and you can now, in addition to turning items on and off, drag and drop to reorder them. For example if you want files to always be the first results show, just drag the files option to the top of the settings list.
+
+### ZFS and the Kernel
+
+The Ubuntu 19.10 installer includes an option to format the root drive using the Z file system, better known as ZFS. This support is label experimental (in all caps even), and it bears heeding this warning. Do not format your root disk to ZFS on production hardware. I went ahead and formatted a root drive with ZFS on a machine I have to return anyway, and I have had no problems (which, frankly, is amazing), but if Canonical changes some implementation detail between now and when ZFS support is declared stable, that data could be lost. Again, don't use it now, but having kernel-level support for ZFS is a huge deal, not the least because Canonical thinks the license allows for it.
+
+Ubuntu has been working on ZFS support for quite a few years now. It started with file-based ZFS in 15.10, which drew on the work of the ZFS On Linux project. Later that support was extended to ZFS for containers in Ubuntu 16.10. Having used ZFS for my LXC containers for nearly a year now with no problems, I can say that Canonical's handling of the ZFS implementation details makes using ZFS with LXC/LXD no different than using any other file system.
+
+Fedora and other distros also have good support for ZFS, but most distros have thus far not included kernel level support. One reason is may be that ZFS is licensed under the Common Development and Distribution License, which [some claim](https://sfconservancy.org/blog/2016/feb/25/zfs-and-linux/) is incompatible with the GNU General Public License. Canonical and others disagree, but Canonical is one of the first to actual ship with ZFS in the kernel.
+
+Ubuntu 19.10 adds support for ZFS as the root file system and has tools to create and partition a ZFS file system layout directly from the installer.
+
+If you're not familiar with ZFS you may be wondering why you should care. Indeed it's possible you shouldn't. There's nothing wrong with ext4, the default file system used by Ubuntu (and nearly every other distro). ZFS, however, enables some powerful tools that you wouldn't have access to otherwise, including pooled storage, disk snapshots, data integrity verification and good bit more. A full background on ZFS is beyond the scope of this article, but for those of us using Ubuntu as a workstation, the two biggest wins ZFS offers are probably pooled storage and disk snapshots.
+
+Because ZFS acts as both a file system and volume manager, it can create a file system that spans multiple hard drives (this is a "pool" in ZFS parlance). How many disks can you pool? Fun fact, Oracle [has done the math](https://blogs.oracle.com/bonwick/128-bit-storage:-are-you-high) and fully populating a 128-bit ZFS storage pool would require more energy than boiling the oceans. Which is to say, ZFS has large datasets covered.
+
+The disk snapshots feature though is more useful on your root partition. Imagine for a moment you have root formatted to ZFS and snapshots are enabled. You install an update that breaks some piece of software you rely on. No problem, you can just roll back the file system to a prior state, effectively wiping the update. This is where Ubuntu is headed, but it's not there yet. Getting ZFS on the root file system is easy (if EXPERIMENTAL), but there aren't really any tools yet to manage and take advantage of ZFS's features. If, however, Canonical can bundle a nice GUI for interacting with and managing ZFS it's going to have an edge over the competition, especially in the enterprise market.
+
+The kernel in 19.10 is based on Linux kernel 5.3, which is notable for adding support for the new Radeon RX 5700 series graphics card, as well as the beginnings of support for Intel Speed Select which adds some easier power tuning options.
+
+Also noteworthy under the hood in the release is the inclusion of proprietary Nvidia drivers on the Ubuntu installation disk. That means you can now install the Nvidia drivers right from the start without any glitchy post-installation hassles.
+
+### Snaps and Bugs
+
+Ubuntu 19.10 ships with quite a few more default apps as Snap packages, notably the Chromium web browser. This change is coming for all version of Ubuntu once the kinks have been worked out. This will save considerable engineering effort on Canonical's side since it eliminates the need to build every new version of Chromium for all supported Ubuntu releases.
+
+I had no problems using the Snap version of Chromium, and indeed the only real indicator that it's a Snap is that it takes just a bit longer to open than usual. That said, there are quite a few reports of bugs over on the [relevant Ubuntu Discourse thread](https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-to-snap-transition/11179/11). The main complaints seem to center around the Snap version not adopting the look when using other GNOME themes, and, for some users, problems with Chromium save dialogs. There are also edge case issues using some advanced features of the Chromium developer tools.
+
+While I can see how moving Chromium in particular to a Snap would be a huge time and effort savings for Canonical, judging by user feedback it's not quite there yet. So far anyway, it hasn't been pushed out to users of older Ubuntu releases.
+
+Ubuntu 19.10 ships with new ‘Media Sharing’ toggle in the Settings app, under the Sharing panel. It shares files that any DLNA or UPnP compatible device can access, which means it should have out of the box support for sharing files with smart TVs, some consoles (Playstation 4, for example), and other devices on your network. There's a couple things to note here though. First off this feature shares three folders by default -- Pictures, Videos and Music -- and it shares them to every device on your LAN. If you want more fine-grained control you're out of luck.
+
+The other more serious note is that initial release of Ubuntu 19.10 shipped with a bug that enabled this sharing by default. That's been fixed, but if you installed 19.10 right away, definitely make sure to update your system and double-check to make sure the sharing feature is off. I tested this feature using VLC on Android to play videos. Everything works fine, but it lacks the polish and speed of Plex. Given how easy it is to install and run Plex (or my personal favorite of the DLNA players, Jellyfin), I'd suggest using a third-party media sharing app.
+
+One final note for those of you waiting on support for the Raspberry Pi 4, Ubuntu has published a [roadmap](https://ubuntu.com/blog/roadmap-for-official-support-for-the-raspberry-pi-4). The short story is that Ubuntu 19.10 support for the Raspberry Pi 4 model B is currently limited to the 1GB and 2GB versions. Canonical's Galem Kayo writes on the Ubuntu blog that, "due to a kernel bug, USB ports are not supported out of the box in the official arm64 image on the 4GB RAM version."
+
+Canonical's engineers have identified the necessary kernel fixes and are currently testing them, but so far there's no official support for the 4 GB model. There is, however, a workaround. I have successfully installed 19.10 on my 4 GB Raspberry Pi 4 using a boot param to tell the kernel it only has 3 GB of RAM. It's hardly ideal, but if you want to play around with it today it is technically possible to do so.
+
+### Conclusion
+
+Ubuntu 19.10 is unusual for an October Ubuntu release in that I'd call it a must-have upgrade. While it retains some of the experimental elements Ubuntu's Fall releases have always been noted for, the speed boosts to GNOME alone make it will worth your time. If you prefer to stick with more stable releases, most of what's new in 19.10 will eventually be backported to 19.04 and possibly even the last LTS release, 18.04.
+
+Still, unless you're committed to the stability of LTS releases, I see no reason not to upgrade. As I said at the beginning of this review, Ubuntu 19.10 is quite possibly the best release of Ubuntu Canonical has ever delivered and it's well worth upgrading if you're already an Ubuntu user and well worth trying if you're not.
diff --git a/vivaldi-mobile-review.html b/vivaldi-mobile-review.html
new file mode 100644
index 0000000..26e0f7d
--- /dev/null
+++ b/vivaldi-mobile-review.html
@@ -0,0 +1,55 @@
+<p>Vivaldi, makers of the power user’s favorite web browser, have finally released a mobile version. Vivaldi for Android (sorry iOS users, it’s Android-only for now) brings most of what’s great about Vivaldi to your phone, and thanks to Vivaldi’s sync service you can have all your desktop data on your mobile device.</p>
+<p>Web browsers are perhaps the most important piece of software we use. Our devices are often little more than small windows onto the web. The web browser is what we use to see and explore what’s in that window. For all their importance though, the modern web browser, especially the mobile web browser, offers precious little in the way of features. It displays the web and that’s about it. Want to interact with what you see? You’re mostly out of luck.</p>
+<p>Most people probably like their browser this way. Google, maker of the most widely-used mobile browser, rarely does anything without extensive user testing. If Chrome is minimalist it’s safe to assume it’s that way because Google has determined that’s what its users want. And since most other browsers copy whatever Google Chrome does, most mobile web browsers end up very minimalist pieces of software.</p>
+<p>On the desktop there has long been an exception to the uniformly dumbed-down offerings of Chrome, Firefox, and Safari – Vivaldi.</p>
+<p>Led by CEO Jon S. von Tetzchner, co-founder and former CEO of Opera, Vivaldi’s primary goal is to build a useful browser, a tool you can bend to your will rather than the other way around. Vivaldi is a tool you can customize the way you like, its preferences may be overwhelming at first glance, but if you dig in you can make Vivaldi do just about whatever you want it to do. For this reason Vivaldi is often called a “power user’s browser”. As opposed, I guess, to the powerless user’s browser.</p>
+<p>For all that there was always one big problem with Vivaldi: it was desktop only. The company said it was working on a mobile version from the beginning, and von Tetzchner told me several times he was already using it, but there was nothing for the rest of us.</p>
+<p>Now Vivaldi Mobile is here, for Android users at least. Technically it’s a beta release and all the common cautions regarding beta software apply, but I’ve been using it for over a month now and have had no problems. Or, I should say, I have had problems, but updates prior to the public release eliminated all of them. And even if there were still bugs, Vivaldi would still be more useful than any other browser on my phone – and yes, I’ve tried nearly all of them, even the small, cottage efforts.</p>
+<h2 id="sync-and-mobile-ui">Sync and Mobile UI</h2>
+<p>Vivaldi Mobile is surprisingly feature-complete for a beta release.</p>
+
+[image="vivaldi-ui-explainer.png" caption='Vivaldi Mobile beta interface explained.']
+
+<p>The headlining feature for now – aside from the mere existence of a mobile version, finally – is the syncing. Building on the syncing support that debuted in <a href="https://arstechnica.com/gadgets/2018/10/vivaldi-2-0-review-meet-your-ideal-browser-if-youre-willing-to-invest-time/">Vivaldi’s 2.0 release</a>, all your bookmarks, tabs, history, and notes are now available on your phone.</p>
+<p>The sync happens both ways of course, so I can click the cloud icon at the top of the browser on my laptop and get quick access to any open tabs on my phone. Notes and bookmarks from my phone appear whenever a sync happens.</p>
+<p>If you, like me, make heavy use of Vivaldi’s bookmarks, notes, and history search, having this synced to your phone is enough to make Vivaldi Mobile more powerful than other mobile browsers, but of course Vivaldi’s take on mobile isn’t limited to syncing.</p>
+<p>Unlike your more minimalist mobile browsers, Vivaldi adds a menu bar to the bottom of the page, giving you quick thumb access to a series of options along the bottom of the screen. On the left is the mobile version of Vivaldi’s Panel, which brings up a new screen that contains bookmarks, history, notes, and downloads. Swipe horizontally to move between them.</p>
+
+[image="vivaldi-ui-explainer.png" caption='Vivaldi Mobile beta interface explained.']
+
+<p>Unlike the desktop, you can’t add anything to this panel (frankly, it wouldn’t really make sense to, it’s an overlaying screen that hides the rest of your content, not a side panel).</p>
+<p>The bottom menu bar also offers back and forward buttons, speed dial, and access to all your open tabs. The center button is actually context-based, so it’s a speed dial button on a web page, but when you’re in speed dial it becomes a search button.</p>
+
+[image="vivaldi-bookmarks.jpg" caption='Click the panel button and Vivaldi Mobile will bring up the panel with bookmarks, history, notes and downloads. You can swipe to move between panes.']
+
+<p>When you scroll content, the both the bottom menu bar and the URL bar are hidden away, maximizing the amount of space available for the actual website. Scroll up and both bars come back. This strikes a nice balance between having the tools you want at your fingertips, and yet also being able to focus on the content of a webpage.</p>
+<p>At the top of the screen there’s a URL bar and Vivaldi icon. As with the desktop version you can prefix your searches with a letter to use different search engines. For example, the string “d Vivaldi” would search DuckDuckGo for the term “Vivaldi”. The mobile version supports the same search engines found in the desktop version.</p>
+<p>Tap the Vivaldi icon and you’ll get a main menu very similar to what you’ll see in Chrome or Firefox, though there are some Vivaldi-specific customizations, like an option to clone the current tab, add a bookmark, access your recent tabs, or grab a screenshot of the current page. The latter will produce a screenshot of either the current viewport or the entire page. Screen captures are, unfortunately, not currently synced with the desktop.</p>
+<p>You can work around the lack of image sync using a separate sync service like Nextcloud or Dropbox. I set up Nextcloud to automatically upload anything in the Vivaldi screen captures folder on my phone and sync it to the Vivaldi screen captures folder on my laptop. It’s not ideal, but until Vivaldi supports syncing images, it works. I should also note that Vivaldi doesn’t currently sync images attached to notes. You do get all your notes synced from the desktop, but not the images that go with them. Currently there does not seem to be a way to add an image to a note in Vivaldi Mobile.</p>
+<p>There’s also a bug in the UI that doesn’t allow you to add a URL when manually creating a note in Vivaldi Mobile. The developers are aware of this and I was told it would be fixed after launch. For now, if you like having your notes attached to a URL, use the “copy to note” option in the context menu, which will create a note with your highlighted text and attach the current URL to the note.</p>
+<p>The main menu is where you access the settings for Vivaldi Mobile. It’s early days for Vivaldi Mobile so there’s currently nowhere near the level of settings and UI control you’ll find in the desktop version. There’s all the standard settings inherited from Chromium – passwords, payment methods, saved address controls, notification settings, privacy, accessibility and so on – along with some Vivaldi-specific controls like the option to set your default search engine and sign into your Vivaldi sync account.</p>
+
+
+[image="vivaldi-colors.jpg" caption='As with the desktop version, Vivaldi will changes the accent colors of the browser based on the site you're visiting.']
+
+<p>One of the things that sets Vivaldi apart on the desktop is the way it allows you to interact with the web more than most browsers. The best thing about the mobile version is that Vivaldi has stuck with this approach of doing more. The tools for interacting with the web, creating notes for example, are largely the same in the Mobile Version. For example, select some text and the context menu that appears will have an option to “copy to note”, which mirrors the context menu on the desktop.</p>
+<p>Similarly, tools like page capture don’t just exist, but are easy to access – just one tap to open the main menu, another to capture the page – which is refreshing change from the usual, “bury it five menus down so it’s not the way” approach of other browsers.</p>
+<h3 id="whats-not-there">What’s Not There</h3>
+<p>Like Google’s mobile version of Chrome – which is also built off the Chromium project – Vivaldi has left extensions to the desktop for now.</p>
+<p>Originally Vivaldi did try to enable extensions. In fact, I suspect this is part of what took so long for the mobile version to be released. The problem, according to von Tetzchner, was that it quickly became apparent that to support extensions Vivaldi would risk lagging behind when Chromium release updates.</p>
+<p>Extension support requires significant changes to Chromium code, changes that it would be up to Vivaldi to maintain (and continue to update down the road, should Chromium change anything). Vivaldi has opted, for now at least, to make sure that it stays up-to-date with Chromium releases even though that means no support for extensions in the mobile version.</p>
+<p>It’s worth noting here that Vivaldi Mobile compiles its own version of Chromium. Many smaller browsers without the programming resources of, for example, Google or Opera, simple render pages with the version of Chromium that ships with Android. While this works, the system version of Chromium doesn’t get updates very often. This is why larger browser makers, including Google, ship with their own bundled version of Chromium with their browsers. This is what Vivaldi is doing as well.</p>
+<p>I point this out because in theory it is possible that down the road Vivaldi could decided the maintenance effort of customizing Chromium to add support for extensions is workable, though personally I would not hold my breath.</p>
+<p>While I am not a heavy extension user (in desktop Vivaldi I use only three extensions), I do miss some kind of ad blocker. Like the mobile version of Chrome, Vivaldi Mobile has an option “Block Ads on Abusive Sites”, but it doesn’t block much.</p>
+<p>I’d love to see Vivaldi embrace some kind of built-in ad blocking solution on mobile. This is one place I think <a href="https://arstechnica.com/information-technology/2019/05/review-opera-once-led-web-browser-innovation-it-has-new-ideas-again-with-reborn-3/">Opera Mobile</a> has an edge over Vivaldi.</p>
+<p>I recognize that I am writing this on a website at least partly supported by advertising, which has a certain irony to it, but on mobile ad-blocking seems like an even more legitimate feature due to bandwidth constraints. Ad blocking on mobile saves bandwidth, which translates to saving money for many users.</p>
+<p>For now you’ll have to live with ads in Vivaldi Mobile, just like you live with them in Chrome. If want ad blocking on mobile your options are Opera, or Firefox with an add-on. Alternatively you can do what I do: disable JavaScript. That stops ads and a host of other things I find irritating, but of course it also breaks half the web. I have go through and whitelist sites where I want JavaScript, which is time consuming and not for most people.</p>
+<h3 id="its-the-beginning-but-its-enough">It’s the beginning, but it’s enough</h3>
+<p>If you like Vivaldi on the desktop you’re going to like it on a phone as well. It’s still early days, and there are half a dozen things I’d like to see added to Vivaldi Mobile, especially support for user profile switching.</p>
+<p>Still, the syncing features alone make this a welcome release for anyone at all invested in Vivaldi’s various tools. Bringing your notes, bookmarks, and other data to mobile is the first step. In the end it may be the only step you really need.</p>
+<p>Much of Vivaldi’s appeal lies in its tools that go beyond mere browsing. With Vivaldi you can take notes, grab screenshots and attach them to notes, create web panels, view two (or more!) pages side by side, and so on.</p>
+<p>But the form factor of mobile devices discourages this kind of participatory browsing. The longer I’ve used Vivaldi Mobile the more I’ve realized the limitations of the form factor. Typing is awkward, even just selecting text can be an exercise in frustration at times. In some ways mobile is meant to be passive.</p>
+<p>For instance, while I think I want to add sites to the Panel like I can on the desktop (where I keep reference sites, and chat windows just a click away), where would the panel <em>go</em> on mobile? I’d want it to be near fullscreen to interact with, but then how would that be different than just another page in a tab?</p>
+<p>Another thing I use all the time is tab tiling. If you have a big enough phone this might work. Some of my testing was done on a Sony Xperia 1, which is tall enough to make tab tiling workable with a horizontal split, but on most phones I think tab tiling would make tabs too small to be useful.</p>
+<p>In the end I’ve come to the conclusion that the main thing I ever really wanted from Vivaldi Mobile, is exactly what this release gives you – a good browser, all your data, and key extras like note support.</p>
+<p>Perhaps less really is more. Then again, I like to think Vivaldi has clever people thinking up clever ways to take all those features I just mentioned and bring them to mobile in way that makes them just as great as they are on the desktop.</p>
diff --git a/vivaldi-mobile-review.txt b/vivaldi-mobile-review.txt
index bd973d6..19a2c7a 100644
--- a/vivaldi-mobile-review.txt
+++ b/vivaldi-mobile-review.txt
@@ -1,41 +1,83 @@
-Vivaldi, makers of the most powerful little browser of the web, have finally released a mobile version.Vivaldi for Android (sorry iOS users, for now it's Android-only) brings what's great about Vivaldi to your phone, and syncs all your data to your mobile device.
+Vivaldi, makers of the power user's favorite web browser, have finally released a mobile version. Vivaldi for Android (sorry iOS users, it's Android-only for now) brings most of what's great about Vivaldi to your phone, and thanks to Vivaldi's sync service you can have all your desktop data on your mobile device.
-Web browsers are perhaps the most important piece of software we use. Our devices are often little more than small windows onto the web. The browser is what we use to see and explore what's in that window.
+Web browsers are perhaps the most important piece of software we use. Our devices are often little more than small windows onto the web. The web browser is what we use to see and explore what's in that window. For all their importance though, the modern web browser, especially the mobile web browser, offers precious little in the way of features. It displays the web and that's about it. Want to interact with what you see? You're mostly out of luck.
-For all their importance though, the modern web browser, especially the mobile web browser, offers precious little control to the user. It used to be the web browser was a tool, but these days most browsers feel like stripped down minimalist affairs. Nowhere is this more true than the mobile web browser, which for the most part barely exists. The UI is hidden away, most features from the desktop version are tucked away deep in menus. Just using finding the forward button in Firefox Mobile takes three taps.
+Most people probably like their browser this way. Google, maker of the most widely-used mobile browser, rarely does anything without extensive user testing. If Chrome is minimalist it's safe to assume it's that way because Google has determined that's what its users want. And since most other browsers copy whatever Google Chrome does, most mobile web browsers end up very minimalist pieces of software.
-Complain about it, perhaps even file a bug report, and the legions of self-appointed UI experts will jump in to tell you how wrongity wrong wrong you are. The philosophy of mobile web browsers is something along of the lines of: take what you get and been happy we gave it to you.
+On the desktop there has long been an exception to the uniformly dumbed-down offerings of Chrome, Firefox, and Safari -- Vivaldi.
-Probably most people like it this way. Google rarely does anything without testing, so if Chrome in minimalist it's because that was Google has determined that's what its users want. And since most other browsers just copy whatever Chrome does, all mobile web browsers end up as very minimal pieces of software.
+Led by CEO Jon S. von Tetzchner, co-founder and former CEO of Opera, Vivaldi's primary goal is to build a useful browser, a tool you can bend to your will rather than the other way around. Vivaldi is a tool you can customize the way you like, its preferences may be overwhelming at first glance, but if you dig in you can make Vivaldi do just about whatever you want it to do. For this reason Vivaldi is often called a "power user's browser". As opposed, I guess, to the powerless user's browser.
-On the desktop there has long been an exception to the uniformly dumbed down offerings of Chrome, Firefox, and Safari -- Vivaldi. Vivaldi first came upon the Ars radar in early 2015.
+For all that there was always one big problem with Vivaldi: it was desktop only. The company said it was working on a mobile version from the beginning, and von Tetzchner told me several times he was already using it, but there was nothing for the rest of us.
-Led by CEO Jon S. von Tetzchner, co-founder and former CEO of Opera, Vivaldi's primary goal is to build a useful browser, a tool. Vivaldi is often called a "power user's browser". As opposed, I suppose, to the powerless user's browser.
+Now Vivaldi Mobile is here, for Android users at least. Technically it's a beta release and all the common cautions regarding beta software apply, but I've been using it for over a month now and have had no problems. Or, I should say, I have had problems, but updates prior to the public release eliminated all of them. And even if there were still bugs, Vivaldi would still be more useful than any other browser on my phone -- and yes, I've tried nearly all of them, even the small, cottage efforts.
-By the time Vivaldi 2.0 rolled around last year, it was clearly on to something. I even called it the cure for the common browser.
+## Sync and Mobile UI
-For all that there was one problem with Vivaldi: it was desktop only. The company said it was working on a mobile version from the beginning, and von Tetzchner told me several times he was already using it, but there was nothing for the rest of us.
+Vivaldi Mobile is surprisingly feature-complete for a beta release.
-Now that's changed, Vivaldi Mobile is here. Technically it's a beta release and all the common cautions regarding beta software apply, but I've been using it for over a month now and have had no problems. Or I should say, I have had problems, but updates prior to the public release eliminated all of them. And even if there were still bugs, Vivaldi would still be more useful than any other browser on my phone -- and yes, I've tried nearly all of them, even the small, cottage efforts.
+The headlining feature for now -- aside from the mere existence of a mobile version, finally -- is the syncing. Building on the syncing support that debuted in [Vivaldi's 2.0 release](https://arstechnica.com/gadgets/2018/10/vivaldi-2-0-review-meet-your-ideal-browser-if-youre-willing-to-invest-time/), all your bookmarks, tabs, history, and notes are now available on your phone.
-### Vivaldi on a Phone
+The sync happens both ways of course, so I can click the cloud icon at the top of the browser on my laptop and get quick access to any open tabs on my phone. Notes and bookmarks from my phone appear whenever a sync happens.
-If you like Vivaldi on the desktop you're going to like it on a phone as well.
+If you, like me, make heavy use of Vivaldi's bookmarks, notes, and history search, having this synced to your phone is enough to make Vivaldi Mobile more powerful than other mobile browsers, but of course Vivaldi's take on mobile isn't limited to syncing.
+Unlike your more minimalist mobile browsers, Vivaldi adds a menu bar to the bottom of the page, giving you quick thumb access to a series of options along the bottom of the screen. On the left is the mobile version of Vivaldi's Panel, which brings up a new screen that contains bookmarks, history, notes, and downloads. Swipe horizontally to move between them.
+Unlike the desktop, you can't add anything to this panel (frankly, it wouldn't really make sense to, it's an overlaying screen that hides the rest of your content, not a side panel).
+The bottom menu bar also offers back and forward buttons, speed dial, and access to all your open tabs. The center button is actually context-based, so it's a speed dial button on a web page, but when you're in speed dial it becomes a search button.
+When you scroll content, the both the bottom menu bar and the URL bar are hidden away, maximizing the amount of space available for the actual website. Scroll up and both bars come back. This strikes a nice balance between having the tools you want at your fingertips, and yet also being able to focus on the content of a webpage.
+At the top of the screen there's a URL bar and Vivaldi icon. As with the desktop version you can prefix your searches with a letter to use different search engines. For example, the string "d Vivaldi" would search DuckDuckGo for the term "Vivaldi". The mobile version supports the same search engines found in the desktop version.
+Tap the Vivaldi icon and you'll get a main menu very similar to what you'll see in Chrome or Firefox, though there are some Vivaldi-specific customizations, like an option to clone the current tab, add a bookmark, access your recent tabs, or grab a screenshot of the current page. The latter will produce a screenshot of either the current viewport or the entire page. Screen captures are, unfortunately, not currently synced with the desktop.
-### Notes
+You can work around the lack of image sync using a separate sync service like Nextcloud or Dropbox. I set up Nextcloud to automatically upload anything in the Vivaldi screen captures folder on my phone and sync it to the Vivaldi screen captures folder on my laptop. It's not ideal, but until Vivaldi supports syncing images, it works. I should also note that Vivaldi doesn't currently sync images attached to notes. You do get all your notes synced from the desktop, but not the images that go with them. Currently there does not seem to be a way to add an image to a note in Vivaldi Mobile.
-functionality, syncing
+There's also a bug in the UI that doesn't allow you to add a URL when manually creating a note in Vivaldi Mobile. The developers are aware of this and I was told it would be fixed after launch. For now, if you like having your notes attached to a URL, use the "copy to note" option in the context menu, which will create a note with your highlighted text and attach the current URL to the note.
-easier to do complex things. like what: you can't take notes, you're not using it as a tool. screen capture. private tabs, cloud tabs, etc, not hidden, easy to access.
+The main menu is where you access the settings for Vivaldi Mobile. It's early days for Vivaldi Mobile so there's currently nowhere near the level of settings and UI control you'll find in the desktop version. There's all the standard settings inherited from Chromium -- passwords, payment methods, saved address controls, notification settings, privacy, accessibility and so on -- along with some Vivaldi-specific controls like the option to set your default search engine and sign into your Vivaldi sync account.
-compile the browser ourselves, not using the rendering on phone.
+One of the things that sets Vivaldi apart on the desktop is the way it allows you to interact with the web more than most browsers. The best thing about the mobile version is that Vivaldi has stuck with this approach of doing more. The tools for interacting with the web, creating notes for example, are largely the same in the Mobile Version. For example, select some text and the context menu that appears will have an option to "copy to note", which mirrors the context menu on the desktop.
-add-ons: mobile chromium code has a lot of code disabled, including extensions. Changing that code might make vivaldi lag on updates, making it less secure, so we didn't want to do that. We have to weight the benefits against the costs.
+Similarly, tools like page capture don't just exist, but are easy to access -- just one tap to open the main menu, another to capture the page -- which is refreshing change from the usual, "bury it five menus down so it's not the way" approach of other browsers.
-Beta release
+### What's Not There
+
+Like Google's mobile version of Chrome -- which is also built off the Chromium project -- Vivaldi has left extensions to the desktop for now.
+
+Originally Vivaldi did try to enable extensions. In fact, I suspect this is part of what took so long for the mobile version to be released. The problem, according to von Tetzchner, was that it quickly became apparent that to support extensions Vivaldi would risk lagging behind when Chromium release updates.
+
+Extension support requires significant changes to Chromium code, changes that it would be up to Vivaldi to maintain (and continue to update down the road, should Chromium change anything). Vivaldi has opted, for now at least, to make sure that it stays up-to-date with Chromium releases even though that means no support for extensions in the mobile version.
+
+It's worth noting here that Vivaldi Mobile compiles its own version of Chromium. Many smaller browsers without the programming resources of, for example, Google or Opera, simple render pages with the version of Chromium that ships with Android. While this works, the system version of Chromium doesn't get updates very often. This is why larger browser makers, including Google, ship with their own bundled version of Chromium with their browsers. This is what Vivaldi is doing as well.
+
+I point this out because in theory it is possible that down the road Vivaldi could decided the maintenance effort of customizing Chromium to add support for extensions is workable, though personally I would not hold my breath.
+
+While I am not a heavy extension user (in desktop Vivaldi I use only three extensions), I do miss some kind of ad blocker. Like the mobile version of Chrome, Vivaldi Mobile has an option "Block Ads on Abusive Sites", but it doesn't block much.
+
+I'd love to see Vivaldi embrace some kind of built-in ad blocking solution on mobile. This is one place I think [Opera Mobile](https://arstechnica.com/information-technology/2019/05/review-opera-once-led-web-browser-innovation-it-has-new-ideas-again-with-reborn-3/) has an edge over Vivaldi.
+
+I recognize that I am writing this on a website at least partly supported by advertising, which has a certain irony to it, but on mobile ad-blocking seems like an even more legitimate feature due to bandwidth constraints. Ad blocking on mobile saves bandwidth, which translates to saving money for many users.
+
+For now you'll have to live with ads in Vivaldi Mobile, just like you live with them in Chrome. If want ad blocking on mobile your options are Opera, or Firefox with an add-on. Alternatively you can do what I do: disable JavaScript. That stops ads and a host of other things I find irritating, but of course it also breaks half the web. I have go through and whitelist sites where I want JavaScript, which is time consuming and not for most people.
+
+### It's the beginning, but it's enough
+
+If you like Vivaldi on the desktop you're going to like it on a phone as well. It's still early days, and there are half a dozen things I'd like to see added to Vivaldi Mobile, especially support for user profile switching.
+
+Still, the syncing features alone make this a welcome release for anyone at all invested in Vivaldi's various tools. Bringing your notes, bookmarks, and other data to mobile is the first step. In the end it may be the only step you really need.
+
+Much of Vivaldi's appeal lies in its tools that go beyond mere browsing. With Vivaldi you can take notes, grab screenshots and attach them to notes, create web panels, view two (or more!) pages side by side, and so on.
+
+But the form factor of mobile devices discourages this kind of participatory browsing. The longer I've used Vivaldi Mobile the more I've realized the limitations of the form factor. Typing is awkward, even just selecting text can be an exercise in frustration at times. In some ways mobile is meant to be passive.
+
+For instance, while I think I want to add sites to the Panel like I can on the desktop (where I keep reference sites, and chat windows just a click away), where would the panel *go* on mobile? I'd want it to be near fullscreen to interact with, but then how would that be different than just another page in a tab?
+
+Another thing I use all the time is tab tiling. If you have a big enough phone this might work. Some of my testing was done on a Sony Xperia 1, which is tall enough to make tab tiling workable with a horizontal split, but on most phones I think tab tiling would make tabs too small to be useful.
+
+In the end I've come to the conclusion that the main thing I ever really wanted from Vivaldi Mobile, is exactly what this release gives you -- a good browser, all your data, and key extras like note support.
+
+Perhaps less really is more. Then again, I like to think Vivaldi has clever people thinking up clever ways to take all those features I just mentioned and bring them to mobile in way that makes them just as great as they are on the desktop.