Hi BrowserUk,

Thank you for your continued interest in RPerl!

To answer your concerns:

Pick a problem

DONE: Alioth "n-body" Solar System Gravity Application

Write a piece of (non contrived; non-simplistic) Perl code that solves that (real world) problem

DONE: Both Monolithic Version and Non-Monolithic Version

Benchmark it (the exact same script) under bog standard Perl and again under RPerl running under the same version of Perl

DONE: n-body Benchmarks

Publish the script

DONE: n-body Script

Publish the command sessions to run both versions

DONE: n-body Command Sequence

Publish a straight forward, line-by-line, textual, command line session to down load and install all the requirements of RPerl

DONE: RPerl INSTALL Notes (Hint: Use Ubuntu & type `cpan RPerl`)

Forget the hype; Forget the videos

NO: I am excited about RPerl and so are many other people. Kickstarter virtually requires videos, and I have no intention of stopping that just because you don't like videos. If you have actual feedback of how to make the videos better, I'm more than open to constructive criticism!

Forget fancy meaningless graphics and js-heavy websites

NO: Graphics are a proven aid to memory, even if you do not happen to personally be a graphics-oriented learner. You think that RPerl.org is Javascript-heavy? It is one of the default templates from Github Pages. I did not create whatever Javascript to which you may be referring, it was Github.

One, simple, plain html(4) page of text that gives us...

YES: I will create an RPerl Quick Start Guide, but not tonight, it is 5:30am and I need to sleep soon.

A simple bullet point list of what constructs are supported (or those not supported if shorter). Now, in the current available version.

DONE: Low-Magic Perl Commandments

A clear list of the goals of the funding you seek. (Bullet points that show what that is currently not supported that can be with more funding.)

DONE: Kickstarter "v1.2 Features" and "Stretch Goals"; TPF Proposal 1; TPF Proposal 2; TPF Proposal 3; and TPF Proposal 4.

Do all of that; and you might encourage people to look; to try; to access; and maybe, fund.

The only thing not currently done is to copy all the stuff from this post into an HTML file to make the RPerl Quick Start Guide.

Meanwhile, please go ahead and read through this post carefully, then let me know if I have missed anything which should go into the Quick Start Guide. I am counting on your contribution to Kickstarter before the campaign ends in 4 days.

Thanks!

Perling,
~ Will the Chill

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.