These are all the JSConf 2014 slides, codes, and notes I was able to cull together from twitter. Thanks to the speakers who posted them and thanks to @chantastic for posting his wonderful notes.
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
The MIT License (MIT) | |
Copyright (c) 2014 Tomas Kafka | |
Permission is hereby granted, free of charge, to any person obtaining a copy | |
of this software and associated documentation files (the "Software"), to deal | |
in the Software without restriction, including without limitation the rights | |
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | |
copies of the Software, and to permit persons to whom the Software is | |
furnished to do so, subject to the following conditions: |
Disclaimer: This is an unofficial post by a random person from the community. I am not an official representative of io.js. Want to ask a question? open an issue on the node-forward
discussions repo
- io is a fork of node v0.12 (the next stable version of node.js, currently unreleased)
- io.js will be totally compatible with node.js
- the people who created io.js are node core contributors who have different ideas on how to run the project
- it is not a zero-sum game. many core contributors will help maintain both node.js and io.js
# Hello, and welcome to makefile basics. | |
# | |
# You will learn why `make` is so great, and why, despite its "weird" syntax, | |
# it is actually a highly expressive, efficient, and powerful way to build | |
# programs. | |
# | |
# Once you're done here, go to | |
# http://www.gnu.org/software/make/manual/make.html | |
# to learn SOOOO much more. |
Kris Nuttycombe asks:
I genuinely wish I understood the appeal of unityped languages better. Can someone who really knows both well-typed and unityped explain?
I think the terms well-typed and unityped are a bit of question-begging here (you might as well say good-typed versus bad-typed), so instead I will say statically-typed and dynamically-typed.
I'm going to approach this article using Scala to stand-in for static typing and Python for dynamic typing. I feel like I am credibly proficient both languages: I don't currently write a lot of Python, but I still have affection for the language, and have probably written hundreds of thousands of lines of Python code over the years.
// Written by @iclanzan | |
// All credit goes to him! | |
// You create the reducer like this: | |
// var reducer = createTimelineReducer('someName', someReducer, ['foo', 'bar']); | |
// And then whenever an action of type `foo` or `bar` happens it calls `someReducer` and adds the result to the timeline. | |
// Then to undo/redo you trigger an action of type `someNameUndo`/`someNameRedo`. | |
var defaults = require('lodash/object/defaults'); | |
var capitalize = require('lodash/string/capitalize'); |
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft
,elem.offsetTop
,elem.offsetWidth
,elem.offsetHeight
,elem.offsetParent
Smallest possible CSS-in-JS library.
- Try demo
- 178 bytes (minified and gzipped)
- Source code fits in a tweet
- Dynamic 4th generation styling
- "jsxstyle" interface
- Pure React — no side effects
*.md diff=markdown |