Yeah, it's the most do-it-yourself but is pretty difficult if your not extremely comfortable with Linux. I tried to do it a few months back (without too much C knowledge) and couldn't figure out how to cross-compile/link libraries I needed. I got it to boot into a shell (without login). At this point, I could probably do it, but I prefer sticking with really minimal distros like CRUX and Void.
There are a few reasons they split off home and root. It makes recovery simpler, and allows you to share the partition between multiple environments - which is useful if you dual boot.
I personally rarely make a second partition for home, but I always make a separate partition for /boot. GRUB requires an separate EFI partition to install (which is kind of dumb), and if you decide to encrypt your disk, the boot directory cannot be encrypted.
I think the reason they put swap in these tutorials is that many times people install linux on low-powered machines that require the swap because of limited memory. It's not a requirement to install linux, though. I never run it on installation.
Yes, but what are ways it is possible to break into a car?
Break a window (drawback: sets off a car alarm)
Duplicate or steal the a key (drawback: requires original key)
Steal car when open (drawback: not many people leave there car open)
How could you break in a Lockitron (or prevent someone from using it)?
Steal a persons phone (much easier than stealing a key. A phone is taken out more often than a set of keys)
Cut telephone wires for wi-fi (a little extreme, but possible)
Hack there password.
Besides, how much motion does it require to open a lock with a key? I guess it makes sense to use it to unlock or lock your house remotely, but when have you been in that kind of situation? If someone needs a key, just give them a copy.
How many people use touchscreen monitors for desktop computers, anyway? They make sense for tablets, but mice and trackpads are easier if your using a (physical) keyboard.
It does work, but when someone tries to reverse engineer
the code( say to write a spider ) its difficult to read.
"(b) it's fast"
Thats probably true for sections of the html, but nested tables are not the fast.
"(c) it runs on both new and old browsers"
But nested tables aren't required in older browsers, they work with divs. Besides, who uses a browser that is older than 2000?
"(e) in this context, seperation of content from formatting is overkill"
Why? It makes quick changes much easier. I was fiddling with HN on firebug and had a hard time finding where everything was. There were tons of in-line styles that kept overriding the basic styles from the CSS file.
It's always better to change things in the CSS file, because it makes changes easier later.
I'm not saying for people to never use tables. But I think they should be used for what they were originally made for: tabular data. Some people go overkill trying not to use tables and that's not a good idea. Tables work really well when they are used right.