2013.05.17, Version 0.10.7 (Stable)

• uv: upgrade to v0.10.7

• npm: Upgrade to 1.2.21

• crypto: Don't ignore verify encoding argument (isaacs)

• buffer, crypto: fix default encoding regression (Ben Noordhuis)

• timers: fix setInterval() assert (Ben Noordhuis)

Source Code: http://nodejs.org/dist/v0.10.7/node-v0.10.7.tar.gz

Macintosh Installer (Universal): http://nodejs.org/dist/v0.10.7/node-v0.10.7.pkg

Windows Installer: http://nodejs.org/dist/v0.10.7/node-v0.10.7-x86.msi

Windows x64 Installer: http://nodejs.org/dist/v0.10.7/x64/node-v0.10.7-x64.msi

Windows x64 Files: http://nodejs.org/dist/v0.10.7/x64/

Linux 32-bit Binary: http://nodejs.org/dist/v0.10.7/node-v0.10.7-linux-x86.tar.gz

Linux 64-bit Binary: http://nodejs.org/dist/v0.10.7/node-v0.10.7-linux-x64.tar.gz

Solaris 32-bit Binary: http://nodejs.org/dist/v0.10.7/node-v0.10.7-sunos-x86.tar.gz

Solaris 64-bit Binary: http://nodejs.org/dist/v0.10.7/node-v0.10.7-sunos-x64.tar.gz

Other release files: http://nodejs.org/dist/v0.10.7/

Website: http://nodejs.org/docs/v0.10.7/

Documentation: http://nodejs.org/docs/v0.10.7/api/

Shasums:

95d64001ccd5a17c2c25f1ae4b0358b6131e7cb8  node-v0.10.7-darwin-x64.tar.gz
c34f991cc0752679002f763b2b3c8927babb08d8  node-v0.10.7-darwin-x86.tar.gz
673c287bcf671eced6aa94637b7c91e5149f4c56  node-v0.10.7-linux-x64.tar.gz
9f14d4f9add721148f0c15f093d3e6b1fa3820c9  node-v0.10.7-linux-x86.tar.gz
1fb7dc4195a9dd228039f5f7ca2cb9f7c35b105a  node-v0.10.7-sunos-x64.tar.gz
d84cd8afb50df44483b9dab0c65d5c81f07ac4a2  node-v0.10.7-sunos-x86.tar.gz
d7794a7da103d639fdec4b9e7236a5a0a4330297  node-v0.10.7-x86.msi
0524ad9268095c9ed435708268e6aad7968309f7  node-v0.10.7.pkg
f2bde505faf6ffed3084c8e550a9e6d4311f13d5  node-v0.10.7.tar.gz
5f50384766dd5435dba4989d95032452754150bf  node.exe
809f12f84c8495d101ce6ae443890e8533695ab0  node.exp
5a7355e2f75ae3f72deab75f4c9f93e4e5325584  node.lib
6e45953bd7488a4236c43fea93b05da0854158a7  node.pdb
fc5e3b2b1c74e53f1d214a9e2d5af30fe5247381  x64/node-v0.10.7-x64.msi
aa67bbd421f26b37fa09ce30d5e626106677853e  x64/node.exe
b289989a156d4d7055554962e6f00ba3e380aeea  x64/node.exp
0dbecc5007c9e28ad488d2058157f8360eaed958  x64/node.lib
e4b63472787a3db6a3d85237e8c7fb4d973f797b  x64/node.pdb

Node core has one creator, one dictator, and a short list of committers. I am not the creator, the dictator, or on the committer list.

I'm the dictator of several tiny GitHub projects and a conference. I'm the CTO of a company with a small but amazing engineering team.

I make decisions, I have opinions, and I agree and disagree with many people about many things in public.

People listen to me because I've gained some amount of credibility with them over time. Other people don't listen to me and probably for similar if opposing reasons.

