W3c: Fill & Download for Free

Over the years, here are my top websites that every web developer must see and examine indepth and why I believe they are important:CSS Zen Garden (The Beauty of CSS Design) - The CSS Zen Garden opened my eyes to CSS and gave me a great understanding of the difference between presentation and structure. On the site, the HTML is the same across all pages...the only thing different is the CSS.Sitepoint (SitePoint – Learn HTML, CSS, JavaScript, PHP, Ruby & Responsive Design) - I believe Sitepoint to be a great site to learn a number of web technologies. Most of the tutorials are bite-sized and great to digest and learn from.A List Apart (For People Who Make Websites) - A List Apart is another site for the latest web technologies and providing value and assistance for web developers.DZone (DZone: Programming & DevOps news, tutorials & tools) - I first chatted about this site back in 2006 on my site (dZone: Digg for developers) and I've been a dedicated reader ever since. I particularly like the web technologies, architecture, and mobile sections they recently added.W3C (World Wide Web Consortium (W3C)) - I always like to see what's on the horizon for the web by examining the drafts and future RFP. I especially use the W3C Validator (Markup Validation Service) for checking my website.GitHub (Build software better, together) - If you want to learn how to write web applications, there is a ton of code on GitHub to show you so many techniques in CSS, JavaScript, and other various server languages that it would take you months to cover everything on the site, but it's a great place to learn.Smashing Magazine (Smashing Magazine – For Professional Web Designers and Developers) - Another great tutorial site that provide detailed tutorials and leave the reader to continue with their imagination. I have bought several of their books and they are definitely worth the money.MSDN Magazine (https://msdn.microsoft.com/en-us/magazine) - Since I'm more Microsoft oriented, I visit the site every month to find the source code for the offline magazine articles as well as the online articles.Code Project (For those who code) - The reason I like this site is because of the tutorials written by other developers. I've learned a lot from this site and used some code as a springboard to expand on their examples.PluralSight (Unlimited, online training for IT, Developer and Creative pros) - For the formal training. I've always liked Pluralsight for learning new web technologies relatively quick.Hope this helped.(Don't forget to upvote!)

Netscape shopped the technology around W3C before taking it to ECMA.I managed the relevant part of W3C, and I didn't think W3C should get into standardizing programming languages.One reason has to do with the Rule of least power. It's very much on purpose that HTML is not a programming language, unlike contemporary technologies such as TeX and nroff.Also, I believe that at the time, I didn't think the time was right to give any one programming language a privileged place in the web. I think IE supported VBScript, and I thought tcl/python/perl/scheme should be allowed to compete. Perhaps I was right that it was too early to pick a winner; perhaps not. I don't recall exactly when this happened.I think some of the staff (e.g. TimBL) were open to the idea, but not supportive enough to move all the relevant mountains. Maybe one or two were strongly against on technical grounds. In particular, noone on the staff made the effort to put together a proposal to the membership that W3C should take on the work. So the Netscape folks took the work to ECMA, where the process for starting work is quite different.I'm reasonably happy with the result, in any case. The folks who are stewarding Javascript these days seem to be doing really well.Maybe we could have fixed a few warts if W3C had taken it on sooner than ECMA, but I think it's not likely.p.s. Interesting... Carl Cargill, one of the people who I'm pretty sure talked with me about whether W3C should work on Javascript, writes "... Microsoft had just forced Netscape to standardize JavaScript in Ecma." in Why Standardization Efforts Fail

There are roughly four mechanisms for determining your location:Country-specific versions of Google search, for example for France, suggest you are in that country.You tell us via the Location preferences in Search Settings.Geo-location of your IP. We have a database mapping IP addresses to rough (approximately city-level) locations. This is how most of the web implements load balancing and nearest-server detection.Through the W3C Geolocation API, which allows your browser to use various signals (such as visible wifi networks or a GPS) to calculate an accurate location and share that with a site. This is the most accurate but generally requires a per-site opt-in.Mapping your IP to a rough location is the most common and sufficiently accurate for the needs of most searches. The W3C Geolocation IP is more accurate, but as it requires special permission, less common. I believe we currently only use it for searches from mobile devices, where an accurate location is more useful.