As someone who grew up in Appalachia and has since moved to NYC and built a career in tech, it hurts me to read stories like these and think about how many good people are getting left behind, due to factors largely out of their control. Sure, folks could uproot and abandon the area, but that solution is no less tragic. In terms of natural beauty, few places can rival. With a bit of enlightenment about what opportunities already exist in affordable tech education, some meaningful investment in infrastructure, and some entrepreneurs willing to get their hands dirty, we could turn this region around. Silicon Holler has a ring to it.
Investment in infrastructure would especially help, because it would create jobs that could then flow into the local economy. West Virginia is one of the most beautiful parts of America, and could have a booming tourist industry. Travel through there and you see one deindustrialized town after another where a few million dollars of investment would transform the local economy.
Not to detract from the creativity here, but the id attribute specifies its element's unique identifier[1]. Strictly speaking, this should never happen:
"strictly speaking" is right. It's invalid but all major browsers will handle the code just fine. Browsers are pretty damn forgiving.
It's also an easy mistake to make. All someone has to do is create an element with an ID in a child template without checking to see if that ID is already used in a parent template.
Is it possible to enable some switch in Chrome to force the browser to render only correct code in dev mode? This would catch me making mistakes that otherwise go unnoticed.
On the note of forgiving browsers, I love how they are a very accepting interpreter of information, much like a human listening to someone's broken English and still understanding what is being said.
I don't think any Javascript is in use at all here, but if it were I would not expect errors but instead simply unexpected behaviour as browsers tend to just try do something if what you are asking isn't clear (for instance if a jquery selector returns nothing, any changes you chain after the call just apply to that nothing instead of complaining that they expect to have some nodes to act on).
Multiple elements with the same ID is wrong of course, so you can't guarantee what will happen if you use and ID based selector: three equally (in)correct interpretations would be "act on the first element you find with that ID", "act on all elements with that ID", and "error because we don't expect to find more than one". By breaking the standard you are exposing yourself to undefined behaviour - the browser can do what it likes and each environment might do something different.
Has it actually been proven that Wal-Mart is detrimental to small retail business?
I know, it seems obvious on the face of it. Wal-Mart comes to Mayberry, and Walker's Drug Store and Foley's Grocery and Weaver's Department Store can't compete and go out of business.
...except weren't those already nailed before Wal-Mart got there by Walgreen's and Safeway and JC Penny?
I suspect that when a place is big enough to support a Wal-Mart, it's already attracted enough big national chains that the small guys are dead or dying.
Wal-Mart is able to survive and thrive in environments where other chains can't. They can be the first, not the last, big national retail chain to move in.
The town where I went to high school got one. Before they showed up, there were no other big chains of anything in that sort of business. The closest were some of the standard big chain fast food joints and gas stations. Walgreens, Safeway, JC Penney, none of them existed there.
I left before the Wal-Mart came so I didn't really see how things changed with it. I have no idea if it was good or bad for small businesses (of which there wasn't much to destroy anyway) or the town as a whole. I'm just addressing the idea that Wal-Mart would somehow be a latecomer.
The point was that you were doing it in an obfuscated way, (using shortened links), without disclosing. I don't think people generally mind when they are explicitly made aware.
The point of the article is that the first problem is not so much a problem and more of an afterthought compared to the more fundamental issues of spacing, proportion, weight, characters per line, and placement on the page, which all equal readability. Once you have considered those, you can more or less drop in whatever typeface you like and then ask yourself whether it improves or detracts from readability and whether it matches the overall tone you are trying to set with your design.
The point of the article is that the first problem is not so much a problem and more of an afterthought compared to the more fundamental issues of spacing, proportion, weight, characters per line, and placement on the page, which all equal readability.
I strongly disagree. These decisions are never independent in practice, but if anything, I’d say the specific font(s) used in a design would influence choices of spacing and layout more than the other way around. For example, I don’t think you can choose leading or justification settings well without taking into account factors like the x-height and typical character widths in your text.
