サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
買ってよかったもの
www.devthought.com
I’m writing this blog post to explain why I no longer consider assertion testing through projects like should.js, expect.js or chai ideal. For the uninitiated, these modules allow you to write assertions in a very clear english-like way: // my test file expect(number).to.be.below(5); someAssertion().should.be.ok; But the most attractive quality is that they provide helper functions to make a lot o
tl;DR: only 2/3 bugs have an impact, one has a trivial workaround (jQuery snippet included below), the other one is UX related. Socket.IO needs no updates. In the past 48 hours a lot has been written about the introduction of iOS6. With such a major software release it’s not surprise that a few issues have been introduced. Of particular importance to us web developers, three different bugs have be
On Monday I had the pleasure of speaking once again at NodeConf in Portland. On this glorious second edition, several talks were dedicated to the topic of realtime, covering angles such as its inception and future, scalability, backend messaging and more. Mikeal requested that I talk about the state of Socket.IO, now one of the corner stones of the so-called realtime web and one of the most popula
TextboxList turns normal textboxes into a widget which can be navigated with the keyboard, effectively turning your input into a “list” of items that can be easily deleted. It comes with an Autocomplete plugin. Demo Click here to see it in action. License You can use and modify TextboxList freely for any non-commercial use. Otherwise you need to purchase a one-time per-domain license of $20, by cl
As a conference curator and fellow argentinian, and due to the lack of any reports in English, I thought I’d share a brief summary of a very unfortunate occurrence: Richard Stallman, father of the FSF, was robbed of his bag containing his laptop, medicine, money and passport after his talk at the University of Buenos Aires on Friday, June 8. Despite his controversial views on a variety of topics,
I just created a module named console-trace that does one very simple yet very useful thing: prepend the line number and filename to console calls. To leverage it you just need to require('console-trace') and prepend a flag: console.trace.error('Test'); console.t.log('Test'); // shorthand You can learn about a few other options in the GitHub repository.
With the announcement of SPDY support by Twitter, I thought it would be cool to visualize how this extends to the rest of the web as I browse it. I developed a Chrome extension you can install to visualize SPDY support in your address bar. Source on Github. Install Chrome Extension For those who haven’t heard of SPDY, it’s a new protocol being developed by Google to transport the existing HTTP pro
I decided to put together a little list of tips and tricks related to NPM you might not know about, that come from my experience working with it daily, in both production and development. Dev dependencies Make sure packages that only need to be installed while developing your module, like test frameworks, are included as devDependencies: "devDependencies": { "module": "0.1.0" } Introspecting packa
With Express 3.0 the view functionality is slimming down even further. Today res.render not only integrates with template engines but also introduces the concept of layouts. The layout option and functionality is being removed in favor of more flexible alternatives that template engines can offer without Express solving it for them. Jade saw the introduction of the extends and block citizens. A te
Daniel Kang recently made public a partial implementation of the Node.JS API in C++11 (also known as C++0x) named node.native. #include <iostream> #include "http.h" using namespace native::http; int main() { http server; if(server.listen("0.0.0.0", 8080, [](request& req, response& res){ res.set_status(200); res.set_header("Content-Type", "text/plain"); res.end("C++ FTW\n"); })) std::cout << "Serve
To many beginner Node.JS users, a fundamental and immediate apparent disadvantage of writing their web applications with Node.JS lies in the inability to save a file, refresh the browser and see their changes live. This “problem” is rooted of course in significantly different architectures. In the case of, for example, PHP applications we traditionally separate the role of the web server and reque
Following my article A String is not an Error, I want to bring attention to an issue that similarly applies to JavaScript in general, but has special relevance in the Node.JS environment. The problem boils down to the usage of {} as a data-structure where the keys are supplied by untrusted user input, and the mechanisms that are normally used to assert whether a key exists. Consider the example of
I decided to write a little article to discourage an unfortunately common pattern in Node.JS modules (and browser JavaScript, to a lesser extent) that can boil down to these two examples: // A: function myFunction () { if (somethingWrong) { throw 'This is my error' } return allGood; } and // B: async Node.JS-style callback with signature `fn(err, …)` function myFunction (callback) { doSomethingAsy
Update: the code that empowers this menu has been upgraded to the latest MooTools version, and even improved! Now works with vertical, horizontal menus, with more flexible morphing! Let me introduce you to Fancy Menu: Home Plant a tree Travel Ride an elephant When it comes to creating the navigation part of your Website, the first thing you might think of is an unordered list that you style
このページを最初にブックマークしてみませんか?
『Guillermo Rauch's Devthought』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く