While we still want to keep decentralized 'come and code together'
approach it would be helpful to share some topics of interests in
advance. Feel free to post here your ideas, from 20minutes
presentation with projector and mic to small particular piece of code
to discuss with other.
My potential topics:
(one of first two could be a 10-20 min talk):
1) X Server in the browser. Node.js serverside birdge X11 <->
socket.io, client-side XServer logic
2) Implementing network protocol servers and clients (existing or
your own protocols) in node.js. Short overview for existing protocols
(mysql, fastcgi, x11, memcached, rfb, http, spdy) - what makes good
protocol good, overview of existing un-framing and deserealiser
libraries (Buffers.read*, bufferlists etc), ...
3) using node profiler
4) parsing JS source with uglifyjs
5) D-BUS native client library in node
6) PHP->javascript compiler
7) benchmarking node.js projects (why ab is not enough)
My vote is to keep presentations at 10 minutes or less. I like the lightning talk format, in fact.
Andrey, I'd be really interested in hearing about the node profiler or benchmarking - options 3) and 4).
For my part, I might give a quick overview on either drafts (https://github.com/nicholasf/drafts.js) or creating a SSO server using express.js, everyauth, and mongo. Or I might do a talk on doing this and using drafts to test it.
On Monday, March 26, 2012 4:26:13 PM UTC+11, Andrey Sidorov wrote:
> Hi all,
> While we still want to keep decentralized 'come and code together' > approach it would be helpful to share some topics of interests in > advance. Feel free to post here your ideas, from 20minutes > presentation with projector and mic to small particular piece of code > to discuss with other.
> My potential topics: > (one of first two could be a 10-20 min talk): > 1) X Server in the browser. Node.js serverside birdge X11 <-> > socket.io, client-side XServer logic > 2) Implementing network protocol servers and clients (existing or > your own protocols) in node.js. Short overview for existing protocols > (mysql, fastcgi, x11, memcached, rfb, http, spdy) - what makes good > protocol good, overview of existing un-framing and deserealiser > libraries (Buffers.read*, bufferlists etc), ...
> 3) using node profiler > 4) parsing JS source with uglifyjs > 5) D-BUS native client library in node > 6) PHP->javascript compiler > 7) benchmarking node.js projects (why ab is not enough)
> Cheers, > Andrey
On Monday, March 26, 2012 4:26:13 PM UTC+11, Andrey Sidorov wrote:
> Hi all,
> While we still want to keep decentralized 'come and code together' > approach it would be helpful to share some topics of interests in > advance. Feel free to post here your ideas, from 20minutes > presentation with projector and mic to small particular piece of code > to discuss with other.
> My potential topics: > (one of first two could be a 10-20 min talk): > 1) X Server in the browser. Node.js serverside birdge X11 <-> > socket.io, client-side XServer logic > 2) Implementing network protocol servers and clients (existing or > your own protocols) in node.js. Short overview for existing protocols > (mysql, fastcgi, x11, memcached, rfb, http, spdy) - what makes good > protocol good, overview of existing un-framing and deserealiser > libraries (Buffers.read*, bufferlists etc), ...
> 3) using node profiler > 4) parsing JS source with uglifyjs > 5) D-BUS native client library in node > 6) PHP->javascript compiler > 7) benchmarking node.js projects (why ab is not enough)
> Cheers, > Andrey
On Monday, March 26, 2012 4:26:13 PM UTC+11, Andrey Sidorov wrote:
> Hi all,
> While we still want to keep decentralized 'come and code together' > approach it would be helpful to share some topics of interests in > advance. Feel free to post here your ideas, from 20minutes > presentation with projector and mic to small particular piece of code > to discuss with other.
> My potential topics: > (one of first two could be a 10-20 min talk): > 1) X Server in the browser. Node.js serverside birdge X11 <-> > socket.io, client-side XServer logic > 2) Implementing network protocol servers and clients (existing or > your own protocols) in node.js. Short overview for existing protocols > (mysql, fastcgi, x11, memcached, rfb, http, spdy) - what makes good > protocol good, overview of existing un-framing and deserealiser > libraries (Buffers.read*, bufferlists etc), ...
> 3) using node profiler > 4) parsing JS source with uglifyjs > 5) D-BUS native client library in node > 6) PHP->javascript compiler > 7) benchmarking node.js projects (why ab is not enough)
> Cheers, > Andrey
On Monday, March 26, 2012 4:26:13 PM UTC+11, Andrey Sidorov wrote:
> Hi all,
> While we still want to keep decentralized 'come and code together' > approach it would be helpful to share some topics of interests in > advance. Feel free to post here your ideas, from 20minutes > presentation with projector and mic to small particular piece of code > to discuss with other.
> My potential topics: > (one of first two could be a 10-20 min talk): > 1) X Server in the browser. Node.js serverside birdge X11 <-> > socket.io, client-side XServer logic > 2) Implementing network protocol servers and clients (existing or > your own protocols) in node.js. Short overview for existing protocols > (mysql, fastcgi, x11, memcached, rfb, http, spdy) - what makes good > protocol good, overview of existing un-framing and deserealiser > libraries (Buffers.read*, bufferlists etc), ...
> 3) using node profiler > 4) parsing JS source with uglifyjs > 5) D-BUS native client library in node > 6) PHP->javascript compiler > 7) benchmarking node.js projects (why ab is not enough)
> Cheers, > Andrey
On Monday, March 26, 2012 4:26:13 PM UTC+11, Andrey Sidorov wrote:
> Hi all,
> While we still want to keep decentralized 'come and code together' > approach it would be helpful to share some topics of interests in > advance. Feel free to post here your ideas, from 20minutes > presentation with projector and mic to small particular piece of code > to discuss with other.
> My potential topics: > (one of first two could be a 10-20 min talk): > 1) X Server in the browser. Node.js serverside birdge X11 <-> > socket.io, client-side XServer logic > 2) Implementing network protocol servers and clients (existing or > your own protocols) in node.js. Short overview for existing protocols > (mysql, fastcgi, x11, memcached, rfb, http, spdy) - what makes good > protocol good, overview of existing un-framing and deserealiser > libraries (Buffers.read*, bufferlists etc), ...
> 3) using node profiler > 4) parsing JS source with uglifyjs > 5) D-BUS native client library in node > 6) PHP->javascript compiler > 7) benchmarking node.js projects (why ab is not enough)
On Mon, Mar 26, 2012 at 4:51 PM, Nicholas Faiz <nicholas.f...@gmail.com> wrote: > Hey,
> My vote is to keep presentations at 10 minutes or less. I like the lightning > talk format, in fact.
> Andrey, I'd be really interested in hearing about the node profiler or > benchmarking - options 3) and 4).
> For my part, I might give a quick overview on either drafts > (https://github.com/nicholasf/drafts.js) or creating a SSO server using > express.js, everyauth, and mongo. Or I might do a talk on doing this and > using drafts to test it.
> Cheers, > Nick
> On Monday, March 26, 2012 4:26:13 PM UTC+11, Andrey Sidorov wrote:
>> Hi all,
>> While we still want to keep decentralized 'come and code together' >> approach it would be helpful to share some topics of interests in >> advance. Feel free to post here your ideas, from 20minutes >> presentation with projector and mic to small particular piece of code >> to discuss with other.
>> My potential topics: >> (one of first two could be a 10-20 min talk): >> 1) X Server in the browser. Node.js serverside birdge X11 <-> >> socket.io, client-side XServer logic >> 2) Implementing network protocol servers and clients (existing or >> your own protocols) in node.js. Short overview for existing protocols >> (mysql, fastcgi, x11, memcached, rfb, http, spdy) - what makes good >> protocol good, overview of existing un-framing and deserealiser >> libraries (Buffers.read*, bufferlists etc), ...
>> 3) using node profiler >> 4) parsing JS source with uglifyjs >> 5) D-BUS native client library in node >> 6) PHP->javascript compiler >> 7) benchmarking node.js projects (why ab is not enough)
>> Cheers, >> Andrey
> On Monday, March 26, 2012 4:26:13 PM UTC+11, Andrey Sidorov wrote:
>> Hi all,
>> While we still want to keep decentralized 'come and code together' >> approach it would be helpful to share some topics of interests in >> advance. Feel free to post here your ideas, from 20minutes >> presentation with projector and mic to small particular piece of code >> to discuss with other.
>> My potential topics: >> (one of first two could be a 10-20 min talk): >> 1) X Server in the browser. Node.js serverside birdge X11 <-> >> socket.io, client-side XServer logic >> 2) Implementing network protocol servers and clients (existing or >> your own protocols) in node.js. Short overview for existing protocols >> (mysql, fastcgi, x11, memcached, rfb, http, spdy) - what makes good >> protocol good, overview of existing un-framing and deserealiser >> libraries (Buffers.read*, bufferlists etc), ...
>> 3) using node profiler >> 4) parsing JS source with uglifyjs >> 5) D-BUS native client library in node >> 6) PHP->javascript compiler >> 7) benchmarking node.js projects (why ab is not enough)
>> Cheers, >> Andrey
> On Monday, March 26, 2012 4:26:13 PM UTC+11, Andrey Sidorov wrote:
>> Hi all,
>> While we still want to keep decentralized 'come and code together' >> approach it would be helpful to share some topics of interests in >> advance. Feel free to post here your ideas, from 20minutes >> presentation with projector and mic to small particular piece of code >> to discuss with other.
>> My potential topics: >> (one of first two could be a 10-20 min talk): >> 1) X Server in the browser. Node.js serverside birdge X11 <-> >> socket.io, client-side XServer logic >> 2) Implementing network protocol servers and clients (existing or >> your own protocols) in node.js. Short overview for existing protocols >> (mysql, fastcgi, x11, memcached, rfb, http, spdy) - what makes good >> protocol good, overview of existing un-framing and deserealiser >> libraries (Buffers.read*, bufferlists etc), ...
>> 3) using node profiler >> 4) parsing JS source with uglifyjs >> 5) D-BUS native client library in node >> 6) PHP->javascript compiler >> 7) benchmarking node.js projects (why ab is not enough)
>> Cheers, >> Andrey
> On Monday, March 26, 2012 4:26:13 PM UTC+11, Andrey Sidorov wrote:
>> Hi all,
>> While we still want to keep decentralized 'come and code together' >> approach it would be helpful to share some topics of interests in >> advance. Feel free to post here your ideas, from 20minutes >> presentation with projector and mic to small particular piece of code >> to discuss with other.
>> My potential topics: >> (one of first two could be a 10-20 min talk): >> 1) X Server in the browser. Node.js serverside birdge X11 <-> >> socket.io, client-side XServer logic >> 2) Implementing network protocol servers and clients (existing or >> your own protocols) in node.js. Short overview for existing protocols >> (mysql, fastcgi, x11, memcached, rfb, http, spdy) - what makes good >> protocol good, overview of existing un-framing and deserealiser >> libraries (Buffers.read*, bufferlists etc), ...
>> 3) using node profiler >> 4) parsing JS source with uglifyjs >> 5) D-BUS native client library in node >> 6) PHP->javascript compiler >> 7) benchmarking node.js projects (why ab is not enough)
>> Cheers, >> Andrey
> On Monday, March 26, 2012 4:26:13 PM UTC+11, Andrey Sidorov wrote:
>> Hi all,
>> While we still want to keep decentralized 'come and code together' >> approach it would be helpful to share some topics of interests in >> advance. Feel free to post here your ideas, from 20minutes >> presentation with projector and mic to small particular piece of code >> to discuss with other.
>> My potential topics: >> (one of first two could be a 10-20 min talk): >> 1) X Server in the browser. Node.js serverside birdge X11 <-> >> socket.io, client-side XServer logic >> 2) Implementing network protocol servers and clients (existing or >> your own protocols) in node.js. Short overview for existing protocols >> (mysql, fastcgi, x11, memcached, rfb, http, spdy) - what makes good >> protocol good, overview of existing un-framing and deserealiser >> libraries (Buffers.read*, bufferlists etc), ...
>> 3) using node profiler >> 4) parsing JS source with uglifyjs >> 5) D-BUS native client library in node >> 6) PHP->javascript compiler >> 7) benchmarking node.js projects (why ab is not enough)
I haven't been to one of these meets yet, but I'm really looking forward to it. I'd be happy to give a talk about my templating library (https://github.com/deoxxa/node-ginger), binary protocol handling with node-binary, spinning up web services really quickly with mongoskin and express or anything else I've done that's on my github account.
> On Mon, Mar 26, 2012 at 4:51 PM, Nicholas Faiz <nicholas.f...@gmail.com> wrote: >> Hey,
>> My vote is to keep presentations at 10 minutes or less. I like the lightning >> talk format, in fact.
>> Andrey, I'd be really interested in hearing about the node profiler or >> benchmarking - options 3) and 4).
>> For my part, I might give a quick overview on either drafts >> (https://github.com/nicholasf/drafts.js) or creating a SSO server using >> express.js, everyauth, and mongo. Or I might do a talk on doing this and >> using drafts to test it.
>> Cheers, >> Nick
>> On Monday, March 26, 2012 4:26:13 PM UTC+11, Andrey Sidorov wrote:
>>> Hi all,
>>> While we still want to keep decentralized 'come and code together' >>> approach it would be helpful to share some topics of interests in >>> advance. Feel free to post here your ideas, from 20minutes >>> presentation with projector and mic to small particular piece of code >>> to discuss with other.
>>> My potential topics: >>> (one of first two could be a 10-20 min talk): >>> 1) X Server in the browser. Node.js serverside birdge X11 <-> >>> socket.io, client-side XServer logic >>> 2) Implementing network protocol servers and clients (existing or >>> your own protocols) in node.js. Short overview for existing protocols >>> (mysql, fastcgi, x11, memcached, rfb, http, spdy) - what makes good >>> protocol good, overview of existing un-framing and deserealiser >>> libraries (Buffers.read*, bufferlists etc), ...
>>> 3) using node profiler >>> 4) parsing JS source with uglifyjs >>> 5) D-BUS native client library in node >>> 6) PHP->javascript compiler >>> 7) benchmarking node.js projects (why ab is not enough)
>>> Cheers, >>> Andrey
>> On Monday, March 26, 2012 4:26:13 PM UTC+11, Andrey Sidorov wrote:
>>> Hi all,
>>> While we still want to keep decentralized 'come and code together' >>> approach it would be helpful to share some topics of interests in >>> advance. Feel free to post here your ideas, from 20minutes >>> presentation with projector and mic to small particular piece of code >>> to discuss with other.
>>> My potential topics: >>> (one of first two could be a 10-20 min talk): >>> 1) X Server in the browser. Node.js serverside birdge X11 <-> >>> socket.io, client-side XServer logic >>> 2) Implementing network protocol servers and clients (existing or >>> your own protocols) in node.js. Short overview for existing protocols >>> (mysql, fastcgi, x11, memcached, rfb, http, spdy) - what makes good >>> protocol good, overview of existing un-framing and deserealiser >>> libraries (Buffers.read*, bufferlists etc), ...
>>> 3) using node profiler >>> 4) parsing JS source with uglifyjs >>> 5) D-BUS native client library in node >>> 6) PHP->javascript compiler >>> 7) benchmarking node.js projects (why ab is not enough)
>>> Cheers, >>> Andrey
>> On Monday, March 26, 2012 4:26:13 PM UTC+11, Andrey Sidorov wrote:
>>> Hi all,
>>> While we still want to keep decentralized 'come and code together' >>> approach it would be helpful to share some topics of interests in >>> advance. Feel free to post here your ideas, from 20minutes >>> presentation with projector and mic to small particular piece of code >>> to discuss with other.
>>> My potential topics: >>> (one of first two could be a 10-20 min talk): >>> 1) X Server in the browser. Node.js serverside birdge X11 <-> >>> socket.io, client-side XServer logic >>> 2) Implementing network protocol servers and clients (existing or >>> your own protocols) in node.js. Short overview for existing protocols >>> (mysql, fastcgi, x11, memcached, rfb, http, spdy) - what makes good >>> protocol good, overview of existing un-framing and deserealiser >>> libraries (Buffers.read*, bufferlists etc), ...
>>> 3) using node profiler >>> 4) parsing JS source with uglifyjs >>> 5) D-BUS native client library in node >>> 6) PHP->javascript compiler >>> 7) benchmarking node.js projects (why ab is not enough)
>>> Cheers, >>> Andrey
>> On Monday, March 26, 2012 4:26:13 PM UTC+11, Andrey Sidorov wrote:
>>> Hi all,
>>> While we still want to keep decentralized 'come and code together' >>> approach it would be helpful to share some topics of interests in >>> advance. Feel free to post here your ideas, from 20minutes >>> presentation with projector and mic to small particular piece of code >>> to discuss with other.
>>> My potential topics: >>> (one of first two could be a 10-20 min talk): >>> 1) X Server in the browser. Node.js serverside birdge X11 <-> >>> socket.io, client-side XServer logic >>> 2) Implementing network protocol servers and clients (existing or >>> your own protocols) in node.js. Short overview for existing protocols >>> (mysql, fastcgi, x11, memcached, rfb, http, spdy) - what makes good >>> protocol good, overview of existing un-framing and deserealiser >>> libraries (Buffers.read*, bufferlists etc), ...
>>> 3) using node profiler >>> 4) parsing JS source with uglifyjs >>> 5) D-BUS native client library in node >>> 6) PHP->javascript compiler >>> 7) benchmarking node.js projects (why ab is not enough)
>>> Cheers, >>> Andrey
>> On Monday, March 26, 2012 4:26:13 PM UTC+11, Andrey Sidorov wrote:
>>> Hi all,
>>> While we still want to keep decentralized 'come and code together' >>> approach it would be helpful to share some topics of interests in >>> advance. Feel free to post here your ideas, from 20minutes >>> presentation with projector and mic to small particular piece of code >>> to discuss with other.
>>> My potential topics: >>> (one of first two could be a 10-20 min talk): >>> 1) X Server in the browser. Node.js serverside birdge X11 <-> >>> socket.io, client-side XServer logic >>> 2) Implementing network protocol servers and clients (existing or >>> your own protocols) in node.js. Short overview for existing protocols >>> (mysql, fastcgi, x11, memcached, rfb, http, spdy) - what makes good >>> protocol good, overview of existing un-framing and deserealiser >>> libraries (Buffers.read*, bufferlists etc), ...
>>> 3) using node profiler >>> 4) parsing JS source with uglifyjs >>> 5) D-BUS native client library in node >>> 6) PHP->javascript compiler >>> 7) benchmarking node.js projects (why ab is not enough)
I think just pick one topic you feel happy to present about and that might hold general interest to the group and put together a 5 to 10 minute presentation about it.
Longer presentations are okay, too, but I think it's better generally to limit the talk to a quick format and then go into more depth with others at the pub, after the meeting, or over a hack session.
On Monday, March 26, 2012 5:05:55 PM UTC+11, Conrad Pankoff wrote:
> Hey all,
> I haven't been to one of these meets yet, but I'm really looking forward > to it. I'd be happy to give a talk about my templating library (
> https://github.com/deoxxa/node-ginger<https://github.com/deoxxa/node-ginger>), > binary protocol handling with node-binary, spinning up web services really > quickly with mongoskin and express or anything else I've done that's on my > github account.
> Conrad
> On 26/03/2012, at 4:56 PM, Andrey Sidorov wrote:
> my vote to everyauth
> On Mon, Mar 26, 2012 at 4:51 PM, Nicholas Faiz <nicholas.f...@gmail.com> > wrote:
> Hey,
> My vote is to keep presentations at 10 minutes or less. I like the > lightning
> talk format, in fact.
> Andrey, I'd be really interested in hearing about the node profiler or
> benchmarking - options 3) and 4).
> For my part, I might give a quick overview on either drafts
