Pros:

• Fast
• Fast. I mean really fast
• Intuitive to use
• Did I mention it’s fast?
• Great new features. I love being able to tear off and rearrange tabs, searching and bookmarking are cake, and it doesn’t seem to have any obscure page rendering issues.
• Easy to use download manager
• Auto hide status bar
• Runs better than IE8 beta.
• Cool Opera-like start page

Cons:

• No home button in the toolbar
• No print preview
• No Undo Close Tab feature like Firefox has.
• No add-ons (yet). Chrome’s source code is available now so we’ll see what happens with that. Adblock is my favorite Firefox extension and if Chrome can get something similar (yes I realize Google owns Adsense) then it will be a huge plus.
• Lacks some basic customization features

Why? A)  Check any DOM inspector and you’ll see that your comment system makes a BAJILLION individual AJAX  calls to load each and every user icon. I mean c’mon, is it really that hard to display user comments? Bulletin boards and forums have been able to do this for years without nearly as much trouble as you’ve had. If slashdot can do it right all these years, maybe you can learn too.

Second, why on God’s green Earth did you decide to hide all the replies to any comment I Digg down? What logic did you apply in thinking that whenever I think comment X sucks, that you must then hide all the replies to comment X? In fact, many replies to comment X are often exactly what I thought in the first place and should be displayed! Perhaps its time you stopped thinking that Digg was the shit, and started realizing that ever since you expanded Digg’s reach to try and attract potential suitors to buy your site, that in reality you made it an ever increasing honeypot for spammers and advertisers to post completely worthless and intelligence insulting drivel that no one with half a brain reads. I used to Digg and submit stores all the time, now I visit weekly to see on the off chance if anything interesting has popped up. Sadly, this is becoming less and less frequent. Your core users are what made Digg great and you’ve decided to turned a deaf ear toward them. Maybe you’ll  realize one day that they once made Digg the enjoyable site that it once was.

What may seem like a trivial issue when trying to allow a user to select a range of table cells actually is far more complex. I was designing a simple calendar system for a client and thought why not give them the ability to select a range of cells if they want to enter an event компютри втора употребаmebeli that spans several days or weeks. How hard could that be I thought? Stupid me.

if (hours < 24 && minutes < 60 && seconds < 60)
{
 return true;
}
else
{
 return false;
}

This is known as Allman style (named after Eric Allman, the developer of sendmail). The most common variant of this would be K&R style (from Kernighan and Ritchie’s book The C Programming Language) and the same code looks like this:

if (hours < 24 && minutes < 60 && seconds < 60) {
 return true;
} else {
 return false;
}

Equivalent in every way except readability. Some people call this “The One True Brace Style” because it’s been around so long. The major difference is that the opening bracket is placed at the end of the line that the control statement is on where in Allman style the brackets are each on their own line.

To me it makes sense to make code as readable as possible by lining up brackets to match the block they go with. It becomes apparent what blocks of code belong to what conditions.

Allman style

K&R style

If I was to have another condition nested within the example, it would look like this:

if (hours < 24 && minutes < 60 && seconds < 60)
{
 if(hours % 2 == 0)
 {
 	return true;
 }
 else
 {
 	return false;
 }
}

Again, very readable.

The funny thing about K&R style is that its roots seems to be based in the fact that programmers used to have to deal with limited screen space and by squishing the brackets together with the blocks that they belonged to, it saved precious screen real estate. Most programmers either picked up the style they use most often from learning coding in a class or by following the examples set by others, while other programmers code for readability, especially now that space isn’t the issue it once was.

While Allman and K&R are just two of the most popular styles (see
http://en.wikipedia.org/wiki/Indent_style and
http://en.wikipedia.org/wiki/Programming_style
for some others and a detailed explanation about the history of each)

(please pardon the less than perfect wordpress code formatting)

But the space? Why does the space need a special code (  or  )? Well technically   and   aren’t just spaces, they’re non-breaking spaces. What’s so special about that you ask? The difference between "just an average space" and the "non-breaking space" is that while a typical space between text will allow the text to be broken up on multiple lines, the non-breaking space does just what it’s name implies and prevents the text from breaking. Here’s a quick example. Let’s say you have some text that is being squeezed due to other elements on your page. So the text "non breaking text" ends up like this:

You can see that the text has been broken up on multiple lines. What happens if we absolutely need to have the text all on one line and want to prevent the browser from automatically breaking it? This is where the non-breaking space comes in handy. By substituting regular spaces with non-breaking ones you get:

This obviously breaks the 50 pixel width we specified, however it does keep the text from breaking. Now if you’re like me, you’ve known about the   tag forever and never given it a second thought. You might also have run into it when looking at code from other folks or from some HTML editors, especially when people try to indent things manually like:       Section 1. Older versions of FrontPage were especially guilty of trying to be overly helpful by using   in places that it didn’t belong, or when content was pasted into it. Older versions of Netscape also used to pitch a fit if a table cell was encountered with no content in it and the easy workaround was to throw a   tag in the cell to appease the browser. Thankfully most of today’s better HTML editors know when to properly apply the   tag and now so do you.

Note: Also check out the <nobr> tag (which was never a formal part of any HTML standard) and CSS nowrap attribute.