ES6 module loading: More complicated than you think - NCZOnline
One of the most long-awaited features of ECMAScript 6 is the formal definition of modules as part of the language. For years, JavaScript developers have struggled with organizing their code and needing to decide between alternate ad-hoc module formats like RequireJS, AMD, and CommonJS. Formally defining modules as part of JavaScript will eliminate a lot of heartache in the future, but right now, t
Node.js and the new web front-end - Human Who Codes
Posted at October 7, 2013 by Nicholas C. Zakas Tags: Architecture, JavaScript, Node.js, Web Server Front-end engineers have a rather long and complicated history in software engineering. For the longest time, that stuff you sent to the browser was “easy enough” that anyone could do it and there was no real need for specialization. Many claimed that so-called web developers were nothing more than g
Are your mixins ECMAScript 5 compatible? - Human Who Codes
Posted at December 11, 2012 by Nicholas C. Zakas Tags: ECMAScript 5, JavaScript I was working with a client recently on a project that could make full use of ECMAScript 5 when I came across an interesting problem. The issue stemmed from the use of mixins, a very common pattern in JavaScript where one object is assigned properties (including methods) from another. Most mixin functions look somethin
Computer science in JavaScript: Quicksort - Human Who Codes
Posted at November 27, 2012 by Nicholas C. Zakas Tags: Algorithms, Computer Science, JavaScript, Sorting Most discussions about sorting algorithms tend to end up discussing quicksort because of its speed. Formal computer science programs also tend to cover quicksort1 last because of its excellent average complexity of O(n log n) and relative performance improvement over other, less efficient sorti
ECMAScript 6 collections, Part 3: WeakMaps - Human Who Codes
Posted at November 6, 2012 by Nicholas C. Zakas Tags: ECMAScript 6, JavaScript, WeakMap Weakmaps are similar to regular maps in that they map a value to a unique key. That key can later be used to retrieve the value it identifies. Weakmaps are different because the key must be an object and cannot be a primitive value. This may seem like a strange constraint but it’s actually the core of what make
JavaScript APIs you've never heard of (and some you have) - Human Who Codes
Posted at November 13, 2012 by Nicholas C. Zakas Tags: Ajax, API, CSS, DOM, JavaScript This week I was scheduled to give a brand new talk at YUIConf entitled, JavaScript APIs you’ve never heard of (and some you have). Unfortunately, a scheduling conflict means that I won’t be able to attend. So instead of letting the work of putting together a brand-= new talk go to waste (or otherwise be delayed)
Now available: Maintainable JavaScript - Human Who Codes
I’m happy to announce that my latest book, Maintainable JavaScript, is now available in print. Thanks to the folks at O’Reilly, the ebook was released as a preview last month, but now all the edits have been completed and the book is officially done. I’m very excited about this book, even moreso than some of the others, because it’s quite different than any I’ve written before. One of the reasons
Working with files in JavaScript, Part 3: Progress events and errors - Human Who Codes
The FileReader object is used to read data from files that are made accessible through the browser. In my previous post, you learned how to use a FileReader object to easily read data from a file in a variety of formats. The FileReader is very similar to XMLHttpRequest in many ways. Progress events Progress events are becoming so common that they’re actually written up in a separate specification1
Working with files in JavaScript, Part 1: The Basics - Human Who Codes
Many years ago, I was asked during a job interview at Google what changes I would make to the web in order to provide better experiences. At the top of my list was having some way to work with files other than the <input type="file"> control. Even as the rest of the web was evolving, the way we dealt with files never changed since it was first introduced. Thankfully, with HTML5 and related APIs, w
JavaScript stack overflow error - Human Who Codes
Posted at May 19, 2009 by Nicholas C. Zakas Tags: JavaScript, Overflow, Performance, Recursion, Stack From time to time, I’ve blogged about JavaScript browser limits and how they present themselves. I started out by discussing the long-running script dialog and then moved on to other performance issues. I thought I had covered most of the annoying and ill-explained JavaScript limits, but this past
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Working with files in JavaScript, Part 2: FileReader - Human Who Codes
Working with files in JavaScript, Part 4: Object URLs - Human Who Codes