People who write node listen to me more than people who don't. I was around in the earliest days of the platform and have written node nearly every day since. Since node is fairly young experience is a scarce resource but every year that resource grows and people who were there early matter less.

I don't make decisions for people. Substack doesn't make decisions for people. Isaac doesn't make decisions for people, except in core. We all write code, we state our opinions, and people choose which to listen to. Isaac, Substack and I almost never all agree about any one thing.

There is no "node leadership" in the larger community in that there is nobody with the authority or even the credibility to end, remove or push out another project or person. There's no illuminati, no committee, and the effect of decisions made by core, which is a dictatorship, are nearly over.

And yet, people sometimes claim that the "node leadership" are stifling their ideas.

Several people are influencers in the node community. People are influenced by them because they have built up a fair amount of credibility for their ideas and solutions. Nearly all of those influencers disagree with underscore and async, the two most depended on libraries in the node ecosystem, which gives some insight in to the ability of so called leadership to stifle ideas or projects.

All of these influencers, especially me, are often wrong. I was very dismissive of underscore and async, which I now use regularly.

No matter what your idea is you will get no more than 50% of the node influencers to agree with it so it's best not to even try. The success of your idea does not hang on me, or Substack, or Isaac endorsing or using it. Most of what the influencers actually produce is dismissed by nearly all other influencers. We sometimes don't even agree that we all like node.js.

I wrote a post that encouraged people with certain ideas to pursue them outside of node's walls not because I disagree with those ideas but because I truly believe they will be more successful that way. Before coming to node I spent time in Python's alternate concurrency systems (Twisted, asyncore, stackless) and the reason why node has succeeded where they failed has a lot to do with node not trying to make an existing community happy and creating a new one instead.

One day someone will write something much better than node and I'll use it, but I don't believe that will happen inside of node's ecosystem because I've never seen it happen before. Grand new projects succeed when they build new communities not seek the approval of people already invested in something else.

If it makes me a negative person to suggest that people will have more success following the path of successful projects than failed ones then I guess I'm an asshole.

It is unlikely that I will stop having opinions, and expressing them, nor will other people in the fictitious "node leadership" but your success and the acceptance of your ideas isn't dependent on our approval and any great idea we didn't already think of we're likely to dismiss out of ignorance, arrogance, or both, so it's best to just ignore what we think and have fun building software.

No idea is served well by complaining about the opinions of people who disagree with it and nobody is going to be convinced your detractors are wrong by complaining about them saying it instead of refuting their ideas with your own.

L'équipe de l'association GRANIT propose une conférence, le 28 Mai prochain au Musée des Transmissions à Cesson Sévigné à partir de 17h : Le Cloud près de chez vous. Nous y présenterons des solutions de Cloud Computing et de DataCenter.

PROGRAMME de la Vespérale Cloud Computing

Au cours de cette soirée les thèmes suivants seront présentés :

• Papa Abdoulaye N’DIAYE, Responsable produit de la ligne de produit DataCenter TDF présentera : Les Datacenters de proximité et réseaux très haut débit en région, pour que vos entreprises restent connectées et proches de leurs clients,
• Samuel Liard, Consultant Apptom Mobile & Cloud présentera : Le Cloud Computing dans la vraie vie ou comment votre entreprise peut profiter du Cloud concrètement,
• Vincent Rabah, Responsable Technique Cloud Computing chez IPSIS présentera : B2GaaS dans le Cloud Orange Business Service, une offre cuisinée au beurre, pour l'international.

Pour rappel : les Vespérales sont GRATUITES pour les adhérents de GRANIT, 20 euros pour les non-adhérents.

Après la conférence, nous vous invitons à prendre un apéritif de l'amitié pour pouvoir échanger

Ceux qui le souhaitent peuvent également se joindre à nous pour dîner à la Brasserie "Chez Edgar" à Cesson (20 euros le repas)

Lien d'inscription pour la Vespérale

