Red Hat is an interesting scenario: they immediately took on Linux to the corporate market, sold support-subscriptions at a reasonable cost but (except for a brief complimentary period) never free-of-charge. They also had a very successful IPO (thank ye!!) and they bankrolled all that cash instead of spending it on riotous living, or so I am told. (And so did I ... ;-) )
Nevertheless, the core problem for the second-example company definitely is revenue. And I suspect that a great many (Perl and otherwise) consultancies and support-providers might well be feeling that pinch in a different form. Having software out there in the market is nothing but a great big sucking sound unless it can be tied, and kept tied, to a dependable revenue stream source. Red Hat certainly did that from the get-go, and that good plan was in their original pre-IPO strategy document, but they also operate at a fairly big economy of scale and with deep pockets. I am not sure that even they could have started with one business-proposition and switched to another.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|