comment on

I followed your link and looked, but all I saw was a pretty diagram consisting of colored boxes with buzzwords in them arranged in a grid, and a little marketing hype. The only other links I saw were to 'screenshots'.

From the phrasing of your OP

After spending the last several years working on projects that ended up needing these kinds of tools, I finally decided to sit down and write them.

this would appear to be a one man development effort, so the text in the boxes:

WWW-live server.
What's the alternative to a "live" WWW server? A dead WWW-server? An offline WWW server?
Customer Extranet.
What does this mean? Something more that you can give customers an ID?password to logon to one or more of your systems?
Document Server.
Documents? Like HTML files? But that would be a web server.
Maybe .PDF files. Hmmm. Documents live in files. So a 'document server' is just a 'file server'.
Unless this is one of them guys in a classy suit that walks up to you, asks: "Are you Mr. firstname lastname"? And when you confirm your identity, 'serves' you with some 'documents'?
Messaging server.
Notification Server.
Scheduling server.
Event stream.
Subscriber API.
Publisher API.
Public API.
Web services.
Bulk email server.
Datapipe server.
Portal server.
WWW-Dev server.
Ah. This is the alternative to a 'live' WWW server--but isn't the difference between them that one is web facing and one is not? If the difference is more than that, doesn't that mean that once I've developed and tested my applications on my WWW-dev server, I have to re-test my applications on my WWW-live server to ensure that they run there also?

All that leads me to these possible descriptions:

Overambitious.
Available "Real Soon Now".
Why does this guy think that he can compete with, never mind surpass, these existing suites?

Sorry if that sounds cynical, but your 10,000 foot overview tells me so little about your development platform that it is a bit like trying to describe a property after being pointed at an ariel view of it taken from a similar height. "It's that slightly darker grey pixel just there."

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^3: Categorizing a Perl Development Platform by BrowserUk
in thread Categorizing a Perl Development Platform by jdrago_999

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! —

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:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

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

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