Lien d'inscription pour le repas

In our April 30th blog post, Nodejitsu announced price increases for customers running on Individual Plans on our hosting platform. You can find the new numbers and details of additional platform changes here. This post is a reminder that these changes are taking place, and a response to a few questions from our customers.

Initially we gave two weeks notice, and scheduled price changes for Wednesday May 15th. Many customers have felt this was not enough time. My team and I heard your feedback, and have pushed the changes out one more week. Wednesday May 22nd is now the day that our new prices will go into effect.

We also received questions regarding the ascending price of our plans. For example, some people have wondered why a Micro plan (1 drone) costs $9 whereas a Small plan (3 drones) costs $33 dollars. This is because our Micro plans (our lowest hosting tier), are being slightly subsidized. We want to continue encouraging experimentation on our PaaS, albeit at a higher price point than before.

In the same spirit of experimentation, Nodejitsu is upholding our commitment to offer a free drone, the equivalent of one Micro plan, to host an open source app to any node.js developer. You simply need to apply through opensource.jit.su.

Nodejitsu's success thus far is due entirely to the support of the node.js community. We understand these price changes have upset some of our customers, but these changes allow us to serve our community sustainably and continue contributing open source software to the node ecosystem. These changes also provide our small but talented team with an opportunity to improve our PaaS, dealing more quickly with production incidents and fixing underlying issues. The goal is to provide our customers with a better product. My team and I are excited to move forward towards a strong future for node, and we look forward to doing so with many members of the node community on our platform.

Aradan 4 gun gecti, Reyhanli ile ilgili hicbir bilgi akisi yok. Yayin yasagini sadece bir kucuk muhalif televizyon kanali kirip halki konusturuyor, onlar da, halkin tamamen galeyana nasil geldigini gosteriyorlar.

Hayatla ilgi ve alakamiz bu kadar; kim nerede galeyana geliyor, kac kisi oluyor ve kac bina yikiliyor.

Bu insanlar hastaneye nasil gider, giderlerse sigortalari var mi, paralari var mi, o kadar evi yikilan insanin battaniyesi, cadiri var mi, ogrencilerin memleketlerine donebilecek harcliklari var mi, hicbir yerde, tek satir dahi bilgi yok.

Reyhanli halkina “nasilsiniz?” diyen dahi yok gozlemledigim kadariyla. Bahsettigim o tek videonun cekilis amaci da, ortasinda bir yerde gosterdikleri bir derginin reklami. Dergiyi gosterip konusma yapan adam tam bir ajan stereotipi.

Tam bir toplumsal pejmurdelik hali icindeyiz. Iletisim araclarina en ihtiyac duydugumuz zaman. Basit bir uygulama dahi oradaki insanlarin veya orayla iletisim kurmaya calisanlarin ihtiyaclarini karsilayabilir.

O kadar insanlarin arasindaki baglari guclendirdigini soyleyen Turkcell’in, diger GSM operatorlerinin, ve diger teknoloji sirketlerinin hic mi aklina birsey organize etmek gelmez?

Eksi Sozluk’un bir baslik acip, Reyhanli ve cevresinden gelen herkese yazma izni vermesi zor birsey midir?

Bir ulus bir felaket aninda ancak bu kadar duyarsizlasabilir.

Velakin sasirdim desem de yalan olur. Hayatla az bucuk baglanti kurmaya calisan herhangi birinin coktandir gozlemledigi sorunlarin iyice ayyuka cikisidir bu durum.

50 yil once bir sair soyle bir laf ediyor; “Biz sehirlere sanki medenilesmek icin degil birbirimizi bogazlamak icin geliyoruz.”

Durumu en iyi aciklayan sey budur. Bir turlu medenilesemedigimiz icin dogru duzgun iletisim araclarimiz yok. Insanlar koca bir felaketin ardindan yapayalniz birakilmis, ve kucuk bir caba dahi sarfetmiyoruz.

