But I wanted to make a meeting agenda site, since I don't like any of the ones out there right now. So the last 4 days I worked on one writing it as a JS web app that talks to a Node backend. It was quite painless. Anything I wanted to do (whether generating uuids, date formatting, etc.) there was a module available on npm. Couldn't be easier.
The platform has really matured a lot, and I didn't run into any issues with Node itself.
If you haven't yet, the next time you're doing an experiment, give it a try. I will probably write my next project this way too.
2) cached or uncached templates?
3) throw 1k+ requests per second and tell us which one is faster
"Probably" is, ipso facto, not normative.
Node's public API is not changing in a backward-incompatible way every day (or even every week, or every month). The software is widely used in production.
I think node 1.0.0 should have been some time ago, and this release should have bumped the major version again.
"The software is widely used in production."
Depending on how you define the "public API", things have changed from 0.8 to 0.10 (streams API, for example).
Your definition of Node 1.0.0 is based on your conception of how others are using node. People can use experimental software in high-profile places without deeming the underlying technology stable.
"Node's public API is not changing in a backward-incompatible way every day (or even every week, or every month). "
Also: in general, development is highly nonlinear. I would say the API is stable when the core developers deem it stable.
When you are in the docs make sure you focus on stream, callbacks, and event emitters. Once you have those down start gluing NPM modules together.
"After 0.12, the next major stable release will be 1.0. At that point, very little will change in terms of the day-to-day operation of the project, but it will mark a significant milestone in terms of our stability and willingness to add new features. However, we've already gotten strict about maintaining backwards compatibility, so this won't really be so much of a shift. "