The End
I've decided to stop writing DailyJS. It's part of my weekday ritual, and so it's a difficult decision to make, but it's time to move on to other things. I love writing regularly, but mistakes have started to creep in that mean it's difficult for me to publish articles with the level of confidence that I'd like. There's been a small community of contributors that have made DailyJS great and encour
Small Modules: Tales from a Serial Module Author
Sindre Sorhus is the author of over 600 modules on npm. He recently wrote a long GitHub comment about why we should use small modules, and I asked for permission to reproduce the text on DailyJS. Read on to learn about why small modules make programming easier, and why it's not really about lines of code. People get way too easily caught up in the LOC (Lines Of Code) argument. LOC is pretty much
DailyJS: Z3d, is-progressive, Japanese Translations, textlint
Z3d Z3d (GitHub: NathanEpstein/Z3d, License: MIT, Bower: z3d) by Nathan Epstein is a library that generates 3D plots. It gives you a Three.js scene, so you can further manipulate the graph with the Three.js API. One of the useful things about Z3d is it has sensible built-in defaults, so you can throw data at it and get something cool out. The basic example is just plot3d(x, y, z), where the argume
DailyJS: JavaScript Developer Survey 2014: Results
The JavaScript Developer Survey has now closed. As always the results are available to the community for further analysis: Summary Raw spreadsheet data (gzipped CSV) Results for 2013 Results for 2012 97% of readers write client-side code, while 56% said they write server-side code. Last year server-side development was at 28%. I’d like to think that the interest and adoption of technologies like N
DailyJS: JavaScript Developer Survey 2014
Here is the JavaScript Developer Survey for 2014! You have two weeks from now to complete the survey (the 15th of December). I asked for help with the questions last year, and collected pull requests and issues to improve the survey. You can view the survey repository at alexyoung/dailyjs-survey. Many thanks to everyone who has helped so far. Please fill out the survey and share it with your fello
DailyJS: The Node Advisory Board
The Node.js Advisory Board has been announced, and it aims to be an “open governance model” that helps advise Node’s development. That doesn’t mean it will take control of Node, but help Node’s core team with certain key decisions. Node’s leadership has changed several times over the years, but having a single leader has so far kept the project tightly focused. I love the choices for things that g
DailyJS: Confused About Components
Client-side development has been shifting away from monolithic libraries. While jQuery is still hugely popular, building projects from smaller libraries is increasingly common. To make this easier to deal with, projects have appeared to manage dependencies. These tools may be simple package managers, or a combination of a build tool and a package manager. Recent History Client-side package manager
DailyJS: The Art of Error
Error was originally a character in the hit video game, "Zelda". I like to define a lot of objects that inherit from Error. I find it helps me to track down issues – post-mortem – but also to clearly handle expected errors. Sometimes writing error handling code feels like a chore, but it shouldn’t be an afterthought. Well-designed and well-tested errors will help you maintain projects, but also he
DailyJS: JavaScript Developer Survey 2013: Results
The JavaScript Developer Survey has now closed. As always the results are available to the community for further analysis: Summary Raw spreadsheet data (zipped CSV) Results for 2012 51% of readers write client-side code, while 28% said they write server-side code. Last year client-side was at 98%, so I imagine this is partly due to a changing audience on DailyJS, but it’s interesting how strong se
DailyJS: JavaScript Developer Survey 2013
Here is the JavaScript Developer Survey for 2013! You have two weeks from now to complete the survey (the 12th of December). Loading... I asked for help with the questions last week, and the response was incredible! I really appreciate the suggestions, and I’ve made a list of the pull requests that I accepted. Any that weren’t accepted were either due to a clash with another suggestion, or lack of
DailyJS: Debugging with Mocha
I do a lot of work with Mocha, because I like to write well-tested Node projects. Sometimes there are things I just can’t figure out non-interactively, and that’s when I reach for the debugger. It’s a lot better than repeatedly running tests with more and more console.log statements. Rather than using any extra Mocha extensions, I find Node’s standard debugger works great. With Mocha you access it
DailyJS: Backbone.js Tutorial: Updates for 1.0, Clear Complete
Part 1: Build Environment Part 2: Google's APIs and RequireJS Part 3: Authenticating with OAuth2 Part 4: Backbone.sync Part 5: List Views Part 6: Creating Lists Part 7: Editing Lists Part 8: Deleting Lists Part 9: Tasks Part 10: Oh No Not More Tasks Part 11: Spies, Stubs, and Mocks Part 12: Testing with Mocks Part 13: Routes Part 14: Customising the UI Part 15: Updates for 1.0, Clear Complete Prep
DailyJS: JavaScript Developer Survey 2012: Results
The JavaScript Developer Survey has now closed. As always the results are available to the community for further analysis: Summary Raw spreadsheet data 98% of readers write client-side JavaScript, which is unchanged from last year. I included Meteor because it’s had so much press this year, but it seems like it’s still not very popular, at 2%. I’ve always felt like this survey could be useful to t
DailyJS: Totally Testacular
We are now 100% relying on @testacularjs. Finally! plus.google.com/11032358723052…— AngularJS (@angularjs) October 18, 2012 Vojta Jina created Testacular (GitHub: vojtajina / testacular, License: MIT, npm: testacular) to write better tests for AngularJS, Google’s client-side library that’s rapidly gaining support from the wider web development community. While established projects like Selenium ar
DailyJS: ES6 for Node
In Harmony of Dreams Come True, Brendan Eich discusses the “new-in-ES6 stuff” that is starting to come to fruition. Although his discussion mostly focuses on Mozilla-based implementations, he does relate upcoming language features to a wide range of JavaScript projects, including games. This is relevant to Node developers because ECMAScript 6 is happening, and changes are already present in V8 its
DailyJS: JSON Extensions
JSON is typically used as a data interchange format. We use it for communicating with services over HTTP, and for configuration files. People are starting to take it beyond Douglas Crockford’s original definition to add more features. Let’s take a look at some of these extensions to JSON. JSON Schema JSON Schema is a JSON-based format for defining the structure of JSON data. Although the JSON Sche
DailyJS: Getting Started with the Chai Assertion Library
Jake Luer is a Node developer and consultant focused on helping to shape the next-generation of mobile and web applications. He is logicalparadox on GitHub and @jakeluer on Twitter. Chai (GitHub: logicalparadox / chai, npm: chai, License: MIT) is a BDD / TDD assertion library for Node and the browser that can be delightfully paired with any JavaScript testing framework. Chai aims to be an expressi
DailyJS: JavaScript Developer Survey 2011 Results
The results are in! Thanks to everyone who took part, your answers are now the property of the community. The raw result set is here: JavaScript Developer Survey 2011, Data. A summary of the results generated by Google Docs can be downloaded here: JavaScript Developer Survey 2011, PDF. I got the feeling that client-side developers felt a little underrepresented by the survey, so in future I can r
DailyJS: Testing with Mocha
Mocha (GitHub: visionmedia / mocha, npm: mocha, License: MIT) by TJ Holowaychuk is a new test library that does just about everything a JavaScript developer needs, and yet remains customisable enough to support both behaviour-driven and test-driven development styles. Mocha presents itself as an unassuming and lightweight library, but it actually goes far beyond the test frameworks I’m familiar wi
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
DailyJS: The How and Why of AMD