Bir suru Facebook ve Twitter klonumuz, e-ticaret ve arkadaslik sitelerimiz, “hot” deyince tek sira halinde dizilip bir kucuk cesaret ornegi dahi gosteremeyen onlarca online haber sitemiz var.

Kendini yeni medyanin oncusu sayan Dipnot TV’de bile Reyhanli’nin haberini gecelim, bir foto galerisi dahi yok.

Hani artik muhabire ihtiyac yoktu? Hani artik interneti olan herkes haber muhabiriydi?

Derhal medeniyetlesmeden, yazilim gelistirmekten, ve sosyal medyadan ne anladigimizi gozden gecirmeliyiz.

Artik ister startup’inizla dunya rekorlari kirin, ister Mars’a uzay mekigi gonderin. Sayet akli basinda torunlarimiz olursa bugunu yazip cizen, bu duyarsiz, pejmurdelikten baska birsey olmayan toplumsal halimizi bizim bugun gordugumuz travmatik, blur haliyle degil tam oldugu gibi, en gercek haliyle gorecekler ve yazacaklar.

Dunya dondugu surece gercegi saklayamaya calisanlar, kendilerine boyun egen ve canak tutanlarla beraber, er veya gec lanetlenir.

Bugun yazilim yapanlara dusen gorev ise medeniyetin onune cikan problemler icin cozum uretmektir. Bir ipin ucundan tutmanin vakti geldi.

Tum bu karamsar tablo hakkindaki fikirlerimizi ortaya koymamiz ve ne yapabilecegimiz hakkinda kolektif bir kulturle sonuca ulastigimiz tartismalar uretmemiz gerekiyor. Yazilimci olarak elimizden ne gelir, ne gibi problemleri nasil cozeriz, en azindan herkesin katilabildigi yazismalar yapabiliriz bu konuda.

Su an kisisel olarak attigim adim Ana Kaynak projesinin bir sonraki surumunu gelistirmeye baslamak oldu. Bunun hakkinda bilgi almak isterseniz bana ulasin. Kisaca ozetlemek gerekirse, Ana Kaynak Reyhanli veya herhangi bir diger konu basliginda gercek zamanli bilgi akisi saglayan portallari bir araya getiren platform olmayi hedefliyor.

Isaac Schlueter talk on Node roadmap to reach Node.js 1.0. A lot of great stuff will come! So dive into that huge video!

2013.05.14, Version 0.10.6 (Stable)

• module: Deprecate require.extensions (isaacs)

• stream: make Readable.wrap support objectMode, empty streams (Daniel Moore)

• child_process: fix handle delivery (Ben Noordhuis)

• crypto: Fix performance regression (isaacs)

• src: DRY string encoding/decoding (isaacs)

Source Code: http://nodejs.org/dist/v0.10.6/node-v0.10.6.tar.gz

Macintosh Installer (Universal): http://nodejs.org/dist/v0.10.6/node-v0.10.6.pkg

Windows Installer: http://nodejs.org/dist/v0.10.6/node-v0.10.6-x86.msi

Windows x64 Installer: http://nodejs.org/dist/v0.10.6/x64/node-v0.10.6-x64.msi

Windows x64 Files: http://nodejs.org/dist/v0.10.6/x64/

Linux 32-bit Binary: http://nodejs.org/dist/v0.10.6/node-v0.10.6-linux-x86.tar.gz

Linux 64-bit Binary: http://nodejs.org/dist/v0.10.6/node-v0.10.6-linux-x64.tar.gz

Solaris 32-bit Binary: http://nodejs.org/dist/v0.10.6/node-v0.10.6-sunos-x86.tar.gz

Solaris 64-bit Binary: http://nodejs.org/dist/v0.10.6/node-v0.10.6-sunos-x64.tar.gz

Other release files: http://nodejs.org/dist/v0.10.6/

