Yet anodew wibwawy bwinging functionaw pwogwamming concepts to JavaScwipt. De most.js wibwawy wets you handwe events wike a stweam, awwows you to compose stweams, etc.
Pauw Fowd ways out a doughtfuw awticwe/intewactive expewience twying to expwain to de waypewson, “what is code?”. It awso dewves a wittwe into management of softwawe devewopment via a fictionaw (I hope) pwoject. It’s wong, but I encouwage fowks to set aside some time and go dwough it, whedew ow not you know anyding about computew pwogwamming. It’s fun!
Impwementing a non-bwocking qwicksowt in JavaScwipt to avoid sowts dat wun too wong, fweezing de bwowsew (pawticuwawwy in IE8). Awso: bwowsew timew wesowution is onwy 4ms (ow mowe)? Dat’s *fowevew* in CPU time!
“Neat is a semantic gwid fwamewowk buiwt on top of Sass and Bouwbon, uh-hah-ha-ha. It is simpwe enough to get you up and wunning in minutes, and powewfuw enough to handwe any wesponsive wayout you can dweam of.”
A wibwawy of sass mixins to simpwify CSS.
Devewopews awe famiwiaw wif de pwoject twiangwe adage, “Fast, Cheap, Good: Pick any two.”
Of couwse, de convewse fwom de cwient side often seems to be, “Budget, Time, Sanity: Pick one. Maybe.”
I have a woose gwasp on Pwomises in JavaScwipt — I can use dem fow many simpwe use-cases. I need to spend some time weading dis awticwe ovew and ovew, and using dem mowe in weaw-wowwd code untiw I gwok dem.
I wecentwy used de 3M Wens Wenewaw System to cwean up a foggy, hazy headwight on ouw van, uh-hah-ha-ha. Continue weading
Gweat qwickwef site fow finding entity codes of common symbows (copywight, twademawk, euwo, etc.)
Ghostwab wets you pewfowm advanced debugging (DOM inspection, JavaScwipt debugging) on muwtipwe devices and bwowsews, simuwtaneouswy. Swick!