Bare domain name (no-www) | FAQ - NearlyFreeSpeech.NET
By default, this is the correct behavior. Using URLs of the form creates a number of problems, and we strongly recommend that you avoid it. Some of the limitations are: It creates noncanonical URLs for your site. It is highly desirable to have one URL for each page, for purposes of bookmarking, etc. Having multiple valid URLs for the same page makes your site look less popular, both in rankings and search engines. Although we don't recommend the practice, you are still welcome to use bare domains with our service. We strongly encourage you to consider the alternatives and implications before using the bare domain name. You can add the example.com alias to your site and enable hard canonical type setting.If you have NearlyFreeSpeech.NET DNS and are using your domain with a site hosted here, you can enable this option by selecting the "Add Bare Domain Forward" action on the DNS information page for your domain in our member UI.
weepy/o_O - GitHub
Microjs: Fantastic Micro-Frameworks and Micro-Libraries for Fun and Profit!
Build Management for Javascript, Coffescript and Friends - Paracode
Update, 16-feb: I’ve added Brewer.js to the review. tl;dr Find a tool that can compile coffeescript, take javascripts and vendor javascript libs, join them preserving order, and minify them into one file good for release. If that tool can do CSS/stylus/sass all the better. I pick sprockets eventually and show how you can tailor it to your needs. Its also been quite a journey and I’ve not to make it tiresome and include all of the details. Custom made concoctions This is the quickest way you can have at setting up a build for your code, and sometimes it is just enough. To do this, you can use plain cat and minify command line libraries with a Makefile, use closure compiler with ruby, or use uglifyjs with node Cakefiles. Dedicated tooling First some words about CommonJS and its module system. stitch With it, you can use CommonJS in your browser. hem Quite a new tool, looks like hem was built to provide great build experience for Spine.JS. sprockets The familiar pipeline from Rails. Brewer.js
How A Missing Favicon Broke My App for Chrome Users
Excuse me while I let off some steam. I’ve just spent many hours debugging an authentication issue that was preventing Google Chrome users from logging into a PHP web app we’re currently working on. Here are the gory details for your amusement. The app uses OAuth to authenticate against the client’s central auth service. The issue we were seeing is that Chrome users were clicking the login link, being sent out to authenticate, coming back and still being told they weren’t logged in. As I went through debugging, it became clear that the point at which the process was failing was when the CSRF tokens were being compared. Poking further, it became clear that the reason the CSRF tokens didn’t match was due to the user being given a new PHP session when they returned. Usually, if sessions go awry, the best thing to do is turn to the raw HTTP headers. Using the Network tab of the Chrome web inspector, I could see the headers for each file.
JavaScript: Warts and workarounds
When warts collide: var versus with Lexical block scope in JavaScript is broken, and though the use of with is generally considered poor form, it's a good solution to this problem. In most curly-braced languages, blocks delineate lexical scope. For example, in C or Java: { int i = 13 ; { int i = 42 ; print(i) ; } print(i) ; } this code prints 42 and then 13. But, in JavaScript: { var i = 13 ; { var i = 42 ; console.log(i) ; } console.log(i) ; } this code prints 42 and 42. In JavaScript, only functions introduce a new lexical scope and variable declarations are implicitly hoisted to this level. For instance: function f () { var i = 13 ; { var i = 42 ; print(i); } print(i) ; } Is equivalent to: function f () { var i ; i = 13 ; { i = 42 ; print(i) ; } print(i) ; } Aside: Hoisting under the hood JavaScript takes hoisting to extremes. The following program -- a lone reference to x -- provokes a reference error: x ; // ReferenceError: x is undefined but the following program is OK because var x gets hoisted:
Two Game Changing CSS 3 Features - CodeBrief
HTML and CSS has always been filled with frustration when it comes to being able to intuitively create layouts and designs. Web developers have long since sacrificed ease of implementation for accessibility and semantic purity. Basic layouts and simple aesthetics frequently require very non-trivial implementations. This is especially apparent to developers who have tasted the forbidden fruit of other platforms such as Flex, Android, et al. Until the near future. Two CSS 3 features in particular are finally solving this in a major way, making web design palatable to the code minimalist in all of us. Flexible Box Layouts The CSS 3 spec has introduced a new module which is supported by all major non-IE browsers as well as the IE 10 preview. Gone are the days of forcing a layout into a float-based implementation. Anyone coming from a Flex or Android background will immediately see the value of this. For example, consider the following layout: Child One Child Two Child Three Child Four
HTML5SQL.JS
robertpiira/ingrid - GitHub
d3.js
