Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements


Dave Williamson davewill here birdie birdie, get in my belly!
  • updated FTDI driver kills fake FTDI FT232

    , figuerres wrote


    ... in general the FTDI ones are the better ones.


    My experience confirms this as well.

  • i hate that volume 13 limit !!!!!

    @wkempf: Wow. Just Wow. Trying to enforce an 85 db sound level at the wrong place in the sound chain.

    This is a great example of how system requirements go off the rails. Look over there, squirrel!

    EDIT: The point being the sound level measure occurs once it has gone analog.  Requiring a techie to limit sound levels prior to going analog is the erroneous system requirement.

  • Desktop App Supported Screen Resolution

    @TheJoe: 1024x768

  • Meanwhile, at Microsoft

    @Sven Groot: Flannel RULES! :)  ... oh ok ... and electric horses.

  • Why do some programmers write code this way?

    @cbae: I can see that when the developer is focused on the domain problem and doesn't circle back to give it the technical focus.

  • So much for artists rights to their material

    Arg. Google is to music what Silk Road is to the drug trade.

    I wonder if part of their algorithm for review involves number of views. i.e. if less than X we won't worry about it because the fines won't be that bad.


  • Anyone using Azure SQL Database?

    We use SQL Azure.  Although we don't connect across the internet to it.  Going from on-premise <1 ms network latency to internet 30+ ms latency could be a biggie.

    There is no concept of a backup in SQL Azure like on-premise.  Recently Azure started offering a mechanism to make scheduled backups (on my list to further investigate).  However, if you have a need for a backup to be made before a certain business process is allowed to execute or if you have a need for a user to trigger a backup whenever they would like then that is going to be a eye opener.  Right now in SQL Azure you have to make a copy of the database and then make a backup of the copy in order to have a transactionally consistent backup.

    Another thing to consider is how disjointed the life cycle could/would become between SQL Azure and the on-premise MSSQL.  Right now all things Azure are changing at breakneck speeds and that needs to be considered.

  • Awwwww Yeah...


  • Internet or a web of networks

    , figuerres wrote


    also if the internet peering billing is done the way they used to do Telco peering it's based on even sharing of traffic and getting the other peer to pay more if they send more.

    From what they have stated that does seem to be the norm still today.  What doesn't seem to be the norm though (at least in this case it sounds like it isn't) is when the network traffic is out of balance the affected party should bill the provider on the other side of the edge.  That provider then in turn bills up their stack.  Apparently that isn't the norm today I gather.

  • Internet or a web of networks

    What is perplexing me is why the market economics don't flow back up the stack.

    customer -> last-mile ISP -> backbone ISP -> Netflix

    Unless Verizon wants to be both a last mile and a backbone network.