QtWebEngine Poses Problems For Debian, Distribution Vendors

[GreatEmerald]

And your hard drive is 8000 GB? So what? The apps are supposed to use the space we have free. Not using space means it's a broken design, not taking advantage of the hardware.

Ever heard of SSDs?

[nanonyme]

And your hard drive is 8000 GB? So what? The apps are supposed to use the space we have free. Not using space means it's a broken design, not taking advantage of the hardware.

The saying is about RAM, not about disk storage. RAM is always better used than free since disk caches on all sane operating systems will occupy all free memory

[GreatEmerald]

The saying is about RAM, not about disk storage. RAM is always better used than free since disk caches on all sane operating systems will occupy all free memory

Actually, it's about disk storage too. Just that in case of disk storage, the free space should be occupied by snapshots.

[curaga]

I shudder to think how the perf would be if the disk was constantly writing and erasing snapshots. IO pauses every second.

[GreatEmerald]

I shudder to think how the perf would be if the disk was constantly writing and erasing snapshots. IO pauses every second.

Not constantly. Once per hour is enough (why you'd need them more often than that, anyway). Besides, making snapshots on Btrfs is free, due to CoW.

[doom_Oo7]

And your hard drive is 8000 GB?.

120 gb on my own computer, 240 gb on the 2000? MacBook Pro I have at work.

[Luke]

One-browser sites should be considered broken

ugh, Chromium... ugh
I hate the trend of sites that only work on Chrome. it is becoming the new IE.
<snip>.

I have yet to see such a site but would simply treat it as broken/down. There never has been and never will be any site on the Web I would install a special browser for. The IE issue also never came up for me since I never used the web for things like banking or shopping, and treated one-browser media as not having been posted at all.

[rdnetto]

I'm looking forward to Debian publishing a full GNOME 3.16.1. I have zero use for KDE outside of K3B and a few apps here and there. I enjoy some of the Qt Apps but I'll dump them all if the Qt/KDE continues to balloon in package numbers and drive space.

I'd rather devote 10GB to Engineering apps and not useless KDE apps

There's a pretty big difference between Qt and KDE. Traditionally, KDE was the bloated one, while Qt was pretty modular, but with KDE5 they've modularized their libraries to a much greater extent. Qt also seems to be the best library for cross-platform support - see the Subsurface video for why that's the case.

Not constantly. Once per hour is enough (why you'd need them more often than that, anyway). Besides, making snapshots on Btrfs is free, due to CoW.

I have daily snapshots on /home, and I can tell you that they are absolutely not free. The cost isn't in the storage, it's in the access time. Snapshots can cause frequently modified files to become heavily fragmented, which really sucks for mechanical hard drives. I put Chrome's cache on a tmpfs and created a separate XFS partition on my SSD for IO-heavy workloads (e.g. compiling large projects) to mitigate this. That makes it tolerable, but Chrome still takes something like 5-10 sec for a cold start.

[curaga]

Not constantly. Once per hour is enough (why you'd need them more often than that, anyway). Besides, making snapshots on Btrfs is free, due to CoW.

The way you wrote, the disk would be full constantly, so any write would trigger a removal of a snapshot, then a new snapshot would be written as space freed, ad infinitum.

[GreatEmerald]

I have daily snapshots on /home, and I can tell you that they are absolutely not free. The cost isn't in the storage, it's in the access time. Snapshots can cause frequently modified files to become heavily fragmented, which really sucks for mechanical hard drives. I put Chrome's cache on a tmpfs and created a separate XFS partition on my SSD for IO-heavy workloads (e.g. compiling large projects) to mitigate this. That makes it tolerable, but Chrome still takes something like 5-10 sec for a cold start.

You can defrag and autodefrag.

The way you wrote, the disk would be full constantly, so any write would trigger a removal of a snapshot, then a new snapshot would be written as space freed, ad infinitum.

Yes, so?