comment on

This seems like a really poor analogy, it's all anecdotal.

It is no analogy, and even if it's all anecdotal, it is first class experience, the sort of used to build science. What's wrong with that? The hard facts are

my old workstation was a dime against a quarter compared to that pizza box
my phone could replace at least 10 of them (let's round that down)
it was 10 times as responsive as the phone

which, doing the math, means that my perl application of the old days is 250 times faster. That might be a particularity of the Android platform, and yes the dev side is a nightmare - but why?

Because of bloat. If I set up a tiny Java devel environment today (think eclipse only), I spend at least about 400MB of disk space; perl5.25.10 on my platform is 105MB, add a full-fledged vim (30MB) and you have 135 MB. I suspect that if perl was used to build eclipse, it would take only a fraction of disk space, and of exercised code, maybe a dime against a dollar.

I call bloat also not using things a platform already provides, but blowing up your own souffé. Perl took the approach to use libs and tools a platform already has, whilst Java likes to cook its own soup.

Java has improved tremendously in the past 5-10 years in all aspects. There are plenty of things people can bitch about but overall, it's a clean, solid platform to develop on.

That might well be, and I am not saying Java isn't clean and solid - but it ain't the fastest thing since sliced bread, not in learning curve, not in development time, not in code execution, and don't let us talk about memory usage and garbage collection. I've seen spikes of loads of 1000 on an e10k Sun because the garbage collector kicked in... anyways - this is now an analogy: I am using the good ol' olvwm OpenLook window manager based on xview as my debian desktop, and it nicely handles all things KDE, Gnome and whatever other desktop window manager can handle. And it does it with a memory footprint of 4MB, even being bloated, too...

BTW, if Java were implemented in forth, that would give a different picture - but only because C is also bloated in comparison to forth ;-)

perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'

In reply to Re^5: Can Perl do anything Java can do? by shmem
in thread Can Perl do anything Java can do? by MikeBraga

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.


There's more than one way to do things
	PerlMonks