So now you'll have a box that analyzes and sends home (for "personalization" and "quality" purposes) everything you say, is always on ("just so you can activate it by voice") and is hooked to your telescreen. Yay!
don't feed it broken urls. Stick the ftp:// at the front.
Why would anyone want to ever use ftp:// for this millenium? If a protocol is default, it should be default for every hostname; I don't expect a small rodent themed page for kids to be accessed with gopher:// so neither should ftp.debian.org be accessed using some pointless ancient protocol.
Dp they use Canvas for drawing or for reading what they've drawn? It's hard to come up with a valid reason for reading, while it's use for fingerprinting is ubiquitous (due to being included in some bloat.js library).
Not sure what you mean. Bare alt does nothing, alt-letter works with the normal (ie, non-default) menu, doesn't appear to do anything with the hamburger abomination,... am I missing something?
The titlebar is a waste of space; I'm glad they got rid of it.
It's gone only on Windows. Then there's the thrice-damned hamburger menu, that's unremovable without an extension, and clumsily provides 1/10 of functionality for menu bar it purports to replace.
Great! Now please remove Pocket and Australis as well, bring tabs back to their ergonomic place not on top, stop hiding "http://" from URLs as if it were a "default" protocol (it's not -- names like ftp.*.debian.org are assumed to be FTP even if they don't support FTP anymore), drop that annoying "reader mode", etc. (Yeah, there are extensions or about:config settings to mask most of those, but most users don't know that.)
On the other hand, instead of copying Chrome, please work on actual security improvements, like DANE (currently marked "WONTFIX").
No, because of eye muscle strain. For the full theather experience, you'd also need to borrow your neighbour's kids (flashing cellphones included, as a modern movie is too boring to watch), spill some food and have it, uhm, age, have a drive beforehand, stand in a ticket queue and watch plenty of adverts beforehand.
The absolute size means diddly jack, all that counts is the angular size, at least past the distances where your eye muscles have to be strained to maintain focus.
By this, and the lack of mention of half an hour of ads, I see you're using proper releases carried by Captain Anakata rather than giving your hard-earned money to the scum of MPAA. Good.
That's your allowance, not the shitcaller's. It's them who are phoning you, why would your allowance even matter? And they certainly dial more than 1000 minutes.
Anyway: there is no reason that a DNS implementation is faster as it has the same limitations regarding disk access.
A DNS server reads zone files just once, at startup. It can do so because it has a means of getting notified of updates (rndc, zone notifies). The data is then stored in an efficient data structure that takes O(1) to find an entry (or O(k) where k is domain's length if we care about this factor, it's sharply bounded). Even without file access inefficiencies, the best a hosts file can do is O(n) (O(n*k)) -- and we can't ignore such inefficiencies, as reading and parsing a file takes ages.
(Some server implementations do O(log n) (binary tree) search rather than O(1) (hash [hopefully], trie [guaranteed]), but that's good enough to still beat a hosts file by orders of magnitude.)
It's read from disk and parsed every time you resolve anything. Which means it is in RAM...
Yeah, page cache, but this wasn't what I'm talking about. On a modern SSD the speedup from in-RAM caching isn't that massive anymore -- and unless you mounted noatime, there's a write for every operation anyway, both to the journal and inode. And then you still need to read the file and parse it to find that entry; in the most likely case, ie, a non-blocked hostname, you'll need to parse the entire file.
while a hosts file is limited to a single hostname per entry. Which it is actually not!
You can have multiple entries per line, like this: 0.0.0.0 facebook.com plus.google.com twatter.com goatse.cx but a single entry applies only to a hostname, not to the entire domain below it.
A hosts file is adequate if you have just a handful of addresses, but it really slows you down if you get more. It's read from disk and parsed every time you resolve anything. Linearly. You really want to run a local DNS server that stores the data in a proper data structure. A zone file can also block a whole domain while a hosts file is limited to a single hostname per entry.
golden days when web pages were under a megabyte on average without images
I remember being told that an image should never have more than 8KB, less if it's only a minor element.
That megabyte per page becomes far less negligible when you, say, need to visit just your bank's page when abroad (over international roaming) and a single visit (several subpages, 7MB total) sets you back $100. Now think about kids in rural Africa connecting their donated OLPCs.
Snapshots use only as much space as the delta is. You don't rewrite all files every day (unless you mount with atime...). Obviously, old snapshots can be pruned from time to time -- but I keep monthlies forever even on small SSD, despite having backups elsewhere.
Use btrfs with a daily cronjob to snapshot/, have/home on a separate subvolume (also snapshotted, but for a different reason). Anything goes wrong, you roll back / to yesterday. Want a version from two months ago? All it takes is a reboot and type subvol=sys-2016-05-18 on the grub command line. That's the key to comfortably running unstable...
Slashdot Mirror
So now you'll have a box that analyzes and sends home (for "personalization" and "quality" purposes) everything you say, is always on ("just so you can activate it by voice") and is hooked to your telescreen. Yay!
Well, in this case they tell you which OSes are toys and which are actually useful.
There is no law banning either open or concealed carry on Mars. In the absence of laws, everything is allowed.
don't feed it broken urls. Stick the ftp:// at the front.
Why would anyone want to ever use ftp:// for this millenium? If a protocol is default, it should be default for every hostname; I don't expect a small rodent themed page for kids to be accessed with gopher:// so neither should ftp.debian.org be accessed using some pointless ancient protocol.
What we need is, at least, to move away from 16:9 to 16:10 monitors
Why would 16:10 be enough? I prefer 16:12 (aka 4:3) or better.
For now, I use legacy monitors while their supplies last.
Dp they use Canvas for drawing or for reading what they've drawn? It's hard to come up with a valid reason for reading, while it's use for fingerprinting is ubiquitous (due to being included in some bloat.js library).
Not sure what you mean. Bare alt does nothing, alt-letter works with the normal (ie, non-default) menu, doesn't appear to do anything with the hamburger abomination, ... am I missing something?
The titlebar is a waste of space; I'm glad they got rid of it.
It's gone only on Windows. Then there's the thrice-damned hamburger menu, that's unremovable without an extension, and clumsily provides 1/10 of functionality for menu bar it purports to replace.
Great! Now please remove Pocket and Australis as well, bring tabs back to their ergonomic place not on top, stop hiding "http://" from URLs as if it were a "default" protocol (it's not -- names like ftp.*.debian.org are assumed to be FTP even if they don't support FTP anymore), drop that annoying "reader mode", etc. (Yeah, there are extensions or about:config settings to mask most of those, but most users don't know that.)
On the other hand, instead of copying Chrome, please work on actual security improvements, like DANE (currently marked "WONTFIX").
And they do record it. Try for example browsing with Canvas Blocker with notifications on. Pretty much every major site will trigger it.
A cat is a cherished pet, a graceful creature superior to humans. A rat (at least in public perception) is a slimy despicable thing, like MAFIAA.
No, because of eye muscle strain. For the full theather experience, you'd also need to borrow your neighbour's kids (flashing cellphones included, as a modern movie is too boring to watch), spill some food and have it, uhm, age, have a drive beforehand, stand in a ticket queue and watch plenty of adverts beforehand.
Since the Anniversary Update, not anymore.
Those people watch hazy phone cams mostly to avoid all that "theater experience" Cameron is pushing as a "good" thing.
40-foot screen
The absolute size means diddly jack, all that counts is the angular size, at least past the distances where your eye muscles have to be strained to maintain focus.
Fast-forward button for the trailers.
By this, and the lack of mention of half an hour of ads, I see you're using proper releases carried by Captain Anakata rather than giving your hard-earned money to the scum of MPAA. Good.
This tradition currently is considered to be acceptable, while the same thing for females is banned with huge penalties.
Because, you know, gender equality and shit.
That's your allowance, not the shitcaller's. It's them who are phoning you, why would your allowance even matter? And they certainly dial more than 1000 minutes.
Anyway: there is no reason that a DNS implementation is faster as it has the same limitations regarding disk access.
A DNS server reads zone files just once, at startup. It can do so because it has a means of getting notified of updates (rndc, zone notifies). The data is then stored in an efficient data structure that takes O(1) to find an entry (or O(k) where k is domain's length if we care about this factor, it's sharply bounded). Even without file access inefficiencies, the best a hosts file can do is O(n) (O(n*k)) -- and we can't ignore such inefficiencies, as reading and parsing a file takes ages.
(Some server implementations do O(log n) (binary tree) search rather than O(1) (hash [hopefully], trie [guaranteed]), but that's good enough to still beat a hosts file by orders of magnitude.)
It's read from disk and parsed every time you resolve anything. ...
Which means it is in RAM
Yeah, page cache, but this wasn't what I'm talking about. On a modern SSD the speedup from in-RAM caching isn't that massive anymore -- and unless you mounted noatime, there's a write for every operation anyway, both to the journal and inode. And then you still need to read the file and parse it to find that entry; in the most likely case, ie, a non-blocked hostname, you'll need to parse the entire file.
while a hosts file is limited to a single hostname per entry.
Which it is actually not!
You can have multiple entries per line, like this:
0.0.0.0 facebook.com plus.google.com twatter.com goatse.cx
but a single entry applies only to a hostname, not to the entire domain below it.
A hosts file is adequate if you have just a handful of addresses, but it really slows you down if you get more. It's read from disk and parsed every time you resolve anything. Linearly. You really want to run a local DNS server that stores the data in a proper data structure. A zone file can also block a whole domain while a hosts file is limited to a single hostname per entry.
golden days when web pages were under a megabyte on average without images
I remember being told that an image should never have more than 8KB, less if it's only a minor element.
That megabyte per page becomes far less negligible when you, say, need to visit just your bank's page when abroad (over international roaming) and a single visit (several subpages, 7MB total) sets you back $100. Now think about kids in rural Africa connecting their donated OLPCs.
I thought piss gives you mostly nitrogen.
Hows that free space looking, mudkip?
Snapshots use only as much space as the delta is. You don't rewrite all files every day (unless you mount with atime...). Obviously, old snapshots can be pruned from time to time -- but I keep monthlies forever even on small SSD, despite having backups elsewhere.
Use btrfs with a daily cronjob to snapshot /, have /home on a separate subvolume (also snapshotted, but for a different reason). Anything goes wrong, you roll back / to yesterday. Want a version from two months ago? All it takes is a reboot and type subvol=sys-2016-05-18 on the grub command line. That's the key to comfortably running unstable...