After using Google’s new Chrome browser for a couple of days I have to say that it shows promise as being a great choice for my go to browser. With some work. Here’s a quick rundown of my initial pros and cons…

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
I’m eager to see how the browser’s development progresses and how it impacts Firefox and IE.

OK, you borked it up for the longest time and released a new version of your comment system that was supposed to address all the harsh criticisms against the epic fail your had previously created. Well, while you made a handful of minor improvements, it still sucks.

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.

Selecting a Range of Table Cells with JavaScript

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.

Next Page »