Presenter:
@othiym23
github.com/othiym23
Friedel Ziegelmayer dignifiedquire
jmervine
/ beyond_mean.md
Last active
December 30, 2015 09:59
jedi4ever
/ nodejs-cluster-zero-downtime.md
Last active
February 11, 2024 13:45
nodejs clustering, zero downtime deployment solutions
The trick? pass the file descriptor from a parent process and have the server.listen reuse that descriptor. So multiprocess in their own memory space (but with ENV shared usually)
It does not balance, it leaves it to the kernel.
In the last nodejs > 0.8 there is a cluster module (functional although marked experimental)
- http://nodejs.org/api/cluster.html
- Simple cluster example:
UPDATE working on this here!
so… I've had this weird idea recently...
In git (and in other secure + distributed systems) you have a tree of hashes where each object is identified by it's hash and objects contain pointers to other objects. They just have the hash of other objects stored inside them.
jonschlinkert
/ markdown-cheatsheet.md
Last active
April 11, 2024 04:45
A better markdown cheatsheet.
(Also see [remarkable][], the markdown parser created by the author of this cheatsheet)
dypsilon
/ frontendDevlopmentBookmarks.md
Last active
May 7, 2024 01:27
A badass list of frontend development resources I collected over time.
Attention: the list was moved to
https://github.com/dypsilon/frontend-dev-bookmarks
This page is not maintained anymore, please update your bookmarks.
While the Codio Client has a simple inheritance system in the form of the core/context plugin, it leaves a little to be desired and is lacking in a few areas that I feel would greatly improve the readability of our code base, as well as providing a little extra functionality.
Javascript has no such thing as Classes, but it has several different ways to fake them. We need a clean and concise way to define and use classes, with the ability for constructors, inheritance and access to overridden methods.
John Resig posted an article a long time ago with his solution for Classes in Javascript. It's simple, but powerful, and is extremely readable, so it will form the basis of this proposal.
Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.
Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.
LindseyB
/ nodejs_resource.markdown
Last active
April 21, 2021 17:03
Node.js is just JavaScript running on the server side. That's it. That's all there is to it.
- Express Docs, if you want to get started and already know JavaScript this is the place to be
domenic
/ interop.md
Last active
July 7, 2022 19:47
`module.exports =` and ES6 Module Interop in Node.js
The question: how can we use ES6 modules in Node.js, where modules-as-functions is very common? That is, given a future in which V8 supports ES6 modules:
- How can authors of function-modules convert to ES6
exportsyntax, without breaking consumers that dorequire("function-module")()? - How can consumers of function-modules use ES6
importsyntax, while not demanding that the module author rewrites his code to ES6export?
@wycats showed me a solution. It involves hooking into the loader API to do some rewriting, and using a distinguished name for the single export.
This is me eating crow for lots of false statements I've made all over Twitter today. Here it goes.
