Feedback
- Interested in knowing more about Rhino performance benchmarks and improvements.
- Very interested in using Ringo's CometD/Bayeux package in a real-world project.
- Demo itself perceived as "suboptimal". ;)
- Seemed to be merely a big excuse how Ringo is inferior to Node.js.
- Take more time in explaining how things actually work.
- More in-depth explanations of actual code (hands-on-ish).
- Suggestion to take examples by Rails'/DHH's evangelism.
- Should rather emphasize on showing off Ringo's strengths.
- Focus more on where Ringo's superior would make sense.
- General suggestion to actually offensively draw comparisons with Node.js, e.g.:
- Faster development with Ringo.
- Full and convenient access to Javaland.
- Ringo's CometD/Bayeux, HTTP client etc. can be used async.
- But maintainable seq. coding offered where it makes sense.
- Actively present interesting libs Ringo has and Node doesn't.
- Increase marketing Ringo's storage APIs and supported backend solutions.
- Don't just mention Hibernate w/o demo how beautiful it is to use from Ringo.
- I.e., preferably show how Ringo works with RDBs, then mention "scary" Hib.
- E.g.: "Oh, and all that works on top of Hibernate if you need more power...".
- Compare storage APIs to Rails' ActiveRecord (-> show where Ringo's better).
- People who see demo/presentation actually want to know 2 things:
- Can I do with Ringo everything I can do with Node?
- Is Ringo maybe even more powerful than Node?
- Put a Node-like, FB-ish chat right on ringojs.org.
- Put a slick Slideshare presentation there as well.
- Pitch Ringo's web framework ("competitve advantage").
edit this page |
list all pages |
go home