305 karma · joined April 10, 2010
1.7.1 How to read this specification
This specification should be read like all other specifications. First, it should be read cover-to-cover, multiple times. Then, it should be read backwards at least once. Then it should be read by picking random sections from the contents list and following all the cross-references.
That being said, to an end user, the difference between 100 nanoseconds and 100 milliseconds is - probably - very small.
Designers should be working to eliminate unnecessary and repetitive interactions that get in the way of accessing content.
Mathematics aside, you would've hoped that they could come up with an improvement over the iMac, instead of a copy. Perhaps the port access on the side of the base counts?
If you're interested in web standards and design, http://www.alistapart.com/ is also a great site to follow.
Thanks!
e.g. www.google.com.
That trailing dot is never used in a web browser, but it most certainly does exist.
ccTLDs are a great idea, but somewhere around 60% of the top million websites in the world are run off of .com domains; there's no guarantee that a country could block an entire gTLD or ccTLD and successfully limit all questionable content.
Link to paper: http://research.microsoft.com/apps/pubs/default.aspx?id=6452...
; <<>> DiG 9.3.2 <<>> @localhost thepiratebay.org A
; (2 servers found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5372
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;thepiratebay.org. IN A
;; ANSWER SECTION:
thepiratebay.org. 3587 IN A 194.71.107.15
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Feb 1 15:37:02 2012
;; MSG SIZE rcvd: 50</code>Has any petition there led to an actionable response from the WH? Curious.
...and coding fail. Put the JavaScript at the bottom of the document.
1) No source code.
2) Incomplete test results. Why showcase two webkit engine based web browsers (Safari and Chrome) but not include a screenshot from Firefox?
3) Factual inconsistencies.
FTA:"The IE team have been chanting a mantra ad nauseum : Same Markup. That means, write once and have it render the same on all browsers. Funny, but the other browsers have been doing that for years. Seems, from the images above that it’s IE that’s unable to render the same markup."
Last I checked, implementing transitions/background gradients (etc.) in CSS required a separate line for webkit, mozilla, etc.
1: Provide time-billing transparency 2: Give away some free time, but make it visible
#2 was a very obvious point, but one that I hadn't really thought about until reading it. Qualifying the value you're providing can definitely improve the relationship you have with your customer.