Website: http://nodejs.org/docs/v0.10.6/

Documentation: http://nodejs.org/docs/v0.10.6/api/

Shasums:

24982edc3b6aafd019273fa5e8a2031353314b56  node-v0.10.6-darwin-x64.tar.gz
e208c5dc83864a7f35f9df60ee35642bc7dd689c  node-v0.10.6-darwin-x86.tar.gz
ab2ad473f5aa0f1c5adb50b9ea47fd05010bca2c  node-v0.10.6-linux-x64.tar.gz
29cdac417449f088e6e6fa67d57c9205d8bff6c5  node-v0.10.6-linux-x86.tar.gz
66e3a9e53af6d8f27c690a77c329a2bd108965ac  node-v0.10.6-sunos-x64.tar.gz
05bda089f4f702deddb8e593653676ede5f0e10b  node-v0.10.6-sunos-x86.tar.gz
6ceb80be28c63f2c57e8479755d206400b205c46  node-v0.10.6-x86.msi
cd0acf9b332c30aba6a72979d3373e342fad6b95  node-v0.10.6.pkg
fa06101af8890eeaf997bd2620d7742b71a7223c  node-v0.10.6.tar.gz
a2a2befa62b3cd2da9c2e51204df017e0f0c0cae  node.exe
8401647a2f8fb3486fa08d7e603822ae12cf6dee  node.exp
8ab923eb23584310874a4f63d71244cca5bfc0f8  node.lib
b9042fec324b202853f7f1d8b1d26ea49d944913  node.pdb
647a2ea899113e14d8f0894aa969ffd3a5d407c6  x64/node-v0.10.6-x64.msi
021048aa29fce5ce200b22896fd5f1b053f0d40c  x64/node.exe
adbdc6112b3172c259a3fa9e07b7d456a0c65beb  x64/node.exp
226af9033a41c96c68ade96cecedcf1289414424  x64/node.lib
cca201bfe38713ffde4a0cad70cb3a5325097257  x64/node.pdb

2013.05.13, Version 0.11.2 (Unstable)

• uv: Upgrade to 0.11.2

• V8: Upgrade to 3.19.0

• npm: Upgrade to 1.2.21

• build: Makefile should respect configure --prefix (Timothy J Fontaine)

• cluster: use round-robin load balancing (Ben Noordhuis)

• debugger, cluster: each worker has new debug port (Miroslav Bajtoš)

• debugger: restart with custom debug port (Miroslav Bajtoš)

• debugger: breakpoints in scripts not loaded yet (Miroslav Bajtoš)

• event: EventEmitter#setMaxListeners() returns this (Sam Roberts)

• events: add EventEmitter.defaultMaxListeners (Ben Noordhuis)

• install: Support $(PREFIX) install target directory prefix (Olof Johansson)

• os: Include netmask in os.networkInterfaces() (Ben Kelly)

• path: add path.isAbsolute(path) (Ryan Doenges)

• stream: Guarantee ordering of 'finish' event (isaacs)

• streams: introduce .cork/.uncork/._writev (Fedor Indutny)

• vm: add support for timeout argument (Andrew Paprocki)

Source Code: http://nodejs.org/dist/v0.11.2/node-v0.11.2.tar.gz

Macintosh Installer (Universal): http://nodejs.org/dist/v0.11.2/node-v0.11.2.pkg

Windows Installer: http://nodejs.org/dist/v0.11.2/node-v0.11.2-x86.msi

Windows x64 Installer: http://nodejs.org/dist/v0.11.2/x64/node-v0.11.2-x64.msi

Windows x64 Files: http://nodejs.org/dist/v0.11.2/x64/

Linux 32-bit Binary: http://nodejs.org/dist/v0.11.2/node-v0.11.2-linux-x86.tar.gz

Linux 64-bit Binary: http://nodejs.org/dist/v0.11.2/node-v0.11.2-linux-x64.tar.gz

