Slashdot Mirror

← Back to Stories (view on slashdot.org)

The ASP.NET Code Behind Whitehouse.gov

Posted by kdawson on from the netcraft-confirms-it dept.

An anonymous reader writes "The author looks at the markup for the new whitehouse.gov site, launched today. It uses ASP.NET and various JavaScript libraries. It suffers from various inefficiencies, most easily remedied. Check the images and techniques used to build the site front-end."

5 of 143 comments (clear)

  1. This page is a way by Nimey · · Score: 4, Insightful

    for the author to show his superiority to the Internet. None of what he cites really matters.

    --
    Hail Eris, full of mischief...

    E pluribus sanguinem
  2. Helpful advice?? by biocute · · Score: 4, Insightful

    Many developers use the JQuery from Google's servers for improved performance and lower latency.

    Is this guy serious? Advising Whitehouse.gov to use a remote server to serve javascripts?

    --
    Virtual Betting on Facebook for non-geeks.
    1. Re:Helpful advice?? by c_g_hills · · Score: 4, Insightful

      Who said anything about hacking? It's entirely feasible that they would change the script they serve up themselves. It would allow Google to track all visitors to the site who have javascript enabled, a possible privacy violation.

  3. well at least it's not... by Cyko_01 · · Score: 4, Insightful

    ...flash based!

  4. Engineering nerds, this is an example! by Anonymous Coward · · Score: 5, Insightful

    You will encounter this sometimes in your life, and you better get used to it. Sometimes, believe it or not, things are done simply because they need to be done.

    They don't spend a lot of time laboring over every little detail, they have a list of tasks and a deadline and they do their best to meet the deadline.

    They anticipate that nerds who nitpick Battlestar Galactica episode continuity errors will likely come in and stroke their butter soaked neck beards and chortle about how this or that could be done better to achieve 5% faster page loads, or allow for translation into Swahili.

    But, they get paid either way and in the grand scheme of things trying to impress anyone on Slashdot is probably pretty low on anyone's to-do list.

    As someone who's argued with people about vi vs. emacs in the past, I can honestly say you guys have reached a new low both in wasting time, having no worthwhile point, and being worthless slashdot editors. The trifecta.