4 ms·

Ah, I'll take a look at that, but actually I was describing 0MQ not TCP. Did you mean I should describe what 0MQ is first?

by zedshaw 16y ago

nailer 16y ago
The preceding sentence is: "What ZeroMQ ends up being is ”sockets the way programmers think sockets work.” Programmers usually hear about TCP or UDP sockets and they think in a naive way that they work like this: " Which makes me think you're talking about TCP or UDP sockets outside of 0MQ. There's also some tightening you could do in your opening paragraph about why Mongrel 2 is awesome. How about this for an intro: Mongrel 2 is awesome for the following reasons: * It can serve both traditional web apps and realtime push-style apps, where the server sends stuff to the clients when you need - great for making chat apps (there's one included in the sample code), stock sites that sends updated pricing to browsers, live blogging updates about news events as they happen or anything else you can think of. * You can make Mongrel apps in your preferred language - PHP, Ruby, Python, C++ now, more soon. You can even configure it in that language.' You say all these things now, but you're currently using too many words. Make it tighter.
- zedshaw 16y ago
  Done: http://mongrel2.org/tktview/b685326bc0ded7a466b61fb0d1c6e7d598c5a5d4 http://mongrel2.org/tktview/b685326bc0ded7a466b61fb0d1c6e7d5... I tend to spew at the mouth then tighten it up later.
  - nailer 16y ago
    Cheers. If it's not obvious, it's me who's bugging you about task-based stuff on Twitter. I spent a few years writing professionally and have a somewhat thick skin of my own when it comes to the editing pen, so pardon if I'm a little insensitive in the suggestions. * You are, genuinely, missing a few 'open your browser, hit this port and try it' bits per Twitter. yes we're looking at the same doc, but I think you're presuming people will actually open their browsers and look at the http://localhost:6767/tests http://localhost:6767/tests or whatever, rather than being told to do so. You also don't show or mention what people can expect to see when they visit this. Throw a screenshot in. * The sections about Steve and Knuth, sysadmins who can't code, and alternative inits you've tried but not liked, can be removed. They distract from the topic at hand. I read the bit about 'insulting to keep you interested' but it doesn't lend the doc character: it comes off like you're bitter, and doesn't help the end user actually set up Mongrel. * For config, first show people how to configure mongrel using the default Python config file. Once you've done that then point out that they can create their own config formats if they don't like Python or want to automate stuff. Mention MVC if you want, restrict it to one sentence at the end. The aim is to making a working web server - anything asides from that gets in the way. See Kathy Sierra's stuff about 'helping users be awesome' for some good info on this. * Be specific. 'Hacking' could be 'making web apps with Mongrel 2'. Per Twitter 'hacking' is ambiguous - think of the HACKING file in every GNU app which discusses modifying the program itself, rather than using it. With a bit of editing, the current daunting manual could be about 50% the size.

Ah, I'll take a look at that, but actually I was describing 0MQ not TCP. Did you mean I should describe what 0MQ is first?

by zedshaw 16y ago

Ah, I'll take a look at that, but actually I was describing 0MQ not TCP. Did you mean I should describe what 0MQ is first?

nailer 16y ago

The preceding sentence is: "What ZeroMQ ends up being is ”sockets the way programmers think sockets work.” Programmers usually hear about TCP or UDP sockets and they think in a naive way that they work like this: " Which makes me think you're talking about TCP or UDP sockets outside of 0MQ. There's also some tightening you could do in your opening paragraph about why Mongrel 2 is awesome. How about this for an intro: Mongrel 2 is awesome for the following reasons: * It can serve both traditional web apps and realtime push-style apps, where the server sends stuff to the clients when you need - great for making chat apps (there's one included in the sample code), stock sites that sends updated pricing to browsers, live blogging updates about news events as they happen or anything else you can think of. * You can make Mongrel apps in your preferred language - PHP, Ruby, Python, C++ now, more soon. You can even configure it in that language.' You say all these things now, but you're currently using too many words. Make it tighter.

zedshaw 16y ago
Done: http://mongrel2.org/tktview/b685326bc0ded7a466b61fb0d1c6e7d598c5a5d4 http://mongrel2.org/tktview/b685326bc0ded7a466b61fb0d1c6e7d5... I tend to spew at the mouth then tighten it up later.
- nailer 16y ago
  Cheers. If it's not obvious, it's me who's bugging you about task-based stuff on Twitter. I spent a few years writing professionally and have a somewhat thick skin of my own when it comes to the editing pen, so pardon if I'm a little insensitive in the suggestions. * You are, genuinely, missing a few 'open your browser, hit this port and try it' bits per Twitter. yes we're looking at the same doc, but I think you're presuming people will actually open their browsers and look at the http://localhost:6767/tests http://localhost:6767/tests or whatever, rather than being told to do so. You also don't show or mention what people can expect to see when they visit this. Throw a screenshot in. * The sections about Steve and Knuth, sysadmins who can't code, and alternative inits you've tried but not liked, can be removed. They distract from the topic at hand. I read the bit about 'insulting to keep you interested' but it doesn't lend the doc character: it comes off like you're bitter, and doesn't help the end user actually set up Mongrel. * For config, first show people how to configure mongrel using the default Python config file. Once you've done that then point out that they can create their own config formats if they don't like Python or want to automate stuff. Mention MVC if you want, restrict it to one sentence at the end. The aim is to making a working web server - anything asides from that gets in the way. See Kathy Sierra's stuff about 'helping users be awesome' for some good info on this. * Be specific. 'Hacking' could be 'making web apps with Mongrel 2'. Per Twitter 'hacking' is ambiguous - think of the HACKING file in every GNU app which discusses modifying the program itself, rather than using it. With a bit of editing, the current daunting manual could be about 50% the size.