Solaris 32-bit Binary: http://nodejs.org/dist/v0.11.2/node-v0.11.2-sunos-x86.tar.gz

Solaris 64-bit Binary: http://nodejs.org/dist/v0.11.2/node-v0.11.2-sunos-x64.tar.gz

Other release files: http://nodejs.org/dist/v0.11.2/

Website: http://nodejs.org/docs/v0.11.2/

Documentation: http://nodejs.org/docs/v0.11.2/api/

Shasums:

ddc85fd6ed70057c64d7c9cd64bb94f28596d163  node-v0.11.2-darwin-x64.tar.gz
9893a3a3598d2e5ed24bfee8642b72c37808dbae  node-v0.11.2-darwin-x86.tar.gz
f81189c30aa268f2b43572e1795fedd50f3495c3  node-v0.11.2-linux-x64.tar.gz
6322bf3be78f907a3b5e06f38af1b33c52957612  node-v0.11.2-linux-x86.tar.gz
3becca01532e104081ca51a265f07e77b6e9e25f  node-v0.11.2-sunos-x64.tar.gz
9489238384edb456d9a603e5bef1128dfafe69b1  node-v0.11.2-sunos-x86.tar.gz
76421e22cff4d4f4d1cb2ce3e3566e2c9004cdee  node-v0.11.2-x86.msi
a23d607f7b433197533cd6d88c981c75463efff8  node-v0.11.2.pkg
1d1080598431062ccb4bbbf7ecbb7596fe664c67  node-v0.11.2.tar.gz
b45a04167d32887c32a2479c4567af394627c8ad  node.exe
c65ce6e073e173ae5769fe4dd9ff83f2f56ce05d  node.exp
31f569697cb8447492e3172e614c3c4cfff81d09  node.lib
c98f8a717ef9d660ff3d45e86e2ee396ca02e721  node.pdb
7caabd3a774c96a8126f10d2e184727bd5160526  x64/node-v0.11.2-x64.msi
3b049227e3c392fdb88de9a5da7ad1ec14c82d17  x64/node.exe
c95f9746e180c064a5225ab83cca604bf918e59a  x64/node.exp
78c94386c312ded2f7cb0c84951535b67e36fecf  x64/node.lib
ad774b472a3cfa03374aac2d1dac19f9599ad2f8  x64/node.pdb

§ Froont — an interesting approach to responsive Web design.

§ CAP has a FAQ:

16. Have I ‘got around’ or ‘beaten’ the CAP theorem?

§ Interesting study of small vs large, open vs closed source projects:

In other words, if you’re looking for bug-free apps, look for a small open source project or a large proprietary piece of software, because those have the best chance of having few defects and high overall code quality.

§ IntegrationContractTest.

§ Track Server-Side Events from Rails in Google Analytics.

§ Dale Emery:

Costs move to where they will not be borne by the people who made the decisions that created them.

§ Coding, Fast and Slow: Developers and the Psychology of Overconfidence:

But here’s where it gets interesting. Every programmer who’s been working in the real world for more than a few months has run into the problems I’m describing above.

And yet… we keep on making these just spectacularly bad estimates.

§ Using checklists for code review:

One of the ways that I avoid the pitfall of giving superficial reviews is with checklists. I have a bunch of different sets of checklists that I’ve developed and tweaked over the past few years, and for any given change, I’ll select the sections which apply.

§ VimSpeak lets you control Vim with your voice using speech recognition, so you can say “select three words” to type v3w or “change surrounding brackets to parens” to type cs.

§ The GitHub JavaScript styleguide:

• Write new JS in CoffeeScript.
• Use soft-tabs with a two space indent.
• Always use camelCase, never underscores.
• Use implicit parentheses when possible.
• …

§ Case study: How effective are CDNs for mobile visitors?.

§ The Onion is a GitHubber.

§ Ode to a shipping label.